Sprint Review
A Scrum event at the end of each sprint where the team demonstrates completed work to stakeholders, gathers feedback, and discusses next steps.
In-Depth Explanation
The sprint review is an inspection and adaptation opportunity at the end of each sprint. The team demonstrates completed work, stakeholders provide feedback, and the Product Owner updates priorities based on learning.
Structure:
- Sprint goal recap: Remind attendees of the sprint objective
- Demonstration: Show completed work in a working environment (not slides)
- Feedback: Stakeholders ask questions and share reactions
- Backlog update: PO may reprioritise based on feedback
- Next steps: Discuss focus for the upcoming sprint
Who attends:
- Scrum team (PO, SM, Development Team)
- Key stakeholders (sponsors, end users, SMEs)
- Other interested parties
Best practices:
- Demonstrate working deliverables, not presentations
- Focus on whether the sprint goal was achieved
- Encourage stakeholder participation
- Keep it informal and collaborative
- Timebox to 1-2 hours for a 2-week sprint
- Record decisions for backlog updates
Anti-patterns:
- Only showing "happy path" functionality
- Turning review into a formal presentation
- No stakeholders attending
- Feedback being dismissed
Business Context
Sprint reviews provide stakeholders with regular evidence of progress and the opportunity to course-correct based on real results, building confidence and ensuring the product meets actual needs.
How Clever Ops Uses This
Clever Ops holds sprint reviews with Australian clients every two weeks, demonstrating working automations, integrations, and dashboards. This transparent approach ensures clients see real progress and can provide meaningful feedback.
Example Use Case
"During a sprint review, a stakeholder sees the automated report and suggests adding a customer segment filter. The PO adds this to the backlog and prioritises it for the next sprint."