# Sprint Review

A collaborative Scrum event where the team and stakeholders inspect the Sprint’s outcome, discuss changing conditions, and adapt what to do next.

- Type: practice
- Domain: Delivery & agility
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/sprint-review/>)

## What it means

The Sprint Review is a working session held near the end of a Sprint to inspect the product Increment and progress toward the Product Goal. The Scrum Team and relevant stakeholders discuss what was achieved, what changed in the environment, and what opportunities or problems deserve attention. The Product Backlog may be adapted as a result.

## Why it matters

A product can meet its specification and still miss the need. Regular review puts usable results, stakeholder knowledge, customer evidence, and market changes in the same conversation. This shortens strategic feedback loops and helps the next decision reflect reality rather than an old plan.

## When to use it

Hold a Sprint Review every Sprint when using Scrum, with people who can contribute useful context or decisions. Show an integrated, usable Increment rather than slideware. Supplement the event with direct customer research and analytics; stakeholders in a review are not automatically representative users.

## How it works

1. Revisit the Product Goal, Sprint Goal, and important changes since the previous review.
2. Inspect the usable Increment and relevant evidence in the context of real workflows.
3. Discuss completed and incomplete outcomes plainly without turning the session into approval theater.
4. Invite stakeholders to contribute customer, operational, commercial, regulatory, and technical insight.
5. Consider progress, new opportunities, risks, and plausible next steps together.
6. Adapt the Product Backlog and follow-up learning while preserving Product Owner accountability.

## A practical example

A logistics team reviews a new delivery-exception workflow with dispatchers, support, and compliance. The Increment works, but dispatchers show that the proposed urgency order conflicts with depot practice. The team changes backlog priorities and schedules field observation before expanding the workflow.

## Where it breaks

A review samples available knowledge; it does not prove customer value or replace research. Senior attendees can suppress candor, and polished demonstrations can hide quality or integration gaps. The event loses purpose when stakeholders only applaud, approve, or request disconnected features.

## Common mistakes

- Running a one-way demonstration with questions saved until the end.
- Showing mockups or unfinished components as though they were a usable Increment.
- Inviting only internal managers and calling their opinions customer feedback.
- Using the event to judge team productivity rather than adapt the product.

## Sources

1. [The Scrum Guide](<https://scrumguides.org/scrum-guide.html>) — Scrum Guides · Official framework guide
2. [What Is Scrum?](<https://agilealliance.org/agile101/scrum>) — Agile Alliance · Professional framework overview
3. [What Is a Sprint Review in Agile?](<https://www.atlassian.com/agile/scrum/sprint-reviews>) — Atlassian · Established practitioner guide

## Related topics

- [Scrum](<https://wiki.soroush.uk/topic/scrum/>)
- [Sprint Planning](<https://wiki.soroush.uk/topic/sprint-planning/>)
- [User Interviews](<https://wiki.soroush.uk/topic/user-interviews/>)
