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.
NEW: Look, there's a free (mini) ebook "Asking for a Better Future" on how to energise teams and get better results – during retrospectives and other conversations – with solution-focussed questions.

It's the latest addition to the Retromat eBook Bundle, complementing "Plans for Retrospectives" for beginners and "Run great agile retrospectives" for advanced facilitators:

Check out the Retromat eBook Bundle

(And of course there's also the Print Retromat.)
Plan-ID:
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.

Proud & Sorry (#33)

What are team members proud or sorry about?
Source: Agile Retrospectives
Put up two posters labeled 'proud' and 'sorry'. Team members write down one instance per sticky note. When the time is up have everyone read out their note and post it to the appropriate poster.
Start a short conversation e.g. by asking:
  • Did anything surprise you?
  • What patterns do you see? What do they mean for you as a team?

Force Field Analysis (#115)

Analyse the factors that support and hinder a particular initiative
Source: Derek Neighbors, via Joel Edwards
State the topic that the team will explore in depth (deployment processes, peer-programming, Definition of Done, ...). Break the room into groups of 3-4 people each. Give them 5-7 minutes to list all contributing factors, drivers and actions that make up the topic. Go around the room. Each group reads 1 of their sticky notes and puts it up inside the force field until no group has any items left. Cluster or discard duplicates. Repeat the last 2 steps for factors that inhibit or restrain the topic from being successful or being as effective as it could be. Review all posted items. Add any that are missing.

To identify the most influential factors, everybody gets to 4 votes - 2 for contributing factors, 2 for inhibitors. Tally the votes and mark the top 2x2 factors with big arrows. Spend the last 15-20 mins of the session brainstorming ways to increase the top driving factors and decrease the top restraining factors.

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.