Sprint Review
A meeting to demonstrate completed work and gather stakeholder feedback.
Detailed Explanation
The Sprint Review is held at the end of a sprint to inspect the increment and adapt the product backlog. The team demonstrates the work completed during the sprint, and stakeholders provide feedback that shapes future development priorities.
The sprint review is not a formal presentation or sign-off meeting — it is a collaborative working session. The team demos working software (not slides), stakeholders ask questions and provide input, and the Product Owner updates the backlog based on the discussion.
The sprint review provides transparency and enables the inspect-and-adapt cycle at the product level. It ensures the product evolves in a direction that stakeholders value, rather than building features in isolation and hoping they match expectations at the end.
Key Points
- Held at the end of each sprint to inspect the increment
- Team demos working software, not slides or presentations
- Collaborative session — stakeholders provide feedback
- Product Owner adapts the backlog based on feedback
- Provides product-level transparency and inspect-adapt cycle
- Not a formal sign-off — a working session
Practical Example
Sprint Review for an e-commerce app: the team demos the new checkout flow to 12 stakeholders. The marketing VP suggests adding a promo code field (not planned). The CFO asks about payment processing fees. The Product Owner captures the promo code idea as a new backlog item and prioritizes it for Sprint 5. The feedback directly shapes what gets built next.
Tips for Learning and Applying
Demo working software, never slides — stakeholders need to see real functionality
Invite a broad stakeholder group for diverse feedback
Capture feedback as backlog items immediately during the meeting
Keep it informal and interactive — encourage questions and discussion
Want to Master These Concepts?
Our courses cover all these terms in depth with practical examples and exercises.