Beyond Scrum Events - Sprint Review
The main purpose of this event is to elicit transparency and inspect the potential releasable increment - working software - to adapt the Product Backlog on what to do next, not to impress or create excitement or status report.
Even though this event is frequently referred as Sprint Demo, it goes way beyond that.
The Sprint Review includes the following elements:
Attendees include the Scrum Team and key stakeholders invited by the Product Owner;
The Product Owner explains what Product Backlog items have been "Done" and what has not been "Done";
The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved;
The Development Team demonstrates the work that it has "Done" and answers questions about the Increment;
The Product Owner discusses the Product Backlog as it stands. He or she projects likely target and delivery dates based on progress to date (if needed);
The entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning;
Review of how the marketplace or potential use of the product might have changed what is the most valuable thing to do next; and,
Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated releases of functionality or capability of the product.
Prepare for this event upfront but keep it to a minimum and focus on what was the Sprint Goal and the resultant increment. Don’t let this be the first time that your Product Owner is seeing what has been developed. The more the Development Team engages with PO throughout the Sprint, the greater the chance to succeed.
Involve stakeholders and make it useful to everyone. Avoid formal presentation and slides. Use this event to highlight constraints that surpass the team’s self-organisation and are hindering the ability to deliver - more - value to your customers. Get support from stakeholders to address them.
Last but not least, celebrate achievements!