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

Check In - Quick Question (#3)

Ask one question that each participant answers in turn
Source: Agile Retrospectives
In round-robin each participant answers the same question (unless they say 'I pass'). Sample questions:
  • In one word - What do you need from this retrospective?
    When someone answers something that alerts you such as "help" or "protection", you have to react to that e. g. with "Is there something we can do right now to help?" oder "What kind of protection?"
  • What's something that caused problems last iteration?
  • If you could change one thing about the last iteration what would it be?

Avoid evaluating comments such as 'Great'. 'Thanks' is okay.

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

Learning Matrix (#9)

Team members brainstorm in 4 categories to quickly list issues
Source: Agile Retrospectives
After discussing the data from Phase 2 show a flip chart with 4 quadrants labeled ':)', ':(', 'Idea!', and 'Appreciation'. Hand out sticky notes.
  • The team members can add their input to any quadrant. One thought per sticky note.
  • Cluster the notes.
  • Hand out 6-10 dots for people to vote on the most important issues.
This list is your input for Phase 4.

Dot Voting - Worked well, Do differently (#39)

Brainstorm what worked well & what to do differently and pick the top initiatives
Source: Agile Retrospectives
Head 2 flip charts with 'Worked well' and 'Do differently next time' respectively. 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.

Take a Stand - Closing (#44)

Participants take a stand, indicating their satisfaction with the retrospective
Source: Corinna Baldauf, inspired by Christoph Pater
Create a big scale (i.e. a long line) on the floor with masking tape. Mark one end as 'Great' and the other as 'Bad'. Let participants stand on the scale according to their satisfaction with the retrospective. Ask people what they notice.
Psychologically, taking a stand physically is different from just saying something. It's more 'real'.
See activity #43 on how to begin the retrospective with the same scale.

(#)


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.