Retrospective Actions: Start with Why

Getting retrospective actions done can be challenging. To assure that your actions get done my advice is to start with why. Know why you are doing the actions, which problems they will solve, and the benefits they will bring.

It isn’t over when the retrospective meeting is finished. If actions from retrospectives are not done, nothing changes. Which means that you are not getting value from the agile retrospectives.

You have to assure that actions get done to prevent wasting time and money in the retrospective meeting.

Start with Why

Simon Sinek explained in his book Start with Why that to get things done you need to know why you are doing it. Understanding the why intrinsically motivates people and empowers them to take action.

The same is true for agile retrospectives: To successfully do the actions you need to know *why* you are doing them. Truly understanding the problems that a retrospective action aims to solve provides energy and motivates people.

How to know the why

Delivering a list of actions from your retrospective is not enough. Make sure that the team knows why these actions should be done.

Here’s a couple of tips and tricks to know the why of retrospective actions:

  • Describe the purpose or goal of the action, why it matters
  • Define a hypothesis on the impact of the action
  • Quantify the expected outcome, make it measurable
  • Play the angel’s advocate to discuss potential benefits of an action
  • Keep asking why until it’s clear why you should do the action

Use a hypothesis

As mentioned above, one way to know the why is to define a hypothesis which states what the impact of a retrospective action will be. This will not only drive people to do the action; it also helps to verify the results.

If it turns out that the action has delivered the expected result, then you’re ready with it. If not, then it would be good to think about alternative actions that could lead to the required impact.

The hypothesis can also help you to come up with alternative actions, or additional actions that increase the chance that the impact will be successful.

Get actions done

Not having actions done is one of the main reasons why agile teams stop doing retrospectives. If nothing happens after the meeting, why do retrospectives? Make sure that this doesn’t happen with your retrospectives!

Knowing why you are doing the actions significantly increases the chance that the actions get done.

 

About Ben Linders

I help organizations with effective software development and management practices. Active member of several networks on Agile, Lean and Quality, and a frequent speaker and writer.
Tagged , , , , , , , , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

  • Ben Linders – Independent Consultant Agile, Lean, Quality, and Continuous Improvement

    Ben Linders
    Ik help organisaties om effectiever software te ontwikkelen. Neem contact op voor mijn diensten.

    I help organizations to effectively develop software. Contact me to hear about my services.