As a Scrum Master, what has been your biggest struggle? I struggled to create a culture of continuous improvement within the team. And you might think what is to struggle there, run a Sprint Retrospective and get your improvements, so easy or is it?

Let me ask a few questions/statements and see if any of it resonates with you.

  • Does your Retrospective follows (all the time) the template
    • What went well?
    • What did not go well?
    • What are the improvements?
  • There is a huge list of identified improvements, but nothing is implemented.
  • Team members typically during the Retrospective are not energized or just go through the motions of it.
  • After the retrospective, no one knows what the improvement work on which the team was supposed to work.
  • Typically, team members do not have any context about what we will do in the Sprint Retrospective besides answering the questions mentioned above; i.e., they do not understand the event’s purpose.
  • You haven’t yet heard about the “Prime Directive” for Sprint Retrospective.

 

If you can resonate with all or any of that, you are in the same boat I was a few years ago when I started my journey as a Scrum Master.

So, how do we change this for you? Well, you don’t have to go through the same mistakes to learn to do things differently. Here I am sharing what I did to improve my retrospectives. The first thing was to read the book “Agile Retrospectives” by Esther Derby and Diana Larsen. Before we get into more ways of improving your retrospective, let’s first start by understanding what a retrospective is.

What is Sprint Retrospective:

When we think of the word “retrospect,” it means to do a review of a past course of events, which is the base for a Sprint Retrospective. In a Sprint Retrospective, we review the past Sprint and its events, intending to identify how we can make the upcoming Sprint better.

From the recent version of the Scrum Guide (scrum guide 2020):

The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.
A few more details: A Sprint Retrospective is the last event on the Sprint, time-boxed for 3 hours or less for a month Sprint. During the event, the Scrum Team collaborates and reflects on the past Sprint concerning people, process, tools, interactions, and the Definition of Done. The Scrum Team also identifies how to improve and make the next sprint effective and meaningful.

Tips to Improve Your Retrospective

Tips to Improve Your Sprint Retrospective

To improve your retrospectives, you need to structure it well. Here is what I learned from “Agile Retrospectives.”

Step 1: Set the context
Step 2: Gather Data
Step 3: Generate Insights
Step 4: Decide what to do
Step 5: Conclude

Step 1: Set the Context

This helps everyone to know the purpose of the Retrospective and create an environment where everyone feels comfortable to speak. It also allows us to set the rules, guidelines, and approach for the retrospective. We can also highlight any specific challenge that the team has brought up and would like to address.

How I do it:

  1. Explicitly talk about the Prime Directive for Sprint Retrospective.
  2. Layout the rules such as – timebox for the event, everyone to respect the opinions of others.

Explain the method we will use for Retrospective – ex: 5 Whys and Fishbone

Step 2: Gather Data

Now that we have set the context, the next step is to gather some data by reflecting on the Sprint gone by. This helps us to make fact-based, empirical decisions.

How I do it:

  1. Walkthrough the burn-down and probe what does it tell?
  2. Look into quality metrics, technical debt, etc.
  3. Look at planned versus actual PBIs completed.
  4. I also ask subtle questions like – how did everyone feel during the Sprint? – allow them time to consider the question and share silently.

Step 3: Generate Insights

With the data assembled, we start generating insights, correlating causes and effects. What are the typical patterns or anti-patterns that we observed in the Sprint? How has it impacted our effectiveness? And so on.

How I do it:

  1. 5 Why analysis is a great way to generate insights
  2. I use another method to divide a sheet of paper into 6 columns marked as – Start, Stop, Less, More, Keep, and WIIFM (What’s In It For Me?)

Step 4: Decide what to do

This about identifying your actionable items, which would help the team to improve its efficacy.

How I do it:

  1. List down all the possible improvements/experiments that we can run in the next sprint.
  2. Use the “Dot Voting” technique to order them.
  3. The one with the highest votes finds a way into our Sprint Backlog.
  4. The team decides the possible course of action to implement the improvement.
  5. Ask team members to volunteer to be accountable for the improvement.

Step 5: Conclude

This is the last part of the retrospective, where we tie up all the loose ends. This part should be utilized to appreciate the team’s efforts, reminding everyone of the actionable improvement, who would be accountable for it, and capturing all these learnings and insights. We usually also take quick feedback on the retrospective itself.

How I do it:

  1. Start by re-affirming the prime directive.
  2. A note of thank you.
  3. Ask if anyone wants to appreciate their team members.
  4. Quick feedback on the retrospective so that I can improve it for the next session.
  5. Wrap up with reiterating the improvement and person accountable for it.

I hope this article was helpful, and you have found some insights to make your retrospectives better.

Author's Bio
Piyush Rahate

Piyush Rahate

An enabler; helping teams in their journey to pursue agility. I believe that happy teams build happy products. Build teams around motivated individuals is my daily mantra. He is having having fifteen years of experience in the industry and have donned various roles earlier.