Scrum: Sprint Review

• What: Event held at the end of every Sprint to inspect the Increment and adapt the Product Backlog if needed.
• Who: Scrum Team, Stakeholders.
• When: At end of each sprint, before sprint planning. Approx. 2 hours for a 2-week sprint.

• Product Owner describes the goals for the sprint and associated backlog items. The PO discusses what Product Backlog items were successfully delivered to “Done” and any that were not “Done”.
• Development Team demonstrates the work that it has “Done” and answers questions about the Increment.
• Product Owner discusses the overall Product Backlog as it stands, (or,  status of the overall Program Backlog for that team if the sprint was completed in the context of a SAFe PI program for example). He or she might discuss upcoming goals based on progress to date. 
• The entire group collaborates on what to do next, Sprint Review provides input to subsequent Sprint Planning.
• Review of the timeline, budget, features, and marketplace for the next anticipated releases of the product.

• Feedback from stakeholders on demonstrated features/stories, and potential changes to product backlog.
• Team and stakeholders aligned on progress, issues and near-term direction.

The SAFe framework recommends holding a system-level demo at the end of each iteration, the focus of which is to demo completed features or end-to-end operation of a system, whereas the typical focus of the sprint review is on completed user stories. One major practical challenge is going to be getting stakeholders to commit to sitting through multiple team-level demos and then an additional system-level demo. The best option, in practical terms, might be to hold a single event, where all teams from the ART demonstrate their completed work, and then have a demonstration any new system-level functionality at the end. Having all teams and all stakeholders in the same place at the same time can help ensure that critical feedback is received and acted upon.