Comments on: Agile is the only way to build SharePoint applications. http://blog.glenc.net/2007/06/15/agile-is-the-only-way-to-build-sharepoint-applications/ Treading water in a sea of man-made confusion. Fri, 10 Jun 2011 04:47:02 +0000 hourly 1 http://wordpress.org/?v=3.1.3 By: Tim http://blog.glenc.net/2007/06/15/agile-is-the-only-way-to-build-sharepoint-applications/comment-page-1/#comment-5688 Tim Mon, 02 Jun 2008 14:35:07 +0000 http://blogtmp.glenc.net/2007/06/15/agile-is-the-only-way-to-build-sharepoint-applications/#comment-5688 Glen I take just about everything you said verbatim. The only point I have trouble with is point 2. in your benefits list "Wireframes and UI designs are less critical because you can “design” on the fly using the out of the box UI - then identify the gaps where additional design elements or controls are needed." Taking an Agile approach gives a designer more data to use in the design process but SP OOTB UI is not an Agile shortcut to UI design. Design is still required as UI design should not be driven by one UI view of the world. UI design criticality remains unchanged. Glen I take just about everything you said verbatim. The only point I have trouble with is point 2. in your benefits list “Wireframes and UI designs are less critical because you can “design” on the fly using the out of the box UI – then identify the gaps where additional design elements or controls are needed.”

Taking an Agile approach gives a designer more data to use in the design process but SP OOTB UI is not an Agile shortcut to UI design. Design is still required as UI design should not be driven by one UI view of the world. UI design criticality remains unchanged.

]]> By: Ricky http://blog.glenc.net/2007/06/15/agile-is-the-only-way-to-build-sharepoint-applications/comment-page-1/#comment-1407 Ricky Sat, 09 Feb 2008 21:47:26 +0000 http://blogtmp.glenc.net/2007/06/15/agile-is-the-only-way-to-build-sharepoint-applications/#comment-1407 Wow. I think this single post might just break us out of the analysis paralysis hole that we're just starting to realize we've been digging. We have been waterfalling hard. We've started with trying to come up with every user/scenario/need permutation that "might" one day be requested, then trying to go through each part of the product to see what we would have to do to prepare for it, then figure out how to actually change it. And our case is even worse - we essentially can start with a blank slate; there's really no solution or user requirements other then our (I.S.) best (non-user) guesses! What we really should be doing is going with the defaults that have been defined for a good reason. If some thing's not working, you then have to make the argument as to why the default won't work for you and then implement the customization in the least invasive way to make them happy. We're spending a majority of our time in over-designing something that will handle all potential things for all potential people. In reality it's pretty much there now, and for the things that do pop up there's usually a solution with negligent impact. Thank you! Wow. I think this single post might just break us out of the analysis paralysis hole that we’re just starting to realize we’ve been digging. We have been waterfalling hard. We’ve started with trying to come up with every user/scenario/need permutation that “might” one day be requested, then trying to go through each part of the product to see what we would have to do to prepare for it, then figure out how to actually change it. And our case is even worse – we essentially can start with a blank slate; there’s really no solution or user requirements other then our (I.S.) best (non-user) guesses!

What we really should be doing is going with the defaults that have been defined for a good reason. If some thing’s not working, you then have to make the argument as to why the default won’t work for you and then implement the customization in the least invasive way to make them happy.

We’re spending a majority of our time in over-designing something that will handle all potential things for all potential people. In reality it’s pretty much there now, and for the things that do pop up there’s usually a solution with negligent impact.

Thank you!

]]> By: Henry http://blog.glenc.net/2007/06/15/agile-is-the-only-way-to-build-sharepoint-applications/comment-page-1/#comment-267 Henry Thu, 21 Jun 2007 00:05:19 +0000 http://blogtmp.glenc.net/2007/06/15/agile-is-the-only-way-to-build-sharepoint-applications/#comment-267 Kudos Glen! Thanks for the insight. Kudos Glen! Thanks for the insight.

]]>