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 the teams to a common vision and to provide cadence and synchronization of the software assets the program is developing. We also introduced release planning as the seminal ...
Get Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and 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.
