There is a fairly large consensus among software industry leaders [14] in support of the benefits of iterative and risk-driven development (many of these benefits are discussed in detail in Chapter 2). Using such an approach typically has substantial benefits, with fewer cost and schedule overruns than waterfall approaches. Predictability is enhanced, allowing the identification of cost or schedule overruns in time to allow for scope cutting, making it possible to deliver at least a reduced set of the most essential capabilities on time and on budget.
But what prevents organizations from using a highly iterative, risk-driven approach with continuous integration and testing? Know-how, good process support, and good tool support.
Because of the benefits of iterative development, projects should strive to go far down on the Waterfall/Iterative axis. However, project teams may find that they need to gain experience, process support, and enhancements of their tool environment in order to get there. |