Use the Sprint Review Canvas as a template to help you and your team run effective Sprint Review events.
The Scrum Guide defines the Sprint Review as a working session … where the Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed…The Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. 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 collaborative working session with the stakeholders. The Scrum team inspects their progress towards the Product Goal and determines what to work on next based on the feedback from stakeholders on the latest Product Increment. The Product Owner updates the Product Backlog accordingly.
The Product Owner kicks off the Sprint Review by recapping the Sprint Goal and how the Product Increment brings the team one step closer to the Product Goal.
Product Backlog Items
The Product Owner then shares the Product Backlog Items that were completed (based on the Definition of Done).
Feedback on the Product Increment
The purpose of the Sprint Review is to get feedback on the Product Increment and determine what to work on next. Developers present the work they accomplished and then let the stakeholders try out the features. Developers observe, answer questions, and gather feedback.
Developers also share the results of any hypothesis they tested in the Sprint and whether they were validated or invalidated. Then the Scrum Team and stakeholders collaborate and identify new opportunities. The Product Owner updates the Product Backlog accordingly.
Feedback on the Product Backlog
The Sprint Review ends with the Product Owner sharing the Product Backlog Items that the team plans to work on next and ensuring that these are the most valuable items to work on.