The Sprint Review is one of the five Scrum events — and one of the most misunderstood. In most organisations, it has been silently replaced by a Sprint Demo: a passive presentation of what was built, with stakeholders watching and clapping. This is not a Sprint Review. Here is the difference.
What the Scrum Guide Actually Says
The Scrum Guide describes the Sprint Review as an "inspection of the increment and adaptation of the Product Backlog." The key word is adaptation. A Sprint Review should result in a changed backlog — priorities updated, new items discovered, some items removed.
Sprint Review vs Sprint Demo: The Difference
| Factor | Sprint Demo (anti-pattern) | Sprint Review (correct) |
|---|---|---|
| Format | One-way presentation | Collaborative working session |
| Stakeholder role | Passive audience | Active participants with opinions |
| Output | Sign-off or applause | Updated Product Backlog |
| Backlog discussed? | Rarely | Always |
| Business context shared? | No | Yes — PO shares market, competitive, user context |
| Value assessed? | No | Yes — did we move the needle? |
| Duration (2-week sprint) | 30–45 minutes | Up to 2 hours |
Sprint Review Agenda (The Right Way)
- Context setting (10 min): PO shares business context — what changed since last sprint? New user feedback, competitor moves, market signals. This grounds the increment review in business reality.
- Increment demonstration (20–30 min): Dev Team demonstrates working software on the actual system (not slides, not a staging environment if production is accessible). Stakeholders interact with the product.
- Discussion and questions (15 min): What worked? What surprised us? What is the real user impact? SM facilitates. All voices count — junior engineer observations are as valid as VP opinions.
- Backlog adaptation (20–30 min): PO walks through the next sprint's proposed backlog. Stakeholders ask: Is this still the right priority? What are we missing? What should we stop doing? The backlog is updated live where possible.
- Close (5 min): SM captures decisions. PO confirms updated sprint candidate list.
Signs Your Sprint Review Is Broken
- The same stakeholders attend every review with zero engagement
- No backlog changes result from the event
- The "review" ends 20 minutes before its scheduled close
- The team prepares slides instead of a working increment
- Business decisions are made in Slack the day after rather than in the room
Fixing a Broken Sprint Review
The SM's first move is to secure genuine stakeholder commitment — not just attendance. This requires PO and SM working together to make Sprint Reviews worth attending: relevant context, live product interaction, and genuine influence over backlog direction. When stakeholders know their input changes what gets built next, they show up prepared.