HKSM
Sprint Review Meeting
An end-of-Sprint session, limited to four hours for a one-month Sprint and scaled to match shorter or longer Sprints, where the Scrum Team demonstrates the Sprint's outputs to the Product Owner, who may accept or reject the work.
Key Points
- Time-box: 4 hours for a one-month Sprint, adjusted proportionally for other Sprint lengths.
- Purpose: inspect the Increment, gather feedback, and update the Product Backlog as needed.
- Participants: Scrum Team and Product Owner; stakeholders may attend; Scrum Master facilitates.
- Outcome: acceptance decisions on delivered work and identified changes or follow-ups.
Example
At the end of a two-week Sprint, the Scrum Team holds a two-hour review. They demo a new search feature to the Product Owner and key stakeholders. The Product Owner accepts the feature but requests a change to the filter behavior, which is added to the Product Backlog for future prioritization.
PMP Example Question
Which Scrum event is time-boxed to four hours for a one-month Sprint (scaled to Sprint length) and focuses on demonstrating completed work to the Product Owner for acceptance?
- Sprint Planning
- Daily Scrum
- Sprint Review Meeting
- Sprint Retrospective
Correct Answer: C — Sprint Review Meeting
Explanation: The Sprint Review is the end-of-Sprint event where the team showcases the Increment and the Product Owner may accept or reject deliverables. It is time-boxed to four hours for a one-month Sprint and scales with Sprint length.
