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!
Retromat Miroboard Mega Template
Are you running your retrospectives with Miro? Create prettier boards faster with the giant Retromat Miroboard Mega Template!

Check out the Mega Template
Retromat.org – by Corinna Baldauf
Plan-ID:
Replaced by JS
◄
Set the stage

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.
►
◄
Gather data

Quartering - Identify boring stories (#64)

Categorize stories in 2 dimensions to identify boring ones
Source: Wayne D. Grant
Draw a big square and divide it into 2 columns. Label them 'Interesting' and 'Dull'. Let the team write down everything they did last iteration on stickies and put it into the appropriate column. Have them add a rough estimate of how long it took on each of their own stickies.
Now add a horizontal line so that your square has 4 quadrants. Label the top row 'Short' (took hours) and the bottom row 'Long' (took days). Rearrange the stickies in each column.
The long and dull stories are now nicely grouped to 'attack' in subsequent phases.

(Splitting the assessment into several steps, improves focus. You can adapt Quartering for lots of other 2-dimensional categorizations.)
►
◄
Generate insights

The Worst We Could Do (#69)

Explore how to ruin the next iteration for sure
Source: Corinna Baldauf
Hand out pens and sticky notes. Ask everyone for ideas on how to turn the next iteration / release into a certain desaster - one idea per note. When everyone's finished writing, hang up all stickies and walk through them. Identify and discuss themes.
In the next phase turn these negative actions into their opposite.
►
◄
Decide what to do

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!
►
◄
Close the retrospective

Feedback Door - Numbers (ROTI) (#14)

Gauge participants' satisfaction with the retro on a scale from 1 to 5 in minimum time
Source: ALE 2011, Corinna Baldauf
Put sticky notes on the door with the numbers 1 through 5 on them. 1 is the topmost and best, 5 the lowest and worst.When ending the retrospective, ask your participants to put a sticky to the number they feel reflects the session. The sticky can be empty or have a comment or suggestion on it.
►
◄

(#)


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.