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

Check In - Draw the Iteration (#31)

Participants draw some aspect of the iteration
Source: Corinna Baldauf, adapted from Thorsten Kalnin, Olivier Gourment; Thomas Guest
Distribute index cards and markers. Set a topic, e.g. one of the following:
  • How did you feel during the iteration?
  • What was the most remarkable moment?
  • What was the biggest problem?
  • What did you long for?
  • If the last iteration had been a circus performance, what part did you play? Juggler, funambulist, clown, knife-thrower, ...
Ask the team members to draw their answer. Post all drawings on a whiteboard. For each drawing let people guess what it means, before the artist explains it.
Metaphors open new viewpoints and create a shared understanding.

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.

BYOSM - Build your own Scrum Master (#94)

The team assembles the perfect SM & takes different points of view
Source: Fabian Schiller
Draw a Scrum Master on a flipchart with three sections on him/her: brain, heart, stomach.
  • Round 1: 'What properties does your perfect SM display?'
    Ask them to silently write down one trait per note. Let participants explain their notes and put them on the drawing.
  • Round 2: 'What does the perfect SM have to know about you as a team so that he/she can work with you well?'
  • Round 3: 'How can you support your SM to do a brilliant job?'
You can adapt this activity for other roles, e.g. BYOProductOwner.

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.