Iteration planning determines the work that the team commits to be completed in the iteration by adjusting the predicted velocity and managing the number and priority of assigned, deferred, and/or new stories. The Iteration Planning Meeting is usually facilitated by the Team Agility Master.
Why to do this practice
The length of an iteration enforces a common cadence and creates boundaries for work. With a fixed iteration length, the Product Owner and the team adjusts scope and cost to fit what can be done in the iteration.
At the beginning of a project, there may be an initial allocations of features or stories to increments based on value or dependencies. However, as the project unfolds, these are revisited at the beginning of each iteration to ensure that the scope of the iteration is reasonable given the current team capacity and that it includes high value work based on the changing environment at the stakeholder and business value level.
Who does this practice
Here are the roles involved in this practice:
What to do
Inputs to iteration planning include:
Here are variances to iteration planning:
Iteration planning should be done as a collaborative exercise. Collaboration establishes a reasonable set of stories to implement within the increment given current team, project and stakeholder status.
Adding, revising, and removing requirements
As customers gain experience with the product, they learn more about what they need. They may development new requirements, may decide they no longer need something they had asked for, or may decide that something is more important or less important than before.
At the end of each iteration, based on what the customer has learned from seeing and using the product, the Product Manager (acting as advocate for the customer) can:
After these adjustments are made, the collection of requirements are then prioritized and used as input for the next iteration.
Issues and considerations
Here are some issues to consider.
Iteration planning results in an iteration backlog. It is populated with stories and any subtasks that are sized, ranked, have agreed to acceptance criteria; project board and team environment set up and cleaned up; team is committed to next iteration.
When to do this practice
Iteration planning is done on the first day of every iteration.
Where to do this practice
Iteration planning is done in a meeting room near the team or people who are involved in the iteration.
Iteration planning results in a clear scope of work for the next iteration must be feasible for the current team.