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

Check In - Quick Question (#3)

Ask one question that each participant answers in turn
Source: Agile Retrospectives
In round-robin each participant answers the same question (unless they say 'I pass'). Sample questions:
  • In one word - What do you need from this retrospective?
    When someone answers something that alerts you such as "help" or "protection", you have to react to that e. g. with "Is there something we can do right now to help?" oder "What kind of protection?"
  • What's something that caused problems last iteration?
  • If you could change one thing about the last iteration what would it be?

Avoid evaluating comments such as 'Great'. 'Thanks' is okay.

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.

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?

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!

Feedback Door - Numbers (ROTI) (#14)

Gauge participants' satisfaction with the retro on a scale from 1 to 5 in minimum time
Source: ALE 2011, Corinna Baldauf
Put sticky notes on the door with the numbers 1 through 5 on them. 1 is the topmost and best, 5 the lowest and worst.When ending the retrospective, ask your participants to put a sticky to the number they feel reflects the session. The sticky can be empty or have a comment or suggestion on it.

(#)


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.