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

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.

Mad Sad Glad (#7)

Collect events when team members felt mad, sad, or glad and find the sources
Source: Agile Retrospectives
Put up three posters labeled 'mad', 'sad', and 'glad' (or >:(, :(, :) alternatively). Team members write down one event per color coded card, when they've felt that way. When the time is up have everyone post their cards to the appropriate posters. Cluster the cards on each poster. Ask the group for cluster names.
Debrief by asking:
  • What's standing out? What's unexpected?
  • What was difficult about this task? What was fun?
  • What patterns do you see? What do they mean for you as a team?
  • Suggestions on how to continue?

Lean Coffee (#51)

Use the Lean Coffee format for a focused discussion of the top topics
Source: Original description and in action
Say how much time you set aside for this phase, then explain the rules of Lean Coffee for retrospectives:
  • Everyone writes down topics they’d like to discuss - 1 topic per sticky
  • Put the stickies up on a whiteboard or flipchart. The person who wrote it describes the topic in 1 or 2 sentences. Group stickies that are about the same topic
  • Everyone dot-votes for the 2 topics they want to discuss
  • Order the stickies according to votes
  • Start with the topic of highest interest
  • Set a timer for 5 minutes. When the timer beeps, everyone gives a quick thumbs up or down. Majority of thumbs up: The topic gets another 5 minutes. Majority of thumbs down: Start the next topic.
Stop when the allotted time is over.

SMART Goals (#13)

Formulate a specific and measurable plan of action
Source: Agile Retrospectives
Introduce SMART goals (specific, measurable, attainable, relevant, timely) and examples for SMART vs not so smart goals, e.g.'We'll study stories before pulling them by talking about them with the product owner each Wednesday at 9am' vs. 'We'll get to know the stories before they are in our sprint backlog'.
Form groups around the issues the team wants to work on. Each group identifies 1-5 concrete steps to reach the goal. Let each group present their results. All participants should agree on the 'SMART-ness' of the goals. Refine and confirm.

Debriefing Cube (#138)

Close with a reflective question from the Debriefing Cube and cards
Source: Chris Caswell and Julian Kea
A good debriefing deepens understanding, learning and sharing. Preparation: Download and assemble the Debriefing Cube and cards. During the retrospective, roll the cube. Then draw a card from the category it shows and use it to prompt a discussion. Repeat as time permits. This will broaden your debriefing options and is especially great for groups without a facilitator to enable them to effectively debrief on their own.

(#)


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.