In 30 seconds
- Show what's actually done, then discuss what to do next.
- Stakeholders give feedback; the Product Backlog may change.
- Timeboxed to 4 hours for a one-month sprint, less for shorter ones.
A simple agenda
- Recap the Sprint Goal and whether it was met.
- Show the done Increment, ideally letting stakeholders try it.
- Discuss what changed in the market, users or constraints.
- Agree what to look at next; update the Product Backlog.
More than a demo
Many teams call it the demo, or "show and tell". The demo is part of it, but the real point is collaboration: stakeholders and the team deciding together what would be most valuable next.
Review vs Retrospective
| Sprint Review | Sprint Retrospective | |
|---|---|---|
| Inspects | The product | The way of working |
| Who | Team and stakeholders | Scrum team only |
| Output | Updated Product Backlog | Improvements for next sprint |
See Sprint Retrospective.
Myth vs reality
Myth · It's a sign-off meeting.
Reality · It's a feedback session; nothing needs formal approval.
Myth · Show slides about progress.
Reality · Show working software; slides hide what's really done.
Myth · Only finished stories matter.
Reality · Discussing what's next matters as much as showing what's done.
FAQ
Who should attend?
The Scrum team plus key stakeholders: users, customers, sponsors.
What if nothing is done?
Say so honestly; the conversation about why is still valuable.
Should it be recorded for absent stakeholders?
Recordings help, but live feedback is what makes the review work.