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!
Are you running your retrospectives with Miro? Create prettier boards faster with the giant Retromat Miroboard Mega Template!

Check out the Mega Template
Plan-ID:
Replaced by JS

Outcome Expectations (#81)

Everyone states what they want out of the retrospective
Source: Inspired by Jim & Michele McCarthy
Everyone in the team states their goal for the retrospective, i.e. what they want out of the meeting. Examples of what participants might say:
  • I'm happy if we get 1 good action item
  • I want to talk about our argument about unit tests and agree on how we'll do it in the future
  • I'll consider this retro a success, if we come up with a plan to tidy up $obscureModule
[You can check if these goals were met if you close with activity #14.]

[The Meet - Core Protocol, which inspired this activity, also describes 'Alignment Checks': Whenever someone thinks the retrospective is not meeting people's needs they can ask for an Alignment Check. Then everyone says a number from 0 to 10 which reflects how much they are getting what they want. The person with the lowest number takes over to get nearer to what they want.]

Lean Coffee (#51)

Use the Lean Coffee format for a focused discussion of the top topics
Source: Original description and in action
Say how much time you set aside for this phase, then explain the rules of Lean Coffee for retrospectives:
  • Everyone writes down topics they’d like to discuss - 1 topic per sticky
  • Put the stickies up on a whiteboard or flipchart. The person who wrote it describes the topic in 1 or 2 sentences. Group stickies that are about the same topic
  • Everyone dot-votes for the 2 topics they want to discuss
  • Order the stickies according to votes
  • Start with the topic of highest interest
  • Set a timer for 5 minutes. When the timer beeps, everyone gives a quick thumbs up or down. Majority of thumbs up: The topic gets another 5 minutes. Majority of thumbs down: Start the next topic.
Stop when the allotted time is over.

Cause-Effect-Diagram (#25)

Find the source of problems whose origins are hard to pinpoint and lead to endless discussion
Source: Henrik Kniberg
Write the problem you want to explore on a sticky note and put it in the middle of a whiteboard. Find out why that is a problem by repeatedly asking 'So what?'. Find out the root causes by repeatedly asking 'Why (does this happen)?' Document your findings by writing more stickies and showing causal relations with arrows. Each sticky can have more than one reason and more than one consequence
Vicious circles are usually good starting points for actions. If you can break their bad influence, you can gain a lot.

Systemic Consensus (#103)

Check for resistance instead of approval
Source: Georg Paulus, Siegfried Schrotta \& Erich Visotschnig via Corinna Baldauf
Do you have a hotly debated matter with several possible ways to go and the team can't agree on any of them? Instead of trying to find a majority for a way that will create winners and losers, try what happens if you turn the decision inside out:
Draw a table with the voters in the left-most column and proposals on top. Now everybody has to fill in their resistance towards each proposal. 0 means 'no resistance - this is what I want', up to 10, meaning 'shoot me now'. Give the least hated solution a try.

Feedback Door - Smilies (#23)

Gauge participants' satisfaction with the retro in minimum time using smilies
Source: Boeffi
Draw a ':)', ':|', and ':(' on a sheet of paper and tape it against the door. When ending the retrospective, ask your participants to mark their satisfaction with the session with an 'x' below the applicable smily.

(#)


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.