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.
Plan-ID:
Replaced by JS

Greetings from the Iteration (#85)

Each team member writes a postcard about the last iteration
Source: Filipe Albero Pomar
Remind the team what a postcard looks like:
  • An image on the front,
  • a message on one half of the back,
  • the address and stamp on the other half.
Distribute blank index cards and tell the team they have 10 minutes to write a postcard to a person the whole team knows (i.e. an ex-colleague). When the time is up, collect and shuffle the cards before re-distributing them. Team members take turns to read out loud the postcards they got.

Watermelon (#142)

How is your project really doing?
Source: Sabina Lammert
A disconnect between the actual state of a project and a too positive external view on it, can be dangerous. The longer the disconnect lasts and the wider the gap, the harder it becomes to address: Let’s look for gaps.

In this activity you compare internal and external view on progress and project state. Prepare a flipchart with a large watermelon cut through, red with seeds on the inside, yellow and green rings on the outside. Write “How does our project look internally?” inside the melon and “How does it appear on the outside?” outside of the green ring.

Prepare a second flip chart with some seeds above and caption them “Which bothersome seeds would we like to get rid of?”. Then draw a seedling captioned “What potential can we spot?” lower on the flipchart.

During the retro present the first flipchart and ask the questions. Let participants write their take on sticky notes – 1 comment per note. Then go around with each person reading out their note and posting in the appropriate spot. Have a short discussion on your observations.

Repeat this with the second flipchart and set of questions. In this round, allow more time for more in-depth discussion. If necessary, provide structure with Lean Coffee (#51).

Remember the Future (#37)

Imagine the next iteration is perfect. What is it like? What did you do?
Source: Luke Hohmann, found at Diana Larsen
'Imagine you could time travel to the end of the next iteration (or release). You learn that it was the best, most productive iteration yet! How do your future selves describe it? What do you see and hear?' Give the team a little time to imagine this state and jot down some keywords to aid their memory. Then let everyone describe their vision of a perfect iteration.
Follow up with 'What changes did we implement that resulted in such a productive and satisfying future?'Write down the answers on index cards to use in the next phase.

Circle of Questions (#11)

Asking and answering go around the team circle - an excellent way to reach consensus
Source: Agile Retrospectives
Everyone sits in a circle. Begin by stating that you'll go round asking questions to find out what you want to do as a group. You start by asking your neighbor the first question, e.g. 'What is the most important thing we should start in the next iteration?' Your neighbor answers and asks her neighbor a related question. Stop when consensus emerges or the time is up. Go around at least once, so that everybody is heard!

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