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

3 for 1 - Opening (#70)

Check satisfaction with iteration results, communication & mood all at once
Source: Judith Andresen
Prepare a flip chart with a co-ordinate plane on it. The Y-axis is 'Satisfaction with iteration result'. The X-axis is 'Number of times we coordinated'. Ask each participant to mark where their satisfaction and perceived touch points intersect - with an emoticon showing their mood (not just a dot).Discuss surprising variances and extreme moods.
(Vary the X-axis to reflect current team topics, e.g. 'Number of times we pair programmed'.)
►
◄
Gather data

Sailboat / Speedboat (#19)

Analyze what forces push you forward and what pulls you back
Source: Luke Hohmann, found at Mike Griffiths
Draw a sailboat (or speedboat) onto a flip chart paper. Give it big sails (motor) as well as a heavy anchor. Team members silently write on sticky notes what propelled the team forward and what kept it in place. One idea per note. Post the stickies to sails (motor) and anchor respectively. Read out each one and discuss how you can increase wind (motor power) and cut anchors.

Variation: Some people add an iceberg in the back of the image. The iceberg represents obstacles they already see coming.
►
◄
Generate insights

5 Whys (#8)

Drill down to the root cause of problems by repeatedly asking 'Why?'
Source: Agile Retrospectives
Divide the participants into small groups (<= 4 people) and give each group one of the top identified issues. Instructions for the group:
  • One person asks the others 'Why did that happen?' repeatedly to find the root cause or a chain of events
  • Record the root causes (often the answer to the 5th 'Why?')
Let the groups share their findings.
►
◄
Generate insights

Perfection Game (#20)

What would make the next iteration a perfect 10 out of 10?
Source: Ben Linders
Prepare a flip chart with 2 columns, a slim one for 'Rating' and a wide one for 'Actions'. Everyone rates the last iteration on a scale from 1 to 10. Then they have to suggest what action(s) would make the next iteration a perfect 10.
►
◄
Close the retrospective

Retro Dart (#83)

Check if you hit bull's eye on important issues
Source: Philipp Flenker
Draw one or several dartboards on a flip chart. Write a question next to each dartboard, e.g.
  • We talked about what's important to me
  • I spoke openly
  • I'm confident we'll improve next iteration
Participants mark their opinion with a sticky. Smack in the middle is 100% agreement. Outside the disc is 0% agreement.
►
◄

(#)


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.