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!
Retromat Miroboard Mega Template
Are you running your retrospectives with Miro? Create prettier boards faster with the giant Retromat Miroboard Mega Template!

Check out the Mega Template
Retromat.org – by Corinna Baldauf
Plan-ID:
Replaced by JS
◄
Set the stage

Greetings from the Iteration (#85)

Each team member writes a postcard about the last iteration
Source: Filipe Albero Pomar
Remind the team what a postcard looks like:
  • An image on the front,
  • a message on one half of the back,
  • the address and stamp on the other half.
Distribute blank index cards and tell the team they have 10 minutes to write a postcard to a person the whole team knows (i.e. an ex-colleague). When the time is up, collect and shuffle the cards before re-distributing them. Team members take turns to read out loud the postcards they got.
►
◄
Gather data

Roles and Responsibilities (#146)

Clarify expectations and responsibilities for each role on the team
Source: Role-Up
Many conflicts arise from unclear expectations. Talking about individual people can feel like an attack. That’s why this activity focusses on expectations towards roles.

Create a table with one column per role in the team. (Limit it to 7 columns. If there are more than 7 roles, leave out roles that have little conflict.) The rows of the table are: 

  • Role name
  • This role is responsible for …
  • This role is NOT responsible for …
Leave enough space between the bottom rows so that people who aren’t sure whether something is a role’s responsibility have an unofficial inbetween space to post them. Hand out pens, as well as yellow and orange sticky notes.

Ask everyone to write yellow sticky notes listing the responsibilities for each role – 1 responsibility per note. Set a timer for 8 minutes and read the room to see if you can stop early or have to give more time. Post all the sticky notes but don’t discuss them yet.

Repeat this process with the non-responsibilities on orange sticky notes.

The team now dot-vote on which topics they want to talk about. Give enough time to read all the sticky notes and distribute 7 votes.

Start with the topic with the most votes. Invite the people who voted for it to share why they want to talk about it. Try to clarify expectations team members have about a role’s responsibilities. Write down clarifications or agreements the team make. Repeat for the next highest voted topic until time runs out.
►
◄
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

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.)
►
◄
Close the retrospective

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.