A regular meeting for the core team to understand and align on the work to be done.
Core delivery team
Regular planning meetings help ensure the product backlog is well-understood by all team members and always reflects the current priorities. By discussing and sizing product backlog items, the team may align on the delivery impact of the work to be done.
Iteration Planning Meetings should generally follow the cadence of product iterations (e.g. weekly) or should be held as often as needed to maintain a well-sized and well-understood product backlog.
Start by framing the conversation for the meeting. Help to set overall project context as needed by briefly recapping recently accepted and in-progress stories or the current state of the newest capabilities in your acceptance environment, to get everyone aligned on where things currently stand as you enter this next iteration. Review the arc of new user stories by outlining what they will add to the product. Present user interface mockups, if available.
Read through the first user story to explain the business value, the user value, and the acceptance criteria. Allow participants to ask questions, providing clarifications as needed.
Prompt the engineers to indicate if they are ready to estimate the user story and if so, to estimate the relative complexity of the story by simultaneously voting on a story point estimate.
Please see the short guide to estimation below for estimation tips.
If there is a consensus on the estimation, label the user story with the estimation result and promote it to the backlog, indicating to the team the priority of this story. Otherwise, if there is no consensus, prompt the engineers to discuss, and re-estimate if necessary until there is a consensus that the team is happy with.
Repeat steps 2-4 for the remaining user stories that were prepared for this meeting.
In the final 10 minutes of the meeting, review and discuss the relative priorities of product backlog items, including any engineering chores.
Firstly, the team should have a shared understanding of the scope and relative complexity of the product backlog items that were discussed. Secondly, items should have been added to the product backlog, which remains sorted according to current priorities. The team should come away from IPM feeling aligned and energized about the work coming up in the next iteration.
Scrum “Sprints” and “Iterations” are both timeboxed activities but with some differences that impact how planning is done:
|Sprint Planning||Iteration Planning|
|Prerequisites||• A Sprint Goal|
• A prioritized Product Backlog
|• A prioritized Product Backlog|
• User stories to be reviewed
|Objective||• Align on a goal for the Sprint|
• Negotiate and plan the scope for the Sprint (a.k.a. the Sprint Backlog)
|• Maintain a shared understanding of the current scope and priorities (i.e. the Product Backlog)|
|Activities||• Review user stories|
• Pull user stories from the Product Backlog to the Sprint Backlog
|• Review user stories|
• Estimate user stories
• Promote user stories to the Product Backlog according to priority
|Outputs||• An unprioritized Sprint Backlog that the team commits to deliver and demonstrate at the end of the Sprint||• A prioritized Product Backlog|
• An estimation of the work that may be delivered and demonstrated during the Iteration
|Participants||• Product Owner|
|• Core team|
Iteration pre-planning (optional)