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.

Hit the Headlines (#119)

Which sprint events were newsworthy?
Source: Thomas Guest
Collect some news headlines in advance and take them to the retrospective to serve as examples. Try to gather a mixture of headlines: factual, opinion, review. Place the headlines where everyone can see them. Hand out sticky notes. Give team members 10 minutes to come up with their own headlines describing newsworthy aspects of the sprint. Encourage short, punchy headlines.
Stick the completed headlines to a whiteboard. If any cover the same news item, combine them. If any are unclear, ask the reporter for details. Vote on which news items to discuss and analyse in more depth.

The Worst We Could Do (#69)

Explore how to ruin the next iteration for sure
Source: Corinna Baldauf
Hand out pens and sticky notes. Ask everyone for ideas on how to turn the next iteration / release into a certain desaster - one idea per note. When everyone's finished writing, hang up all stickies and walk through them. Identify and discuss themes.
In the next phase turn these negative actions into their opposite.

Circle of Questions (#11)

Asking and answering go around the team circle - an excellent way to reach consensus
Source: Agile Retrospectives
Everyone sits in a circle. Begin by stating that you'll go round asking questions to find out what you want to do as a group. You start by asking your neighbor the first question, e.g. 'What is the most important thing we should start in the next iteration?' Your neighbor answers and asks her neighbor a related question. Stop when consensus emerges or the time is up. Go around at least once, so that everybody is heard!

Elevenie (#144)

Write a short poem
Source: Stefanie Dinh
An Elevenie (German 'Elfchen') is a poem with 11 words on five lines – 1, 2, 3, 4 and 1 word per line respectively. Only do this with a team in which people enjoy working with each other. It's a wonderful activity to do with a team that is disbanding at the end of a project as a way to commerate the good times.

Hand out pens and paper and read out the instructions:
'We are going to each write a poem with 5 lines. Each line has a specific number of words. Don't worry, I'll guide you through each line, one by one. Write down 1 word that comes to mind when you think about our team (a feeling, a color, ...).
On the next line, describe this feeling with 2 words.
On the next line, add details with 3 words – What is it like? How does it smell or sound? What would you like to add?
On line 4, write down a sentence with 4 words, starting with 'I'. What do you associate with your feeling.
Take a moment to read your poem thus far. What 1 word comes to mind? This is the final word of your poem on line 5.'

Now you can go around and everybody who wants to, can read out their poem. Bring tissues, it can be quite moving.

(#)


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.