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

Weather Report (#2)

Participants mark their 'weather' (mood) on a flipchart
Source: Agile Retrospectives
Prepare a flipchart with a drawing of storm, rain, clouds and sunshine. Each participant marks their mood on the sheet.

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.

Plus & Delta (#40)

Each participant notes 1 thing they like and 1 thing they'd change about the retro
Source: Rob Bowley
Prepare a flip chart with 2 columns: Head them with 'Plus' and 'Delta'. Ask each participant to write down 1 aspect of the retrospective they liked and 1 thing they would change (on different index cards). Post the index cards and walk through them briefly to clarify the exact meaning and detect the majority's preference when notes from different people point into opposite directions.

(#)


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.