Chapter 16. Concluding a Construction Iteration

Improving software development practices counts for nothing unless it improves software development results.

As you learned in Chapter 15, “A Typical Day of Construction,” a properly executed Construction iteration yields a tested working solution every day. If the iteration was successful the team should be able to demonstrate functionality representing the work items that they committed to deliver at the beginning of the iteration. The end of the iteration is also a good time to assess progress against the release plan, evaluate the team’s performance, and identify any opportunities for improvement. The end of each iteration is an opportunity to discuss with your stakeholders how, or whether, ...

Get Disciplined Agile Delivery: A Practitioner’s Guide to Agile Software Delivery in the Enterprise now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.