Scrum guide · Scrum events
Sprint Review: Goal, Agenda and Checklist
The Sprint Review inspects the outcome of the Sprint and determines future adaptations. The Scrum Team presents the results to key stakeholders, and together they discuss progress towards the Product Goal.
Key takeaways
- The Sprint Review inspects the Increment and adapts the Product Backlog.
- It is a working session with stakeholders, not a slide show.
- Demonstrate only work that meets the Definition of Done.
Main purpose
The Sprint Review is a working session, not a presentation. Its goal is to inspect what was done and adapt the Product Backlog based on feedback and changes in the environment. The Scrum Guide warns against limiting it to a presentation.
Who attends and how long
- The Scrum Team and key stakeholders invited by the Product Owner.
- Time-boxed to four hours for a one-month Sprint; usually shorter for shorter Sprints.
Sample agenda
- Welcome and Sprint Goal: what the team set out to achieve.
- What was done, and what wasn't, and why.
- Demonstration of the Increment, ideally hands-on for stakeholders.
- Feedback and questions.
- Changes in the market, budget, timeline or capabilities.
- Discussion of the Product Backlog: what to do next.
- Review of the release forecast or Product Goal progress.
Preparation checklist
- Invite the right stakeholders well in advance.
- Confirm which items meet the Definition of Done; demo only those.
- Prepare a realistic environment for the demonstration.
- Have the Product Backlog and any forecast charts ready.
- Decide who will demonstrate each item.
- Prepare questions you want stakeholders to answer.
Mistakes to avoid
- Demonstrating unfinished work.
- Slide shows instead of working software or results.
- No real stakeholders present.
- Collecting feedback but never updating the backlog.
- Treating it as an approval gate; releases can happen at any time.
Free templates for this topic
Frequently asked questions
What is the difference between a Sprint Review and a demo?
A demo shows work; a Sprint Review also discusses feedback and adapts the Product Backlog.
Who runs the Sprint Review?
The Scrum Team; the Product Owner often leads the discussion about the backlog.
How long is a Sprint Review?
A maximum of four hours for a one-month Sprint. Shorter Sprints usually have shorter Reviews.
Who attends the Sprint Review?
The Scrum Team and key stakeholders, typically invited by the Product Owner.
What is the output of a Sprint Review?
Feedback on the Increment and an adapted Product Backlog, possibly with updated forecasts towards the Product Goal.
Is the Sprint Review a release gate?
No. The Scrum Guide says the Sprint Review should never be considered a gate to releasing value. Increments can be released whenever they are ready.
Should unfinished work be shown at the Sprint Review?
Work that does not meet the Definition of Done is not part of the Increment and should not be presented as done. Teams can mention it when discussing what was and was not completed.
How do you prepare for a Sprint Review?
Invite the right stakeholders, confirm which items meet the Definition of Done, prepare a realistic demo environment and have the Product Backlog and forecasts ready.
What if stakeholders do not attend the Sprint Review?
Find out why, adjust the timing or format, and show them how their feedback changes priorities. Without stakeholders, the event loses most of its value.
Can the Sprint Review be done remotely?
Yes. Share a live demo or let stakeholders try the Increment themselves, and use a shared board to capture feedback and backlog changes.
Who presents at the Sprint Review?
Usually the Developers demonstrate the work they built, and the Product Owner leads the conversation about the Product Backlog and next steps.