Chapter 16. Release Planning
Worldly affairs do not always go according to a plan and orders have to change rapidly in response to a change in circumstances. If one sticks to the idea that once set, a plan should not be changed, a business cannot exist for long.
—Taiichi Ohno, widely considered to be the father of lean manufacturing
We Plan to Re-plan.
—A T-shirt seen at the Agile Alliance Conference
In the previous chapter, we saw how the Agile Release Train implements systemic product development flow at the Program level. This is the primary tool programs use to align ...
- Chapter 16. Release Planning
- from Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise
- Publisher: Addison-Wesley Professional
- Released: December 2010
Using the paradigm of a release train, the release planning event can be compared to a rolling wave that is used to communicate the product vision to the team and enable them to set release objectives. This lesson provides you with a sample agenda and process for conducting the release planning event.
Share this highlighthttp://www.safaribooksonline.com/a/agile-software-requirements/84773/