Sprint Review Explained: Purpose, Participants and Scrum Master Role

The Sprint Review is held near the end of the Sprint. The Scrum Team and stakeholders inspect what was achieved and discuss what should happen next.

It is not simply a demonstration or a status meeting. It is a collaborative opportunity to inspect the product outcome and adapt future work.

Purpose of the Sprint Review

The main purpose is to inspect the outcome of the Sprint and use what was learned to decide what to do next.

Inspect the outcome → Gather feedback → Adapt the Product Backlog

Who Participates?

The Sprint Review involves:

  • Scrum Team
  • Stakeholders
  • Other relevant people who can provide useful feedback or information.

The Product Owner is responsible for ensuring the right stakeholders are involved in the discussion.

What Happens During a Sprint Review?

1. Inspect the Sprint Outcome

The team discusses what was accomplished during the Sprint and inspects the resulting Increment.

2. Discuss Changes

The team and stakeholders discuss changes in the product environment, customer needs, market conditions or other factors that may affect future work.

3. Gather Feedback

Stakeholders can provide feedback and share information that may influence future Product Backlog decisions.

4. Discuss What Comes Next

Based on what has been learned, the Product Backlog may be adjusted and the team can discuss likely next steps.

Is the Sprint Review Just a Demo?

No.

A demonstration of the Increment can be part of the Sprint Review, but the event is broader than showing completed work.

The important part is the conversation around the product, feedback, value and what should happen next.

Remember:

A demo shows what was built. A Sprint Review helps the Scrum Team and stakeholders decide what should happen next.

Simple Example

Imagine a team has improved the checkout process of an online shopping application.

During the Sprint Review, the team demonstrates the usable Increment and discusses the results with stakeholders.

Stakeholders point out that customers are still abandoning the payment page because a particular payment option is missing.

The Product Backlog can then be adapted based on this feedback.

What Is the Scrum Master's Role?

The Scrum Master helps ensure the Sprint Review takes place and helps participants understand its purpose.

The Scrum Master can also facilitate useful collaboration when needed, but should avoid turning the event into a presentation controlled by one person.

Common Mistakes

Only a Demo Showing completed features without meaningful discussion.
Status Reporting Reporting project progress instead of inspecting the product outcome.
No Stakeholder Feedback Inviting stakeholders but not involving them in the conversation.
No Adaptation Finishing the review without considering what should change next.

Key Takeaway

The Sprint Review connects the Scrum Team with stakeholders and helps ensure that future work remains aligned with product needs and changing circumstances.

What Comes Next?

The final Scrum event in our current sequence is the Sprint Retrospective, where the Scrum Team focuses on improving how it works.