Product Delivery Playbook >> Events >> Product Planning
Embedded Files
Purpose: To collaboratively define the work the team will commit to for the upcoming iteration (usually a sprint). It's about understanding the "what," "why," and "how" of the work and creating a shared plan.
Who Attends:
Who Attends:
Product Owner (PO): Presents and clarifies the prioritized backlog items (the "what" and "why").
Development Team: Discusses technical feasibility and determines how the work will be done (the "how").
Scrum Master (SM): Facilitates the session, ensures the process is followed, and removes impediments.
When: Typically at the beginning of each iteration (e.g., sprint).
Key Activities:
Key Activities:
- Review the Iteration Goal (If Applicable):
The PO often articulates a high-level objective for the iteration to provide focus.
- Select Backlog Items:
The PO presents the top prioritized items from the product backlog.
The Development Team discusses each item, asking clarifying questions to ensure a shared understanding of the requirements and acceptance criteria.
The team considers their capacity (velocity) from previous iterations.
The team collaboratively selects the backlog items they believe they can realistically complete within the iteration.
- Task Breakdown (Optional but Recommended):
For each selected backlog item, the Development Team may break it down into smaller, more manageable tasks.
This helps with understanding the work involved and tracking progress.
- Estimation (If Not Already Done):
If backlog items haven't been estimated during refinement, the team will estimate the effort required for each selected item (using story points, t-shirt sizes, or hours).
- Identify Dependencies and Risks:
The team discusses any dependencies between the selected items or potential risks that could impact their ability to deliver.
Strategies for managing dependencies and mitigating risks may be discussed.
- Team Capacity Discussion:
The team considers individual availability (e.g., holidays, time off) to ensure the planned workload is realistic.
- Commitment and Plan Finalization:
The Development Team collectively commits to delivering the selected backlog items by the end of the iteration.
The iteration backlog (the list of committed items and their associated tasks) is finalized and made visible to the team and stakeholders.
Tips for a Successful Session:
Tips for a Successful Session:
Come Prepared: The PO should have a well-prioritized and refined backlog. The team should have reviewed it beforehand.
Focus on Value: Prioritize items that deliver the most business value.
Encourage Collaboration: Foster an open and inclusive environment where everyone contributes.
Keep it Timeboxed: Respect the allocated time for the planning session.
Focus on "What" and "Why" (PO) and "How" (Team): Maintain clear roles.
Aim for a Realistic Commitment: Avoid over-committing the team.
Visualize the Plan: Make the iteration backlog visible (e.g., on a physical board or in a digital tool).
Outcome:
Outcome:
A clear and shared understanding of:
The goal of the iteration (if defined).
The backlog items the team will deliver.
The plan for how the work will be done (potentially including tasks).
Any dependencies and risks.
The team's commitment for the iteration.
Effective planning sessions set the stage for a focused and productive iteration, increasing the likelihood of delivering valuable software.
Page updated
Report abuse