Sprint Review
PSM I PSM I · Scrum Events
The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of its work to key stakeholders, and progress toward the Product Goal is discussed. During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment, and based on this information they collaborate on what to do next. The Product Backlog may also be adjusted to meet new opportunities. The Sprint Review is timeboxed to a maximum of four hours for a one-month Sprint, and for shorter Sprints it is usually shorter. It is the second-to-last event of the Sprint — only the Retrospective follows it.
The most important thing to understand about the Sprint Review is what it is not. It is not a demo, not a presentation, and not a sign-off gate. The Guide says explicitly that the Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation. A team that shows slides for an hour while stakeholders watch passively is missing the point. The event is a conversation: stakeholders see the Increment, give feedback, share what has changed in their world, and work with the team to figure out the most valuable next steps. That conversation is where adaptation happens at the product level — the Product Backlog is adjusted based on what everyone learned. The exam tests this with options that describe the Review as a formal approval meeting or a demo; both are wrong.
The Sprint Review is also not a gate to releasing value. An Increment may be delivered to stakeholders before the end of the Sprint, and the Review should never be treated as the moment when value is allowed out the door. This matters because many organizations turn the Review into a release approval board, which delays value and contradicts the empirical approach. The Increment is inspected at the Review because inspection drives adaptation, not because stakeholders must approve it. The Product Owner's decisions about the product are visible through the Increment and the backlog, and the Review is where those decisions meet stakeholder feedback — not where permission is granted.
Who attends? The Scrum Team and key stakeholders. The Product Owner has a central role, since the discussion is about progress toward the Product Goal and the future of the Product Backlog. The Developers are there to present what they built and to hear feedback directly. The Scrum Master ensures the event takes place and is positive and productive. Stakeholders are invited because their input shapes what happens next — they are collaborators in the working session, not an audience. The exam sometimes asks whether stakeholders must attend or whether the Review can happen without them: the Guide describes the event as the team presenting to key stakeholders, so a Review with no stakeholders present is missing its purpose, even if it is not formally forbidden.
What gets inspected
Two things are inspected at the Sprint Review: the outcome of the Sprint — the Increment and what was accomplished — and the environment, meaning what has changed since the Sprint began. Markets shift, competitors act, users give feedback, regulations change. The Review is the moment when the team and stakeholders put those two pictures together and decide what to do next. The output is not a document or a sign-off; it is an updated shared understanding and an adapted Product Backlog. The Product Backlog may be adjusted to meet new opportunities discovered during the discussion, which is why the Review is an adaptation event as much as an inspection event. A team that leaves the Review with exactly the same backlog it entered with has either learned nothing or failed to act on what it learned.
Worked scenario
A Scrum Team finishes a Sprint with a working Increment: a new search feature for an online store. At the Sprint Review, the team demonstrates the feature live, and a stakeholder from customer support points out that users have been asking for filters, not just search — and that the search results are confusing without them. The Product Owner notes this, and the team and stakeholders discuss whether filters should become the focus of the next Sprint. The Product Backlog is adjusted to reflect the new understanding. This is the Review working as intended: inspection of the Increment, feedback from stakeholders, adaptation of the backlog. If instead the team had shown slides, received polite applause, and changed nothing, the event would have been a presentation, not a Review — and the opportunity to adapt would have been lost.
Running a good Sprint Review
A good Sprint Review feels like a working session, not a ceremony. The team demonstrates the Increment live, stakeholders try it and give feedback, and the conversation turns to what to do next. Preparation matters: the Product Owner invites the right stakeholders, the Developers prepare a working demonstration rather than slides, and the Scrum Master facilitates so the discussion stays focused on the product rather than drifting into status updates. The Review is also the moment when the Product Backlog is most visibly alive: stakeholders see their feedback turn into reordered or new items, and the Product Owner explains the reasoning behind the ordering. When stakeholders leave a Review understanding what was built, what was learned, and what might happen next, the event has worked. When they leave having watched a presentation, it has not.
Stakeholder collaboration is the Review's deeper purpose. The Product Owner cannot maximize value alone — they need to hear what stakeholders need, what has changed in their world, and how they react to the Increment. The Review is the structured moment for that conversation, but it should not be the only one: the Product Owner talks to stakeholders throughout the Sprint, and the Scrum Master facilitates that collaboration when it is needed. A stakeholder who first sees the product at the Review has been kept too far away; the Review should confirm what they already know from ongoing conversation, not surprise them. The exam tests this through scenarios where stakeholders are ignored or excluded: the correct response always involves bringing them into the conversation, because their feedback is what makes adaptation possible.
Exam traps to watch for
- Treating the Sprint Review as a demo or a presentation. It is a working session; the team should avoid limiting it to a presentation.
- Treating the Review as a sign-off or release gate. An Increment may be delivered before the Sprint ends; the Review should never be considered a gate to releasing value.
- Confusing the Review with the Retrospective. The Review inspects the Increment and the product; the Retrospective inspects the team's way of working.
- Forgetting the timebox: maximum 4 hours for a one-month Sprint, usually shorter for shorter Sprints.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.What is the purpose of the Sprint Review?
Explanation: The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations, with the Scrum Team presenting results to key stakeholders and progress toward the Product Goal discussed. It is not a sign-off gate — the Review should never be considered a gate to releasing value. Inspecting how the team worked is the Retrospective's purpose. Planning the next Sprint's work is Sprint Planning's purpose.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q2.What is the maximum timebox for the Sprint Review for a one-month Sprint?
Explanation: The Sprint Review is timeboxed to a maximum of four hours for a one-month Sprint. Eight hours is Sprint Planning's maximum. Three hours is the Sprint Retrospective's maximum. Fifteen minutes is the Daily Scrum.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q3.Which statement about the Sprint Review is TRUE?
Explanation: The Guide says the Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation. Stakeholders do not vote to accept or reject the Increment. The Developers attend as part of the Scrum Team presenting results. And an Increment may be delivered to stakeholders prior to the end of the Sprint — the Review is not a gate.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q4.During the Sprint Review, stakeholders share that market conditions have changed significantly. What may happen as a result?
Explanation: During the Sprint Review, the Product Backlog may be adjusted to meet new opportunities identified in discussion with stakeholders. A Sprint is cancelled only when the Sprint Goal becomes obsolete, and the Review happens at the end of the Sprint anyway. The Definition of Done is not relaxed because of market changes. And the Sprint Goal of a finished Sprint is not rewritten after the fact.
Exam objective: PSM I Focus Area: Managing Products with Agility — Product Backlog Management
Q5.Who attends the Sprint Review?
Explanation: The Scrum Team presents the results of its work to key stakeholders at the Sprint Review — the whole Scrum Team attends, along with the stakeholders. Limiting it to the Product Owner and stakeholders leaves out the Developers and Scrum Master. The Developers and Scrum Master alone would leave out the Product Owner and stakeholders. And the entire organization is not invited — key stakeholders are.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q6.A team delivers a usable Increment to stakeholders three days before the Sprint ends. Is this allowed?
Explanation: An Increment may be delivered to stakeholders prior to the end of the Sprint, and the Sprint Review should never be considered a gate to releasing value. Delivery does not have to wait for the Review or the Retrospective. And the Scrum Master does not approve deliveries.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Artifacts
Q7.What is discussed at the Sprint Review in relation to the Product Goal?
Explanation: At the Sprint Review, the Scrum Team presents results to key stakeholders and progress toward the Product Goal is discussed. Abandoning the goal is not a routine Review topic — a Product Goal is fulfilled or abandoned only when its objective is met or no longer makes sense. The Product Goal is discussed at the Review, not only annually. And no single team member is responsible for it; it is the team's shared objective.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q8.A Scrum Team's Sprint Review consists of the Product Owner showing slides for 45 minutes while stakeholders listen silently. What is wrong with this?
Explanation: The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation — stakeholders should collaborate on what to do next, not listen passively. The Product Owner presenting is not itself the problem. The Scrum Master does not run the Review. And 4 hours is a maximum, not a required duration.
Exam objective: PSM I Focus Area: Developing People and Teams — Facilitation
Q9.Which event comes immediately AFTER the Sprint Review in a Sprint?
Explanation: The Sprint Review is the second-to-last event of the Sprint; the Sprint Retrospective follows it and concludes the Sprint. Sprint Planning for the next Sprint comes after the Retrospective, at the start of the new Sprint. The Daily Scrum happens every working day, not after the Review specifically. Refinement is an ongoing activity, not an event in the sequence.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events