Product Delivery Playbook >> Events >> Product Review
Embedded Files
Purpose: To inspect the increment (the working software delivered during the sprint) and adapt the product backlog if needed. It's a collaborative event to gather feedback from stakeholders.
Who Attends:
Who Attends:
Scrum Team: Development Team, Product Owner, and Scrum Master.
Stakeholders: Customers, users, management, etc. (anyone with an interest in the product).
When: At the end of each Sprint, typically timeboxed to 1 hour per week of sprint length (e.g., 2-hour review for a 2-week sprint).
Key Activities:
Key Activities:
- Product Owner Recap:
Briefly reminds everyone of the Sprint Goal and what the team set out to achieve.
- Demonstration of the Increment:
The Development Team demonstrates the work they have completed during the sprint.
Focus on working software and new functionality.
Keep the demo focused and avoid technical jargon.
Showcase the features that meet the "Done" criteria.
- Stakeholder Feedback and Discussion:
Stakeholders provide feedback on the demonstrated increment.
This is a crucial opportunity to gather insights, ask questions, and express needs.
The Product Owner facilitates the discussion and ensures feedback is captured.
- Product Owner Discusses Progress Towards Goal:
The PO provides an update on the overall progress towards the Product Goal, based on the sprint's outcome.
- Review of the Product Backlog (Optional but Recommended):
The Product Owner may present the current state of the Product Backlog.
Based on the feedback and the increment, the PO may discuss potential adjustments to priorities, upcoming features, or estimated timelines.
- Next Steps and Closing:
Briefly discuss any immediate next steps or key takeaways.
Thank stakeholders for their participation.
Tips for Success:
Tips for Success:
Focus on the Increment: The primary focus is on the working software delivered.
Keep it Interactive: Encourage stakeholders to ask questions and provide feedback throughout the demo.
Prepare the Demo: The Development Team should rehearse the demonstration to ensure it's smooth and efficient.
Value Stakeholder Feedback: Actively listen to and capture all feedback, even if it's critical.
Be Transparent: Be honest about what was and wasn't completed during the sprint.
Keep it Business-Focused: Frame the discussion around business value and user needs.
Stay Within the Timebox: Respect everyone's time and keep the meeting focused.
Document Key Decisions and Feedback: Record any important decisions or feedback that will impact the Product Backlog.
End on a Positive Note: Acknowledge the team's hard work and progress.
What to Avoid:
What to Avoid:
Technical Deep Dives: The review is for stakeholders, so keep the technical details to a minimum.
Status Reporting: It's a demonstration and feedback session, not a detailed progress report.
Blaming or Defending: Focus on the product and how to improve it.
Treating it as a Sign-Off Meeting: It's about inspection and adaptation, not formal approval.
Outcome of a Successful Sprint Review:
Outcome of a Successful Sprint Review:
Shared understanding of the increment and its value.
Valuable feedback from stakeholders.
Adaptation of the Product Backlog based on insights.
Increased alignment between the Scrum Team and stakeholders.
Clearer direction for future sprints.
By conducting effective Sprint Review ceremonies, you ensure the product is evolving in the right direction based on real-world feedback and stakeholder needs.
Page updated
Report abuse