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!
Do you want to learn how to facilitate effective retrospectives? Check out our new series for beginners:

New: Corinna's Guide to Facilitating Retrospectives
Retromat.org – by Corinna Baldauf
Plan-ID:
Replaced by JS
◄
Set the stage

Three Words (#82)

Everybody sums up the last iteration in 3 words
Source: Yurii Liholat
Ask everyone to describe the last iteration with just 3 words. Give them a minute to come up with something, then go around the team. This helps people recall the last iteration so that they have some ground to start from.
►
◄
Gather data

Appreciative Inquiry (#65)

Lift everyone's spirit with positive questions
Source: Doug Bradbury, adapted for SW development by Corinna Baldauf
This is a round-based activity. In each round you ask the team a question, they write down their answers (gives everyone time to think) and then read them out to the others.
Questions proposed for Software Development teams:
  1. When was the last time you were really engaged / animated / productive? What did you do? What had happened? How did it feel?
  2. From an application-/code-perspective: What is the awesomest stuff you've built together? What makes it great?
  3. Of the things you built for this company, which has the most value? Why?
  4. When did you work best with the Product Owner? What was good about it?
  5. When was your collaboration best?
  6. What was your most valuable contribution to the developer community (of this company)? How did you do it?
  7. Leave your modesty at the door: What is the most valuable skill / character trait you contribute to the team? Examples?
  8. What is your team's most important trait? What sets you apart?

('Remember the Future' (#37) works well as the next step.)
►
◄
Generate insights

Election Manifesto (#105)

Different parties present manifestos for change. Who will get your vote?
Source: Thomas Guest
Is there an election coming up in your country? Use it as a back drop for your team to convince each other of their change initiatives.

Ask the participants to split into political parties with 2 or 3 members. For 20 minutes, each party will work on a manifesto for change. What isn't working? How would they improve things?
Afterwards the parties meet again and their leaders present their manifestos. Be prepared for tough questions and heckling!
Now plan for a better world! Summarise the manifestos with sticky notes, one color per party. What do the parties agree on? Which promises are unrealistic and which can you achieve?
►
◄
Decide what to do

Systemic Consensus (#103)

Check for resistance instead of approval
Source: Georg Paulus, Siegfried Schrotta \& Erich Visotschnig via Corinna Baldauf
Do you have a hotly debated matter with several possible ways to go and the team can't agree on any of them? Instead of trying to find a majority for a way that will create winners and losers, try what happens if you turn the decision inside out:
Draw a table with the voters in the left-most column and proposals on top. Now everybody has to fill in their resistance towards each proposal. 0 means 'no resistance - this is what I want', up to 10, meaning 'shoot me now'. Give the least hated solution a try.
►
◄
Close the retrospective

My Team is Awesome (#120)

Acknowledge what's awesome about your team
Source: Jesus Mendez
Give each team member a piece of paper and ask them to write down the following text:
'My team is awesome because _______________
and that makes me feel __________________'

Everyone fills out the blanks for themselves and signs below. When everyone is finished, put up the sheets on a wall. A volunteer reads out the sheets and the team celebrates by cheering or applausing. Take some time to review and share observations. Take a picture to remind the team how awesome it feels to be part of the team.
►
◄

(#)


Source:
►
Retromat contains activities, allowing for combinations () 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 Mastodon. 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 trainings for scrum master certification and product owner certification. He also 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. Connect with him on LinkedIn, BlueSky, Mastodon, FB, Insta, Threads.