The Sprint Review is the most misunderstood event in Scrum. Teams routinely run it as a slide deck presentation, skip stakeholder collaboration entirely, or confuse it with the Sprint Retrospective. On the PSM I and PSPO I exams, that confusion costs points — often several, because Sprint Review questions test nuances that only make sense once you understand what the event is actually for.
This article breaks down everything the exam tests you on: the purpose, the timebox, who attends, what the output is, why it is not a release gate, and how to keep it cleanly separated from the Sprint Retrospective in your mind.
What the Sprint Review Is — According to the Scrum Guide
The 2020 Scrum Guide defines the Sprint Review with precise language that the exam takes seriously. The full statement:
“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 their work to key stakeholders and progress toward the Product Goal is discussed.”
Two things stand out immediately. First, the purpose is inspection and adaptation — the same empirical pillars that run through every Scrum event. Second, the focus is on the outcome of the Sprint, not just the completed Increment. Progress toward the Product Goal is an explicit topic.
The Scrum Guide goes on:
“During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next. The Product Backlog may also be adjusted to meet new opportunities. The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation.”
That last sentence is the one most teams ignore. The Sprint Review is a working session, not a demo, not a sign-off ceremony. The exam will present you with scenarios where a team treats the Sprint Review as a one-way presentation, and you will need to identify that as a problem.
Timebox and Sequencing
The Sprint Review is the fourth of the five Scrum events (the Sprint being the container for all others). Here is the correct sequence:
- The Sprint — the container event
- Sprint Planning — opens the Sprint
- Daily Scrum — runs each working day
- Sprint Review — second to last event
- Sprint Retrospective — closes the Sprint
The Scrum Guide is explicit: “The Sprint Review is the second to last event of the Sprint and is timeboxed to a maximum of four hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.”
Exam candidates often confuse the timebox lengths. Here is the comparison directly from the 2020 Scrum Guide:
- Sprint Planning: max 8 hours (one-month Sprint)
- Daily Scrum: 15 minutes, every working day
- Sprint Review: max 4 hours (one-month Sprint)
- Sprint Retrospective: max 3 hours (one-month Sprint)
“Timeboxed to a maximum” means the event cannot exceed that duration — it can and often does end sooner. It does not mean the team must fill the entire timebox.
Who Attends the Sprint Review
This is another area the exam tests carefully. The Scrum Guide states that the Scrum Team presents results “to key stakeholders.” Scrum.org’s resource on the Sprint Review clarifies that “attendees include the Scrum Team and key stakeholders invited by the Product Owner.”
Three things to know for the exam:
The entire Scrum Team attends. That means the Developers, the Product Owner, and the Scrum Master — all three accountabilities. The Product Owner is not optional; they are central to the discussion about the Product Backlog and progress toward the Product Goal.
Key stakeholders are invited by the Product Owner. The Scrum Guide does not prescribe a fixed attendee list beyond the Scrum Team. The Product Owner decides which stakeholders are relevant for a given Sprint Review. Exam questions may test whether you recognize this as the Product Owner’s call.
Stakeholders do not attend the Sprint Retrospective. The Sprint Review is the event where external input happens. The Retrospective is a Scrum Team-only event — more on that distinction shortly.
What Actually Happens in a Sprint Review
The 2020 Scrum Guide keeps the Sprint Review description lean and intentionally non-prescriptive. It does not mandate a specific agenda. Scrum.org describes typical elements that help candidates understand the scope of the event:
- The Scrum Team explains which Product Backlog items have been Done and which have not been Done
- The Developers demonstrate completed work and answer questions about the Increment
- The Product Owner discusses the Product Backlog as it currently stands and may discuss projected target dates based on progress to date
- The entire group collaborates on what to do next — providing direct input into the next Sprint Planning
- Changes in the marketplace, environment, or stakeholder needs that affect prioritization are reviewed
The output of the Sprint Review is a revised Product Backlog. As Scrum.org states: “The result of the Sprint Review is a revised Product Backlog that defines the probable Product Backlog items for the next Sprint.” This is not a separate sign-off document or a formal approval. It is a Product Backlog that has been updated based on what was learned during the event.
The Sprint Review Is Not a Release Gate
This is one of the most directly tested concepts on both the PSM I and PSPO I, and it catches candidates who carry assumptions from stage-gate project management into their Scrum study.
The 2020 Scrum Guide is unambiguous: “The Sprint Review should never be considered a gate to releasing value.”
The guide adds: “However, an Increment may be delivered to stakeholders prior to the end of the Sprint.” A Scrum Team does not need to wait until the Sprint Review to release completed work. The decision to release is separate from the Sprint Review event itself. The Sprint Review inspects what was produced and helps adapt the plan — it does not authorize deployment.
Watch for exam questions that ask when a Product Owner may release an Increment. The correct answer is not “only at the Sprint Review” — it is whenever it makes sense, at the Product Owner’s discretion, even within the Sprint.
There is one firm constraint, however: an item that does not meet the Definition of Done cannot be presented at the Sprint Review. The Scrum Guide states: “If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review. Instead, it returns to the Product Backlog for future consideration.”
Incomplete work goes back to the Product Backlog. It does not get a partial presentation. It does not get finished after the review and credited to the Sprint. It simply returns to the backlog for re-ordering and future consideration.
Sprint Review vs. Sprint Retrospective: The Exam’s Favorite Trap
The exam will almost certainly test your ability to distinguish between these two events. The core difference is straightforward:
The Sprint Review is about the product. It involves stakeholders. It inspects the outcome of the Sprint and adapts the Product Backlog. The focus is on what was built, how it advances the Product Goal, and what to build next.
The Sprint Retrospective is about the team. It is a Scrum Team-only event — no stakeholders. It inspects how the team works together and adapts their processes.
The Scrum Guide on the Sprint Retrospective: “The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done.”
The Sprint Retrospective is timeboxed to a maximum of three hours for a one-month Sprint and concludes the Sprint.
Sequence Matters for the Exam
The Sprint Review happens before the Sprint Retrospective. This is intentional. The Scrum Team gathers stakeholder feedback and product-related observations in the Sprint Review, then brings that full context into the Retrospective conversation about how to improve how they work.
A Scenario-Based Example
The PSM I exam frequently uses scenarios to test this distinction. Consider:
During the Sprint Review, the Scrum Team realizes they spent too much time in unnecessary coordination meetings, which slowed their delivery. What should they do?
The Scrum-aligned answer is to note this observation and address it in the upcoming Sprint Retrospective. The Sprint Review is not the forum for discussing how the team worked — that belongs in the Retrospective. Taking team process improvement action inside the Sprint Review is a common wrong option the exam offers.
The Sprint Review and Empiricism
It is worth connecting the Sprint Review to Scrum’s theoretical foundation, because exam questions do this too.
Scrum is built on empiricism: transparency, inspection, and adaptation. The Scrum Guide describes each event as “a formal opportunity to inspect and adapt Scrum artifacts.” The Sprint Review is where this applies to the product: the Scrum Team and stakeholders inspect the actual Increment and actual progress toward the Product Goal, then adapt the Product Backlog based on what they observe — not projections.
The Scrum Guide also notes: “The sum of the Increments is presented at the Sprint Review thus supporting empiricism.” Note the phrasing: “sum of the Increments.” If multiple Increments were produced during the Sprint, all of them — those that meet the Definition of Done — form what is presented. The Sprint Review is not limited to the final item completed.
Quick-Reference Exam Facts
Here are the Sprint Review facts most commonly tested on the PSM I and PSPO I assessments:
- Purpose: Inspect the outcome of the Sprint and determine future adaptations
- Timebox: Maximum 4 hours for a one-month Sprint; shorter for shorter Sprints
- Position: Second to last event of the Sprint; comes before the Sprint Retrospective
- Attendees: The Scrum Team plus key stakeholders invited by the Product Owner
- Output: A revised Product Backlog
- Not a release gate: Increments can be released before the Sprint Review
- DoD constraint: Items not meeting the Definition of Done cannot be presented
- Nature: A working session, not a one-way presentation
- Not for team process: That is the Sprint Retrospective’s purpose
Practice What You Know
The Sprint Review sits at the intersection of two areas where both PSM I and PSPO I exams test heavily: Scrum events and empiricism. Getting this event right means understanding its purpose, its hard constraints, and how it connects to the Retrospective, the Product Backlog, and the next Sprint Planning.
If you want to stress-test your understanding with exam-style questions on the Sprint Review, empiricism, Definition of Done, and the full range of Scrum topics, the PSM I Exam Simulator and the PSPO I Exam Simulator include hundreds of scenario-based questions grounded in the 2020 Scrum Guide. You can also try before you buy — the free PSM I practice test and the free PSPO I practice test are available without registration.