Planning your next agile retrospective? Start with a random plan, change it to fit the team's situation, print it and share the URL. Or browse around for new ideas!

Is this your first retrospective? Start here!
Retromat Miroboard Mega Template
Are you running your retrospectives with Miro? Create prettier boards faster with the giant Retromat Miroboard Mega Template!

Check out the Mega Template
Retromat.org – by Corinna Baldauf
Plan-ID:
Replaced by JS
◄
Set the stage

Check In - Quick Question (#3)

Ask one question that each participant answers in turn
Source: Agile Retrospectives
In round-robin each participant answers the same question (unless they say 'I pass'). Sample questions:
  • In one word - What do you need from this retrospective?
    When someone answers something that alerts you such as "help" or "protection", you have to react to that e. g. with "Is there something we can do right now to help?" oder "What kind of protection?"
  • What's something that caused problems last iteration?
  • If you could change one thing about the last iteration what would it be?

Avoid evaluating comments such as 'Great'. 'Thanks' is okay.
►
◄
Gather data

I like, I wish (#126)

Give positive, as well as non-threatening, constructive feedback
Source: Inspired by Satu Rekonen
Hang up two flip charts, one headed 'I like' and the other 'I wish'. Give the participants 5-10 minutes to silently write down what they liked about the past iteration and the team and what they wish was different (and how it should be different) – one point per sticky note. When everyone is finished, go around the circle and everybody reads out their 'I like' items and hangs them up. Repeat the same for the 'I wish' stickies. Either debrief or use the stickies as input for the next phase.

Variation: Add a third column headed 'I wonder' for things that are puzzling or that they would like to explore.
►
◄
Generate insights

5 Whys (#8)

Drill down to the root cause of problems by repeatedly asking 'Why?'
Source: Agile Retrospectives
Divide the participants into small groups (<= 4 people) and give each group one of the top identified issues. Instructions for the group:
  • One person asks the others 'Why did that happen?' repeatedly to find the root cause or a chain of events
  • Record the root causes (often the answer to the 5th 'Why?')
Let the groups share their findings.
►
◄
Decide what to do

Divide the Dollar (#72)

How much is an action item worth to the team?
Source: Gamestorming
Hang up the list of possible actions. Draw a column next to it, titled 'Importance (in $)'. The team gets to spend 100 (virtual) dollars on the action items. The more important it is to them, the more they should spend. Make it more fun by bringing paper money from a board game such as Monopoly.

Let them agree on prices. Consider the 2 or 3 highest amount action items as chosen.
►
◄
Close the retrospective

Note to Self (#104)

Remind yourself of your good intentions
Source: Fun Retrospectives
Thinking back about the discussions, everybody writes a reminder for her- or himself about a change in their own behaviour they want to try during the next iteration. It's for quiet self reflection and is not shared with the group. They take their respective sticky notes with them to their desktop and put it in a place they will look at often.
►
◄

(#)


Source:
►
Retromat contains 127 activities, allowing for 8349005 combinations (25x30x22x22x23+5) and we are constantly adding more.

Created by Corinna Baldauf

Corinna wished for something like Retromat during her Scrummaster years. Eventually she just built it herself in the hope that it would be useful to others, too. Any questions, suggestions or encouragement? You can email her or follow her on Twitter. If you like Retromat you might also like Corinna's blog and her summaries on Wall-Skills.com.

Co-developed by Timon Fiddike

Timon gives Scrum trainings. He mentors advanced scrum masters and advanced product owners. Human, dad, nerd, contact improv & tango dancer. He has used Retromat since 2013 and started to build new features in 2016. You can email him or follow him on Twitter. Photo © Ina Abraham.