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.
There's a new Retromat book geared towards beginners!

Check out "Plans for Retrospectives"

(Looking for the Print Retromat?)
Plan-ID:
Replaced by JS

Give me a face (#114)

Participants show how they feel by drawing a face on a tangerine
Source: Afagh Zadeh
Each team member gets a sharpie and a tangerine with a sticky note asking: 'How do you feel? Please give me a face'. After all are done drawing you go around and compare the works of art and emotions. It's a light-hearted way to set the stage.

Story Oscars (#54)

The team nominates stories for awards and reflects on the winners
Source: Marin Todorov
Display all stories completed in the last iterations on a board. Create 3 award categories (i.e. boxes on the board):
  • Best story
  • Most annoying story
  • ... 3rd category invented by the team ...
Ask the team to 'nominate' stories by putting them in one of the award boxes.
For each category: Dot-vote and announce the winner. Ask the team why they think the user story won in this category and let the team reflect on the process of completing the tasks - what went good or wrong.

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