by The Scrum framework consists of Scrum Teams and their associated accountabilities, artifacts, events and rules as defined in the Scrum Guide.
Scrum events
Sprint Review definition
- Sprint Review is a mandatory event of Scrum and is about the Product.
- Sprint Review is a meeting for presenting the Increment for feedback and collaboration.
- The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.
Sprint Review purpose
- The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations :
- Eliciting feedback from the Stakeholders and Customers is the main purpose of the Sprint Review :
- The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations if needed.
- Sprint Review is a mandatory event of Scrum and is a feedback loop that Developers demonstrate the Increment to the Stakeholders and elicit feedback from them in order to determine likely Product Backlog Items (PBIs) for the next Sprint.
- Sprint Review serves the Scrum Team and the Stakeholder to inspect the Increment of the Product resulting from the Sprint, asses the impact of the work on the progress, and update the Product Backlog to maximize value for the next period.
Sprint Review topics
- The most important topics in this event are :
- Inspect the Increment through showing it by the Developers and try it by stakeholders and customers in order to elicit feedback
- Check how the current Sprint went and if the Sprint Goal was achieved or not
- Adapt Product Backlog through the Team and stakeholders’ collaboration to nominate things that can be done during the next Sprint
- The Product Owner explains the project status and last forecast of the project completion date
- Stakeholders collaborate with the Team to adjust the budget, inspect market status and every project level interested things
- Sprint Review is an informal meeting and there is not any hand-off / sign-off in it.
Sprint Review value
- The multiple feedbacks are the value given by the Sprint Review.
Sprint Review results
- The result of the Sprint Review is that the Product Backlog is revised to defines the probable Product backlog Items (PBIs) for the next Sprint.
Sprint Review time-boxing
- Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed.
- The Sprint Review is the second to last event of the Sprint and is timeboxed to a maximum of four hours for a one-month Sprint.
- Sprint Review is a time-boxed event of 4 hours, or less, to conclude the development work of a Sprint.
- The Sprint Review is at most a four-hour meeting for one-month Sprints, or shorter for shorter Sprint.
- It should be conducted at the end of each Sprint before the Sprint Retrospective.
Sprint Review participants
- Participants of the Sprint Review are all Scrum Team members plus key Stakeholders invited by the Product Owner :
- Product Owner
- Key Stakeholders
- Developers
- Scrum Master
- Key Stakeholders
- Because the Product Owner is responsible for ROI and has the most knowledge on what the complete objectives are for a product, the Product Owner should lead the Sprint Review. [Agile Project Management with Scrum. Ken Schwaber.]
- The Key Stakeholders are allowed to participate only in the Sprint Review meeting.
- Stakeholders are actively engaged with the Scrum Team at the Sprint Review meeting.
- However, any member of the Scrum Team can interact with them any time.
Sprint Review practice
- During the event, the Scrum Team and Stakeholders review what was accomplished in the Sprint and what has changed in their environment.
- The Scrum Team and Stakeholders collaborate about what was done in the Sprint.
- The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.
- In the Sprint Review the Developers demonstrate the work that is has “Done” and answers questions about the Increment.
- In the Sprint Review Developers discusses what went well concerning the Product during the Sprint, any problems had, and how they were solved.
- During the event, the Scrum Team and Stakeholders review what was accomplished in the Sprint and what has changed in their environment.
- The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.
- In the Sprint Review, the Scrum Team explains what Product Backlog items have been “Done” or not “Done.”
- Based on this information, attendees collaborate on what to do next.
- Based on what was done in a sprint and any changes to the Product Backlog during the Sprint, attendees of this meeting collaborate on the next things items to do for optimized value.
- During this meeting attendees take into account what was done during the Sprint, and any changes to the Product Backlog, in order to collaborate what items to do next for optimized value.
- In the Sprint Review everyone collaborates on what to do next, in order to provide valuable input to the subsequent Sprint Planning meeting.
- The Product Backlog may also be adjusted to meet new opportunities.
- Also, the last forecasted project end date, budget, market status, new capabilities, and insights about the project could be discussed.
- The Product Owner explains the project status and last forecast of the project completion date.
- In the Sprint Review, PO projects the likely target and delivery dates for the Product Backlog as it stands.
- Key Stakeholders collaborate with the Team to adjust the budget, inspect market status and every project level interested things.
- In this meeting event the marketplace/potential use of the product is reviewed in order to asses what is the most the most valuable thing to do next.
- In this meeting the timeline, budget, potential capabilities, and market place for the next anticipated releases of functionality/capability are reviewed.
- In the Sprint Review, the Scrum Team and stakeholders collaborate on adapting the Product Owner to nominate things that can be done during the next Sprint.
- The Product Owner explains the project status and last forecast of the project completion date.
- The Scrum Team and Stakeholders collaborate about what was done in the Sprint.
- Sprint review is a working session :
- The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation
- Fundamentally the Sprint Review is an Inspect and Adapt loop, not just a demo meeting
- Sprint Review is an informal meeting, not a status meeting
- Sprint Review is an informal meeting and there is not any hand-off / sign-off in it
- Sprint Review feedbacks :
- If the feedbacks are good, the Product Owner may validated the Increment, so no much work is needed for the choosen Product Backlog items, and these PBIs are removed from the Product Backlog.
- If the feedbacks are not good, the Product Owner may not validated the Increment, so much work is needed for the choosen Product Backlog items, and these PBIs are not removed from the Product Backlog, some new PBIs may be added for fixing bugs or modify the Increment.
- At the end of the Sprint Review, based on the feedbacks the Product Owner give a new updated version of the Product Backlog.
- Product Owner (PO) tracks total work remaining in at least every Sprint Review.
- The amount of work remaining is compared by the Product Owner with the previous reviews to assess progress.
More informations for the Scrum PSD certification here.
Updated : 03/09/2021
