Overview#Iteration Planning is for the team to commit to the completion of a set of the highest-ranked product backlog items.
This commitment defines the iteration Backlog and is based on the team's velocity or capacity and the length of the iteration.
Who Is Involved?#Iteration Planning is a collaborative effort involving these roles:
- Scrum Master: Facilitates the meeting
- Product Owner: Represents the detail of the product backlog items and their acceptance criteria
- Delivery Team: Define the tasks and effort necessary to fulfill the commitment
Before The Iteration Planning#Before getting started, ensure:
- The items in the product backlog have been sized by the team and assigned a relative story point value
- The product backlog is stack ranked to reflect the priorities of the Product Owner
- There is a general understanding of the acceptance criteria for these ranked backlog items
The product backlog addresses new functionality and fixes to existing functionality. The order in which a product backlog item is scheduled is completely independent of its ancestry.
For the purpose of Iteration Planning, the important characteristics for a product backlog item are:
- It is small enough to be completed in the iteration
- We can verify it has been implemented correctly
Right-Size Backlog Items#
If we can split a product backlog item so that its children deliver value, then our iterations incrementally deliver value. If you split by process, then we impact time-to-market because value is not delivered until all the children are complete.
Compound stories can be easily split through disaggregation. Complex stories present a different challenge. Bill Wake enumerates twenty techniquesVelocity and Capacity for Iteration Planning