ABSTRACT
In a Nutshell: Iterative development is the key technique used by a design and development team to evolve solutions from a high-level idea to a delivered product. The so-called evolving solution is the main CCM product that is subjected to the iterative development process, although it is expected that the concepts associated with the technique will be applied to most project deliverables. As such, this approach is a life cycle within a life cycle. Iterative development is a way of breaking down the solution development of a large change management intervention into smaller chunks. In iterative development, the basic approach is designed, developed, and tested in repeated cycles. With each iteration additional features can be designed, developed, and tested until there is a fully functional application already being deployed to customers in three-to six-month cycles. Iterative development contrasts with change management traditional methods in which each phase of the development life cycle is a gated one. If software is involved, then coding doesn’t begin until design of the entire proposed application is complete and has gone through a phased gate review. Likewise, testing doesn’t begin until all production and coding is complete and has passed necessary phase gate reviews. The purpose of working iteratively is to allow more flexibility for changes. When requirements and design of a major application are done in the traditional method, there can be unforeseen problems that don’t surface until development begins. By working iteratively, the change management team goes through a cycle where they evaluate with each iteration and determine what changes are needed to produce a satisfactory end product.
