Sprint Retrospect

Purpose:

Retrospective meetings are intended to reflect on the most recent sprint/project/milestone and identify areas that need improvement and celebrate team wins.

Objective:

Looking back or dealing with past events or situations.

Description:

At the end of the Sprint, the full Scrum Team comes together to inspect the increment produced. The meeting is informal and intended to elicit high-quality feedback. It is neither a pitch in which the Team attempt to dazzle a critical Product Owner, nor a party at which everyone congratulates themselves on what a great job they did.

The Development Team needs to demonstrate the work that’s been produced, and the Product Owner needs to identify what has been ‘done’ or ‘not-done,’ give feedback (along with that of any other stakeholders) and consider the remaining Product Backlog. The feedback and discussion that follows will form much of the input into the next Sprint Planning Meeting. There can be significant changes of direction or new ideas generated from these meetings which may have a tremendous impact on the rest of the Product Backlog.

RASIC:

Inputs:

• Sprint Burndown Charts

Outputs:

• Sprint Retrospect Meeting Invite
• Documented Actionable items
• Action Plan created
• Sprint Retrospect Meeting Minutes

Controls:

• Sprint Retrospect Meeting Invite
• Techniques to Set the Stage
• Techniques for Gathering Data
• Techniques to Generate Insights
• Techniques to Create Action
• Techniques for Wrap Up
• Stacey complexity model

Task Instructions:

Set the Stage

1. 1. Using the Sprint Retrospect Meeting Invite, [the facilitator] is responsible for scheduling each sprint retrospect meeting.
   2. Using a Set the Stage technique, [the facilitator] with the support from the scrum team, is responsible for getting everyone scrum team members engaged.

Gather Data

1. 1. Using the Sprint Burndown charts, …, [the facilitator] is responsible for informing the scrum team of the data.
   2. Using a technique to Gather Data, [the facilitator], with the support from the scrum team, is responsible for identifying additional data.
   3. Using the data gathered, [the facilitator], with support from the scrum team, is responsible for identifying improvements for the next Sprint.

Generate Insights

1. 1. Using the list of improvements and a Technique to Generate Insights, [the facilitator] with the support from the scrum team is responsible for identifying the top three improvements.
   2. Using the list of the top three improvements, [the facilitator] with the support from the scrum team is responsible for determining the root cause for each of the three items.

Create Actions

1. 1. Using the Stacey Complexity Model, [the facilitator] is responsible for selecting the appropriate management actions in a complex adaptive system based on the degree of certainty and level of agreement for the identified three improvements.
   2. Using the Root Cause Analysis and a Technique to Create Action, [the facilitator] with support from the scrum team is responsible for creating action plans for the three improvements.

Wrap Up

1. 1. Using the Sprint Retrospect Meeting Invite, [the facilitator] is responsible for creating a Sprint Retrospect Meeting Minutes by updating items discussed and action items.
   2. Using the Sprint Retrospect Meeting Minutes, [the facilitator] is responsible for distributing the meeting minutes.