jspωiki
Iteration Planning

Overview#

Iteration Planning is for the Delivery Team to commit to the completion of a set of the highest-ranked product backlog items.

This commitment defines the Sprint Backlog and is based on the team's velocity or capacity and the length of the Sprint.

Who Is Involved?#

Iteration Planning is a collaborative effort involving these roles:

Before The Iteration Planning#

Before getting started, ensure:

Equal Opportunity Backlog#

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 sprint
  • We can verify it has been implemented correctly

Right-Size Backlog Items#

Product Backlog items too large to be completed in an Sprint need to be split into smaller pieces. The best way to split Product Backlog items is by Business value, not by process.

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 techniques

Using Velocity and Capacity for Iteration Planning#

Mature teams can use Using Velocity and Capacity for Iteration Planning

More Information#

There might be more information for this subject on one of the following: