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

Last Retro's Actions Table (#84)

Assess how to continue with last retro's actions
Source: Sven Winkler
Create a table with 5 columns. The first column lists last retro's action items. The other columns are headed 'More of', 'Keep doing', 'Less of' and 'Stop doing'. Participants place 1 sticky note per row into the column that states how they want to proceed with that action. Afterwards facilitate a short discussion for each action, e.g. asking:
  • Why should we stop doing this?
  • Why is it worth to go further?
  • Are our expectations satisfied?
  • Why do opinions vary that much?
►
◄
Gather data

Laundry Day (#98)

Which things are clear and feel good and which feel vague and implicit?
Source: Katrin Dreyer
Use this activity if you suspect the team to make lots of unconscious decisions hardly ever questioning anything. You can figure out what things need to be talked about to get an explicit grasp of them.

You need:
  • about 3 metres of string as the clothesline
  • about 20 clothes pins
  • a white shirt (cut from paper)
  • a pair of dirty pants (cut from paper)
Hang up the clothesline and mark the middle, e.g. with a ribbon. Hang up the clean shirt on one side and the dirty pants on the other. Ask the team now to write items onto index cards for each of the two categories: 'Clean - Clear and well understood' and 'Dirty - Unclear and confusing'. Hang up the notes with clothespins and re-arrange them into clusters. Now the team picks 2 'dirty' and 2 'clean' topics they want to talk about, e.g. by dot voting.
►
◄
Generate insights

Braver (#145)

What does courage look like? What would the team do if they were bolder?
Source: Johanna Amlacher
Put up four posters with the following questions:
  • Which person in the team do you find courageous and how does courage show itself?
  • When have you felt insecure and wished you were braver?
  • What helps you to be brave?
  • What bold idea would you try as a team if you were 10 times bolder?
For each question do a round of:
  • 4 minutes of quiet time to answer the question on sticky notes
  • Ask people to read out and post their answers. (In a large group you can use 1-2-4-All to discuss answers in smaller groups first.)
  • Cluster similar answers
(We do it in several rounds to slowly warm up the participants to tackle the last question.)

After the last round, look at all the answers and facilitate a discussion. Ask participants what is standing out for them? What's unexpected? What patterns do they see? What do these patterns mean for them as a team?

Then ask the team to rate themselves on a scale of 1-10: How brave do they think they are? Followed by: What would be possible if they were one step higher on the scale?

Based on everything they’ve talked about, what would they like to try that’s somewhat bold yet safe enough?
►
◄
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

Helped, Hindered, Hypothesis (#16)

Get concrete feedback on how you facilitated
Source: Agile Retrospectives
Prepare 3 flip chart papers titled 'Helped', 'Hindered', and 'Hypothesis' (suggestions for things to try out). Ask participants to help you grow and improve as a facilitator by writing you sticky notes and signing their initials so that you may ask questions later.
►
◄

(#)


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 trainings for scrum master certification and product owner certification. He also 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. Connect with him on LinkedIn, BlueSky, Mastodon, FB, Insta, Threads.