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

Who said it? (#106)

Attribute quotes to team members and situations
Source: Beccy Stafford
Before the retro, spend some time looking through email threads, chat logs, ticket discussions, and the like. Collect quotes from the last iteration: Funny quotes, or quotes which without context sound a little odd. Write them down with the name of the person who said them.

Read out the quotes at the beginning of the retro, and ask the team to guess who said it - the source may not self-identify! Often the team will not only know who said it, but also talk about what was going on at the time.

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.

Undercover Boss (#58)

If your boss had witnessed the last iteration, what would she want you to change?
Source: Love Agile
Imagine your boss had spent the last iteration - unrecognized - among you. What would she think about your interactions and results? What would she want you to change?
This setting encourages the team to see themselves from a different angle.

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.

Appreciations (#15)

Let team members appreciate each other and end positively
Source: Agile Retrospectives who took it from 'The Satir Model: Family Therapy and Beyond'
Start by giving a sincere appreciation of one of the participants. It can be anything they contributed: help to the team or you, a solved problem, ...Then invite others and wait for someone to work up the nerve. Close, when no one has talked for a minute.

(#)


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.