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!

Preparing your first remote retrospective? This might help.
Plan-ID:
Replaced by JS

Weather Report (#2)

Participants mark their 'weather' (mood) on a flipchart
Source: Agile Retrospectives
Prepare a flipchart with a drawing of storm, rain, clouds and sunshine. Each participant marks their mood on the sheet.

Back to the Future (#141)

You take the DeLorean back to the beginning of the project
Source: Dominik Panzer
This activity is great for looking at a longer period of time. Put on your storyteller hat and ask your team to imagine the following scenario:

"You are sitting relaxed at your computer working, when suddenly there is a loud bang and a huge cloud of dust is in your room. You cough and as the dust settles, you realize that a car has driven through the wall of your house. You approach cautiously to see what has happened. The car looks futuristic and has gullwing doors. You wipe the dust off the windshield and realize: it's Marty McFly with his DeLorean. He seems unharmed, but is unconscious. You sense your chance and gently push Marty into the passenger seat. The time machine seems to be undamaged. You risk it and travel back to the beginning of your project: Greenfield. Not a single line of code has been written yet. Now you have the possibility to start again from scratch:
  • What do you definitely keep?
  • What do you do differently this time?
  • What were your biggest learnings?"
Give everybody 7 minutes to write down their ideas on sticky notes – 1 idea per sticky. When the time is up, the first person briefly presents their stickies for the first category and posts them on the board for this category. Then the second person presents and so on. Cluster as you go along. What themes do appear?

Repeat for the other two categories.

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.

Dot Voting - Keep, Drop, Add (#38)

Brainstorm what behaviors to keep, drop & add and pick the top initiatives
Source: Agile Retrospectives
Divide a flip chart into boxes headed with 'Keep', 'Drop' and 'Add'. Ask your participants to write concrete proposals for each category - 1 idea per index card. Let them write in silence for a few minutes. Let everyone read out their notes and post them to the appropriate category. Lead a short discussion on what the top 20% beneficial ideas are. Vote on it by distributing dots or X's with a marker, e.g. 1, 2, and 3 dots for each person to distribute. The top 2 or 3 become your action items.

Feedback Door - Numbers (ROTI) (#14)

Gauge participants' satisfaction with the retro on a scale from 1 to 5 in minimum time
Source: ALE 2011, Corinna Baldauf
Put sticky notes on the door with the numbers 1 through 5 on them. 1 is the topmost and best, 5 the lowest and worst.When ending the retrospective, ask your participants to put a sticky to the number they feel reflects the session. The sticky can be empty or have a comment or suggestion on it.

(#)


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. As Integral Coach and Agile Coach he coaches executives, managers, product owners and scrum masters. 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.