Topic 4.5 - Sprint Review and Retrospective

Sprint Review 

The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations.

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.

The Product Backlog may also be adjusted to meet new opportunities.

The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation.

The Sprint Review is the second to last event of the Sprint and is timeboxed to a maximum of four hours for a one-month Sprint.

For shorter Sprints, the event is usually shorter in duration.

Sprint Retrospective 

The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.

The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done.

Inspected elements often vary with the domain of work.

Assumptions that led them astray are identified and their origins explored.

The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved.

The Scrum Team identifies the most helpful changes to improve its effectiveness.

The most impactful improvements are addressed as soon as possible.

They may even be added to the Sprint Backlog for the next Sprint.

The Sprint Retrospective concludes the Sprint.

It is timeboxed to a maximum of three hours for a one-month Sprint.

For shorter Sprints, the event is usually shorter in duration.

Techniques for Driving a Retrospective

The 5 Stages of a Retrospective