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.
Are you serious about retrospectives? The Retromat eBook Bundle is here to support you: "Plans for Retrospectives" for beginners, "Run Great Agile Retrospectives" for advanced facilitators and "Asking for a Better Future" on how to energise teams and get better results.

Check out the Retromat eBook Bundle

(And of course there's also 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.

Retro Wedding (#89)

Collect examples for something old, new, borrowed and blue
Source: Jordan Morris, via Todd Galloway
Analogue to an anglo-american wedding custom ask the team to give examples for the following categories:
  • Something Old
    Positive feedback or constructive criticism on established practice
  • Something New
    Positive feedback or constructive criticism on experiments in progress
  • Something Borrowed
    Tool/idea from another team, the Web or yourself for a potential experiment
  • Something Blue
    Any blocker or source of sadness
One example per sticky note. There's only one rule: If someone contributes to the 'Something Blue' column, s/he must also have a positive comment in at least 1 other column.

Everyone posts their stickies in the appropriate column on the board and describes it briefly.

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.

Three by Three (#125)

Build on each other's ideas to create a great action item
Source: Simon Tomes
This silent brainstorming technique helps the team come up with truly creative solutions and gives quiet people equal footing:

  • Everyone writes 3 sticky notes with 1 action idea each
  • Go around the room and pitch each idea in 15 seconds
  • Gather all stickies so that everyone can see them
  • Each team member adds their name to the sticky note that inspires them the most
  • Take off all ideas without a name on them
Repeat this process 2 more times. Afterwards, everyone can dot vote to determine which action(s) the team is going to implement.

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.