Blog | Books | Membership | About
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.
There's a new Retromat book geared towards beginners!

Check out "Plans for Retrospectives"

(Looking for the Print Retromat?)
Replaced by JS

ESVP (#1)

How do participants feel at the retro: Explorer, Shopper, Vacationer, or Prisoner?
Source: Agile Retrospectives
Prepare a flipchart with areas for E, S, V, and P. Explain the concept:
  • Explorer: Eager to dive in and research what did and didn't work and how to improve.
  • Shopper: Positive attitude. Happy if one good things comes out.
  • Vacationer: Reluctant to actively take part but the retro beats the regular work.
  • Prisoner: Only attend because they (feel they) must.
Take a poll (anonymously on slips of paper). Count out the answers and keep track on the flipchart for all to see. If trust is low, deliberately destroy the votes afterwards to ensure privacy. Ask what people make of the data. If there's a majority of Vacationers or Prisoners consider using the retro to discuss this finding.

Avoid Waste (#135)

Tackle the 7 Wastes of Software Development
Source: Tony O'Halloran
This activity facilitates a broad discussion around waste, using the 7 Wastes of Software Development from Lean Software Development by Mary and Tom Poppendieck.

Prepare the room with 7 flip-chart sheets, each representing a category of waste. Be sure to give enough room for small groups to stand around them, so spread the sheets out across the room!

The 7 categories of waste are:
  1. Partially Done Work
    Is work going from beginning to end in a single rapid flow? For example; are you building up large amounts of untested or undeployed work? Do you have long-lived feature branches?
  2. Extra Features
    Do your customers or users actually need what you’re building?
  3. Relearning
    Do you spend a lot of time rediscovering what you (or someone else on your team) already knew at one time?
  4. Handoffs
    Is your team truly collaborating, or handing off bits of work to each other, losing tacit knowledge in the process?
  5. Delays
    Does work typically spend lots of time stalled awaiting things like environments, someone to be available, or decisions to be made?
  6. Task Switching
    Do you find that you lose time to context switching frequently?
  7. Defects
    Does your team have a low defect rate? How late in the development process do you find defects? Could this feedback loop be shorter?
To start, briefly describe each of the different types of waste (more in-depth information here). Then pose the core questions:

In which situations do we incur this type of waste?
Where do we do a good job of avoiding this type of waste?

Break into groups of 2-3 people, preferably with a mix of roles in the groups. This helps to build awareness of the waste everyone else is dealing with on your team. Then, each group selects their first topic and spends a short amount of time writing post-its to answer the two questions above. Limit it to 2 or 3 minutes per topic and 2 post-its per person for each topic to avoid getting swamped with data. When the timebox is up, each group cycles to the next category until everyone has had an opportunity to contribute to each.

What themes are emerging? What do participants notice? Use dot-voting to decide which topics are important enough to further discuss in the next phase.

5 Whys (#8)

Drill down to the root cause of problems by repeatedly asking 'Why?'
Source: Agile Retrospectives
Divide the participants into small groups (<= 4 people) and give each group one of the top identified issues. Instructions for the group:
  • One person asks the others 'Why did that happen?' repeatedly to find the root cause or a chain of events
  • Record the root causes (often the answer to the 5th 'Why?')
Let the groups share their findings.

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.

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.