What is the Sprint Review?

Question

Accepted Answer

The Sprint Review is held **at the end of the Sprint to inspect the Increment and adapt the Product Backlog**. The Scrum Team and stakeholders look at what was built, discuss what changed in the market or business, and decide what to do next. It is a working session, not a one-way presentation.

## How it works

```text
- The team demonstrates the working Increment (Done items only)
- Stakeholders give feedback and ask questions
- The Product Owner discusses backlog status and likely next steps
- The group collaborates on what is most valuable to do next
```

It is time-boxed to a maximum of four hours for a one-month Sprint.

## Concrete example

The team demos a working checkout flow. A stakeholder notices the order confirmation email is missing, so the Product Owner adds it as a high-priority item for the next Sprint.

## Common pitfalls

- Demoing slideware or half-finished work instead of a working Increment.
- Treating it as a sign-off gate rather than a feedback conversation.
- Confusing it with the Retrospective — the Review is about the *product*, the Retrospective about the *process*.

## Why it matters

The Review closes the feedback loop with real stakeholders, ensuring the team builds what is actually valuable.

Adapting the backlog here is how Scrum stays responsive to change instead of marching to an outdated plan.