Sprint Reviews and Scrum Events: Purpose, Agenda, and Outputs
Published:
Last Updated:
A Sprint Review brings the Scrum Team and key stakeholders together to inspect the Sprint’s outcome and decide how to adapt. It includes usable results, feedback, and changes in the surrounding environment. Scrum.org emphasizes collaboration rather than a presentation-only meeting. See The Scrum Framework for the wider framework.
Compare the event purposes
Event | Central question | Useful output |
|---|---|---|
Sprint | What can we achieve and learn in this period? | Usable results and evidence |
Sprint Planning | Why is this valuable, what can be done, and how? | A goal, selected work, and plan |
Daily Scrum | What should Developers adjust toward the goal? | An actionable near-term plan |
Sprint Review | What should change because of results and new conditions? | Input to product and backlog decisions |
Retrospective | How should the team improve its working practices? | An improvement experiment |
The Sprint contains the other events. Keep the review’s product discussion distinct from Retrospective Frameworks, which examines the way the team works.
Prepare evidence and decisions
Bring the Sprint Goal, completed work, observed evidence, unfinished scope, and decisions that need discussion. Ticket counts alone rarely tell stakeholders enough about value.
For an application-form improvement, let participants try the result and inspect what is known about user difficulties. If evidence comes from only a few observations, state that limitation instead of presenting it as a proven effect for all users.
A fictional 45-minute agenda
- Five minutes: agree the goal and questions.
- Ten minutes: inspect the usable result.
- Fifteen minutes: discuss feedback and changed conditions.
- Ten minutes: identify options, investigations, and work to defer.
- Five minutes: confirm the record, ownership, and next decision point.
Record field | Illustrative example |
|---|---|
Result | Entries remain after an input error |
Observation | One participant could not find the correction field |
Hypothesis | The route to the field may be unclear |
Next option | Test a more visible error location |
Unknown | The small sample does not establish an effect for all users |
Follow-up | Product Owner considers ordering and brings back the choice |
Stakeholder suggestions are input, not an automatic commitment to put every request into the next Sprint.
Connect review, planning, and daily adaptation
Sprint Planning addresses purpose, selected work, and approach. The Daily Scrum is a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the plan. A three-question format is optional; an actionable plan matters more than reciting a script.
Respect timeboxes and release rules
For a one-month Sprint, Planning has an eight-hour maximum, Review four hours, and Retrospective three hours. Shorter Sprints usually use shorter events. These upper limits differ from the illustrative agenda above.
The review is not a Scrum release gate. Usable work can be released during the Sprint, subject to any separate organizational requirements. Distinguish unfinished work from an Increment that meets the Definition of Done.
Connect the cadence in Sprint Duration and Planning with the surrounding approval process. Xtrategy’s project management features provide context for campaign task progress, costs, and approval information.
