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

Outcome Expectations (#81)

Everyone states what they want out of the retrospective
Source: Inspired by Jim & Michele McCarthy
Everyone in the team states their goal for the retrospective, i.e. what they want out of the meeting. Examples of what participants might say:
  • I'm happy if we get 1 good action item
  • I want to talk about our argument about unit tests and agree on how we'll do it in the future
  • I'll consider this retro a success, if we come up with a plan to tidy up $obscureModule
[You can check if these goals were met if you close with activity #14.]

[The Meet - Core Protocol, which inspired this activity, also describes 'Alignment Checks': Whenever someone thinks the retrospective is not meeting people's needs they can ask for an Alignment Check. Then everyone says a number from 0 to 10 which reflects how much they are getting what they want. The person with the lowest number takes over to get nearer to what they want.]
►
◄
Gather data

4 Ls - Loved, Learned, Lacked, Longed for (#78)

Explore what people loved, learned, lacked and longed for individually
Source: Mary Gorman & Ellen Gottesdiener probably via groupmap.com
Each person brainstorms individually for each of these 4 questions:
  • What I Loved
  • What I Learned
  • What I Lacked
  • What I Longed For
Collect the answers, either stickies on flip charts or in a digital tool if you're distributed. Form 4 subgroups, on for each L, read all notes, identify patterns and report their findings to the group. Use this as input for the next phase.
►
◄
Generate insights

Speed Dating (#26)

Each team member explores one topic in depth in a series of 1:1 talks
Source: Thorsten Kalnin
Each participant writes down one topic they want to explore, i.e. something they'd like to change. Then form pairs and spread across the room. Each pair discusses both topics and ponders possible actions - 5 minutes per participant (topic) - one after the other. After 10 minutes the pairs break up to form new pairs. Continue until everyone has talked to everyone else.
If the group has an odd number of members, the facilitator is part of a pair but the partner gets all 10 minutes for their topic.

(The way to make all the pairings come out even is the following: Form two rows facing each other. This is pairing one. Pick one person. This person's position is fixed the entire time. Everybody else rotates one spot after each pairing.)
►
◄
Decide what to do

Dot Voting - Worked well, Do differently (#39)

Brainstorm what worked well & what to do differently and pick the top initiatives
Source: Agile Retrospectives
Head 2 flip charts with 'Worked well' and 'Do differently next time' respectively. 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.
►
◄
Close the retrospective

Helped, Hindered, Hypothesis (#16)

Get concrete feedback on how you facilitated
Source: Agile Retrospectives
Prepare 3 flip chart papers titled 'Helped', 'Hindered', and 'Hypothesis' (suggestions for things to try out). Ask participants to help you grow and improve as a facilitator by writing you sticky notes and signing their initials so that you may ask questions later.
►
◄

(#)


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.