Comments on: Scope and vision http://blog.butel.co.nz/2007/08/12/scope-and-vision/ The crossover between business and software Mon, 22 Feb 2010 02:50:54 +0000 http://wordpress.com/ hourly 1 By: papa http://blog.butel.co.nz/2007/08/12/scope-and-vision/#comment-2581 papa Sun, 02 Dec 2007 16:01:52 +0000 http://blog.butel.co.nz/2007/08/12/scope-and-vision/#comment-2581 It was very helpful by providing info about how the scope vision should look like It was very helpful by providing info about how the scope vision should look like

]]> By: Andrew http://blog.butel.co.nz/2007/08/12/scope-and-vision/#comment-293 Andrew Tue, 14 Aug 2007 05:23:53 +0000 http://blog.butel.co.nz/2007/08/12/scope-and-vision/#comment-293 I'm a big fan of the Unified Process (http://en.wikipedia.org/wiki/Unified_Process) for iterative and incremental software development, where each of the four phases have well defined outputs before the next phase begins. Often these outputs are implicit, which easily leads to incorrect software being built. Having explicit outputs from each phase makes the 'vision and scope' document (and other documentation) a deliverable which all stakeholders should expect. Development of a SaaS application is a great example of iterative and incremental software development, as it can be driven by users with very short release cycles. The development of each feature becomes a small project and still needs the vision and scope to be well understood before the use cases, business analysis, interaction design and detailed specification can be completed. I’m a big fan of the Unified Process (http://en.wikipedia.org/wiki/Unified_Process) for iterative and incremental software development, where each of the four phases have well defined outputs before the next phase begins.

Often these outputs are implicit, which easily leads to incorrect software being built. Having explicit outputs from each phase makes the ‘vision and scope’ document (and other documentation) a deliverable which all stakeholders should expect.

Development of a SaaS application is a great example of iterative and incremental software development, as it can be driven by users with very short release cycles. The development of each feature becomes a small project and still needs the vision and scope to be well understood before the use cases, business analysis, interaction design and detailed specification can be completed.

]]> By: Mike Riversdale http://blog.butel.co.nz/2007/08/12/scope-and-vision/#comment-292 Mike Riversdale Tue, 14 Aug 2007 01:37:05 +0000 http://blog.butel.co.nz/2007/08/12/scope-and-vision/#comment-292 <em>A scope document is often (or at least should be) the first deliverable in a software project and its important to get it right.</em> Hmm, I'd say the first deliverable should be a working piece of functionality ... the rest isn't really a deliverable as such but something on the way to it and should be kept to the bare essentials to get you to (as I say) the working product. For instance my latest project is delivering a new way of storing information and allowing collaboration - the "to do list" (Product Backlog) is a wiki page (reviewed/amended each month) and everything else is an actual feature (live not demo/pilot) delivered to the users. A scope document is often (or at least should be) the first deliverable in a software project and its important to get it right.
Hmm, I’d say the first deliverable should be a working piece of functionality … the rest isn’t really a deliverable as such but something on the way to it and should be kept to the bare essentials to get you to (as I say) the working product.

For instance my latest project is delivering a new way of storing information and allowing collaboration – the “to do list” (Product Backlog) is a wiki page (reviewed/amended each month) and everything else is an actual feature (live not demo/pilot) delivered to the users.

]]> By: You can’t have scope until you know what your product IS…. « business, strategy, governance http://blog.butel.co.nz/2007/08/12/scope-and-vision/#comment-281 You can’t have scope until you know what your product IS…. « business, strategy, governance Sun, 12 Aug 2007 23:47:00 +0000 http://blog.butel.co.nz/2007/08/12/scope-and-vision/#comment-281 [...] can’t have scope until you know what your product IS…. Andrew posted over here about the importance of a well thought out scope document for software product [...] [...] can’t have scope until you know what your product IS…. Andrew posted over here about the importance of a well thought out scope document for software product [...]

]]>