Scrum guide · Scrum events
Sprint Review vs Sprint Retrospective: What's the Difference?
The Sprint Review and Sprint Retrospective both happen at the end of a Sprint, which is why they are often confused. The short version: the Review is about the product; the Retrospective is about the process.
Key takeaways
- Review: product and stakeholders; Retrospective: process and team.
- The Review updates the backlog; the Retrospective creates improvement actions.
- Keep them separate.
Side by side
| Sprint Review | Sprint Retrospective | |
|---|---|---|
| Focus | The product: what was built | The team: how it worked |
| Question | What should we do next? | How can we work better? |
| Attendees | Scrum Team and stakeholders | Scrum Team only |
| Output | Updated Product Backlog | Improvement actions |
| Time-box (1-month Sprint) | Up to 4 hours | Up to 3 hours |
| Order | First | After the Review; concludes the Sprint |
Why both are needed
Without the Review, the team may build the wrong thing efficiently. Without the Retrospective, it may build the right thing inefficiently, and never improve. Together, they apply empiricism to both the product and the process.
Common mix-ups
- Discussing team problems in front of stakeholders at the Review.
- Turning the Retrospective into a product-feedback session.
- Combining both into one meeting and losing depth in each.
Free templates for this topic
Frequently asked questions
Which comes first, the Sprint Review or Retrospective?
The Sprint Review comes first; the Sprint Retrospective concludes the Sprint.
Can stakeholders attend both the Sprint Review and Retrospective?
Stakeholders are key attendees at the Sprint Review. The Retrospective is for the Scrum Team; inviting others can reduce openness, though teams sometimes invite guests for specific topics.
Sprint Review vs Sprint Retrospective: what is the main difference?
The Review inspects the product and adapts the Product Backlog with stakeholders. The Retrospective inspects how the Scrum Team worked and plans improvements.
How long are the Sprint Review and Retrospective?
For a one-month Sprint, the Review is time-boxed to four hours and the Retrospective to three hours. Both are usually shorter for shorter Sprints.
Can the Sprint Review and Retrospective be on the same day?
Yes. Many teams hold the Review and then the Retrospective on the last day of the Sprint, often with a break between them.
What are the outputs of the Sprint Review and Retrospective?
The Sprint Review produces an adapted Product Backlog. The Sprint Retrospective produces improvement actions, some of which may be added to the next Sprint Backlog.
Are the Sprint Review and Retrospective just a demo and a lessons learned?
Broadly, though the Review is more than a demo because it discusses what to do next. The Retrospective is a regular, short-cycle version of lessons learned.
Does the Product Owner attend the Sprint Review and Retrospective?
Yes. The Product Owner is a member of the Scrum Team and takes part in both events.
Which is more important, the Sprint Review or Retrospective?
Neither. The Review ensures the team builds the right thing; the Retrospective ensures it works well. Skipping either weakens empiricism.
Does product feedback belong in the Sprint Review or Retrospective?
In the Sprint Review. If product feedback comes up in a Retrospective, pass it to the Product Owner, who can consider it for the Product Backlog. The Retrospective itself should stay focused on how the team works.
How do the Sprint Review and Retrospective differ from Sprint Planning?
The Review and Retrospective look back, at the Increment and at how the team worked; Sprint Planning looks forward and selects work for the next Sprint. Both feed into Planning: the Review through the adapted Product Backlog and the Retrospective through improvement actions.