Sprint review
- In Agile
- by fixture-author
- Published
- Reading time
The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations.
During the event, the Team review what was accomplished in the Sprint. Based on this information, attendees collaborate on what to do next. The Product Backlog may also be adjusted to meet new opportunities. The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation.
Structure | The Scrum Master takes on the logistics of event preparation. The Product Owner should ask stakeholders questions to gather as much feedback as possible. They should also answer any of their stakeholder’s questions. |
Attendees | Development Team, Scrum Master, Product Owner. Optionally, management, customers, developers, and other stakeholders |
When | At the end of the sprint |
Duration | max 2,5% – 1h/week |
Outcomes | After this ceremony, the Product Owner might need to adjust or add to the product backlog. They might also release product functionality if it’s already complete. |