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

Surprise! (#136)

How do the toys in Kinder Surprise Eggs represent participants?
Source: Unknown via Andreas Drexhage
Prepare by buying a Kinder Surprise Egg (or something similar with a surprise toy inside) for each participant.

Hand out the eggs at the beginning of the retrospective. Eating the chocolate is optional, but everybody needs to open their egg and assemble the toy. Ask “How does your toy represent your role in this iteration?”

Give everyone a minute to think. Then go around the group for everyone to present their toy and how they relate to it.

Proud & Sorry (#33)

What are team members proud or sorry about?
Source: Agile Retrospectives
Put up two posters labeled 'proud' and 'sorry'. Team members write down one instance per sticky note. When the time is up have everyone read out their note and post it to the appropriate poster.
Start a short conversation e.g. by asking:
  • Did anything surprise you?
  • What patterns do you see? What do they mean for you as a team?

Election Manifesto (#105)

Different parties present manifestos for change. Who will get your vote?
Source: Thomas Guest
Is there an election coming up in your country? Use it as a back drop for your team to convince each other of their change initiatives.

Ask the participants to split into political parties with 2 or 3 members. For 20 minutes, each party will work on a manifesto for change. What isn't working? How would they improve things?
Afterwards the parties meet again and their leaders present their manifestos. Be prepared for tough questions and heckling!
Now plan for a better world! Summarise the manifestos with sticky notes, one color per party. What do the parties agree on? Which promises are unrealistic and which can you achieve?

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.

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 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.