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

Check out the Mega Template
Plan-ID:
Replaced by JS

Who said it? (#106)

Attribute quotes to team members and situations
Source: Beccy Stafford
Before the retro, spend some time looking through email threads, chat logs, ticket discussions, and the like. Collect quotes from the last iteration: Funny quotes, or quotes which without context sound a little odd. Write them down with the name of the person who said them.

Read out the quotes at the beginning of the retro, and ask the team to guess who said it - the source may not self-identify! Often the team will not only know who said it, but also talk about what was going on at the time.

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

Poster Session (#91)

Split a large group into smaller ones that create posters
Source: Unknown, adapted by Corinna Baldauf, inspired by Michal Grzeskowiak
After you've identified an important topic in the previous phase you can now go into detail. Have the larger group split up into groups of 2-4 people that will each prepare a poster (flip chart) to present to the other groups. If you have identified more than one main topic, let the team members select on which they want to work further.
Give the teams guidelines about what the posters should cover / answer, such as:
  • What exactly happens? Why is that a problem?
  • Why / when / how does this situation happen?
  • Who benefits from the current situation? What is the benefit?
  • Possible solutions (with Pros and Cons)
  • Who could help change the situation?
  • ... whatever is appropriate in your setting ...
The groups have 15-20 minutes to discuss and create their posters. Afterwards gather and each group gets 2 minutes to present their results.

Dot Voting - Start, Stop, Continue (#12)

Brainstorm what to start, stop & continue and pick the top initiatives
Source: Agile Retrospectives
Divide a flip chart into boxes headed with 'Start', 'Continue' and 'Stop'. Ask your participants to write concrete proposals for each category - 1 idea per index card. Let them write in silence for a few minutes. Let everyone read out their notes and post them to the appropriate category. Lead a short discussion on what the top 20% beneficial ideas are. Vote on it by distributing dots or X's with a marker, e.g. 1, 2, and 3 dots for each person to distribute. The top 2 or 3 become your action items.

(Check out Paulo Caroli's 'Open the Box' for an awesome variation of this activity.)

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.