concept next iteration in category agile

This is an excerpt from Manning's book Becoming Agile ...in an imperfect world. Login to get full access to this book.

Table 8.7. Acme Media’s Adapt phase embraces change. The team focuses on learning as the project progresses and delivering what is needed at the end, not necessarily what was requested at the beginning.

Step	Adapt phase	Group(s)	Change notes
1	Perform customer acceptance.	Requirements and guests	In the past, Acme performed customer acceptance at the very end of development. The new process allows several reviews. The deliverables for the iteration are presented to the customer for review, testing, and ultimately acceptance. When the review is kicked off, stakeholders are invited to see the overall status of the iteration. In the past, the review was only for customers. This step helps prevent surprises. If features aren’t accepted, the team reviews the issues and makes a decision on whether to continue work on the feature into the next iteration. In the past, rework time was limited to the bug-fix window.
2	Undertake discovery.	Project team	The team reviews new information that materializes during development: business-climate changes, competitor product changes, priority changes, and so on.
3	Evaluate the iteration pace.	Project manager	The project manager reviews development’s actual velocity versus the forecast velocity and adjusts the features assigned to the next iteration accordingly.
4	Re-plan.	Project manager and team	The team modifies the plan for the next iteration based on all the information gleaned during the Adapt phase.

Accept the discovery and continue the work into the next iteration. Try to demonstrate the state of the feature at the end of the iteration if possible, with a test harness or limited user interface.

Figure B.4. Development starts by establishing a foundation in iteration 0. Iteration 0 includes items such as architectural design, environment preparation, and finalizing contracts. Development iterations follow, delivering working code in subsets every 2 to 4 weeks. The working code is surfaced for a demonstration and customer feedback. That feedback is incorporated during the planning cycle for the next iteration. When all iterations are completed, the code is delivered to a Production environment.