Sprint Review: Inspect the Increment

Overview

• What you’ll learn: The purpose of the Sprint Review, how it differs from a demo, stakeholder participation, and how the Product Backlog is adapted based on feedback.
• Prerequisites: Lesson 20 — Daily Scrum.
• Estimated reading time: 12 minutes

Introduction

The Sprint Review is the second-to-last event of the Sprint. It is where the Scrum Team presents the Increment to stakeholders and inspects the outcome of the Sprint. The key word is “inspect” — this is not a presentation; it is a working session where feedback drives Product Backlog adaptation.

Sprint Review vs. Demo Day

What Happens During the Sprint Review

• The Scrum Team presents the Increment — what was Done and what was not.
• Stakeholders inspect the Increment and provide feedback.
• The Product Owner discusses the Product Backlog — what has been done, what remains, and potential future direction.
• The group collaborates on what to do next, providing input for Sprint Planning.
• The Product Backlog may be adjusted to meet new opportunities.

Timebox

The Sprint Review is timeboxed to a maximum of four hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.

Key Takeaways

• The Sprint Review inspects the Increment and adapts the Product Backlog based on feedback.
• It is a collaborative working session, not a demo or presentation.
• Stakeholder feedback drives Product Backlog adaptation.
• If stakeholders are just clapping, you are missing the point: feedback.
• Timeboxed: 4 hours max for a 1-month Sprint.

What’s Next

In Lesson 22, you will explore the Sprint Retrospective — Scrum’s most important ceremony for continuous improvement.