Inspection of the product increment with stakeholders -- demo, feedback, backlog adaptation.
The Sprint Review is the event where the team shows the finished product increment to stakeholders and jointly adapts the Product Backlog based on the feedback received. It takes place at the end of each Sprint, before the Retrospective. The goal is inspection and adaptation: stakeholders see what was built, and the team learns whether it is heading in the right direction.
What matters is that working software is demonstrated, not slides or screenshots. When customers test the new search function live and discover that a price filter is missing, a new backlog item emerges immediately. This direct feedback is more valuable than any requirement written in advance because it is based on actual use. Good Sprint Reviews are interactive: stakeholders can ask questions, try the product themselves, and contribute their priorities for upcoming Sprints.
The Scrum Guide recommends a maximum of four hours for a four-week Sprint. In practice, reviews for shorter Sprints often last 30 to 60 minutes. The most common mistake is treating the Review as a pure demo event instead of using it as a feedback loop.
Apply methods, don't just know them. View trainings and workshops
