One of the last events held at the end of the sprint. It is about to inspect the Increment and adapt the product backlog.
According to Scrum Guide: “During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done to optimize value. This is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration.”
To keep it short the following process has been put in place: aim for doing as much as possible preparation work individually before the meeting than limit the review meeting to the Increment and the Demo.
Pre-review activities:
- Classify bugs and turn them into Stories if needed
- Ensure all Stories / Tasks are up to date and reflects the reality
- Prepare for Demo
Review:
- Product Owner presents to the Dev Team and Stakeholders the items which were “Done”
- Devs give tiny product demos (short, focused, non-technical)
- Product Owner explains how the business priorities have been changed based on the outcome of the Sprint
Items “In progress” will be moved to the next Sprint as soon as the current one is closed and the next one gets opened; it happens at the same.
The next and the last event is the Retro; the inspection and adaptation of Sprint activities in regard to people, relationships, process, and tools. Remember the review is about what has been done during the sprint and the retro is about the how.