The Sprint Review is a working session for the stakeholders, users, and customers to collaborate with the Scrum team which includes the Developers, Product Owner, and Scrum Master, and inspect the progress made toward the Product Goal based on the latest Product Increment. The Sprint Review is about getting feedback from the stakeholders and users on the Product Increment and then adapting the Product Backlog accordingly.
In the Sprint Review the team shares with the stakeholders the Sprint goal and the Product Backlog Items the team worked on to deliver on the Sprint Goal and produce the Product Increment. The team might demo the Product Increment or have the stakeholders use it to verify that what they built meets their expectations, that they are on the right track, and that the Increment is useful and valuable. The team verifies that the next items in the Product Backlog are still the most important items to work on or whether they should pivot and work on something else instead. Based on this feedback, the Product Owner adjusts and adapts the Product Backlog accordingly to meet any new opportunities or requirements identified and therefore ensuring that the Scrum team is always working on the most valuable items.
The Sprint Review happens towards the end of the Sprint, involves the entire Scrum team collaborating with the stakeholders and users, and is timeboxed to 4 hours for a 4-week Sprint or 2 hours for a 2-week Sprint, and so on.
And that’s the Sprint Review. A timeboxed event that occurs towards the end of the Sprint for the Scrum team to collaborate with the stakeholders and inspect the Product Increment and the progress being made toward the Product Goal and to adapt the Product Backlog accordingly.
For more details, sign up for an upcoming foundational ScrumMaster® (CSM®) class or a Certified Product Owner® (CSPO®) class or Certified Scrum Developer® (CSD®) class.
Next check out the entire Scrum in a Nutshell series: