Chapter 17. Iteration Planning
Each iteration is planned by breaking down the stories for that iteration into tasks. Tasks are scheduled by asking programmers to sign up for the tasks they want, then asking them to estimate their tasks, then rebalancing as necessary.
The release plan is synchronized to the rhythms of business. It gives the business people a way of thinking about sets of stories that together tell a good story to the market. The iteration plan is synchronized to the rhythms of programming. Two weeks is long enough to
Develop some new functionality
Do a substantial refactoring
Develop some infrastructure
Try some experiments
Recover from little disappointments
Unlike the release plan, the iteration plan is very much the developers'. They ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access