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

Appreciative Goal (#36)

State an affirmative goal for the session
Source: Diana Larsen
Concentrate on positive aspects instead of problems by setting an affirmative goal, e.g.
  • Let's find ways to amplify our strengths in process and teamwork
  • Let's find out how to extend our best uses of engineering practices and methods
  • We'll look at our best working relationships and find ways to build more relationships like that
  • We'll discover where we added the most value during our last iteration to increase the value we'll add during the next
►
◄
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

If I were you (#95)

What could sub-groups improve when interacting with others?
Source: Thomas Wallet
Identify sub-groups within the participants that interacted during the iteration, e.g. developers/testers, clients/providers, PO/developers, etc. Give participants 3 minutes to silently write down what they think their group did that negatively impacted another group. One person should be part of one group only and write stickies for all groups they don't belong to - 1 sticky per issue.

Then in turn all participants read their stickies and give them to the corresponding group. The affected group rates it from 0 ('It was not a problem') to 5 ('It was a big problem'). Thus you get insights and shared understanding about problems and can select some of them to work on.
►
◄
Decide what to do

Merge (#21)

Condense many possible actions down to just two the team will try
Source: Lydia Grawunder & Sebastian Nachtigall
Hand out index cards and markers. Tell everyone to write down the two actions they want to try next iteration - as concretely as possible (SMART). Then everyone pairs up with their neighbor and both together must merge their actions into a single list with two actions. The pairs form groups of 4. Then 8. Now collect every group's two action items and have a vote on the final two.
►
◄
Close the retrospective

Debriefing Cube (#138)

Close with a reflective question from the Debriefing Cube and cards
Source: Chris Caswell and Julian Kea
A good debriefing deepens understanding, learning and sharing. Preparation: Download and assemble the Debriefing Cube and cards. During the retrospective, roll the cube. Then draw a card from the category it shows and use it to prompt a discussion. Repeat as time permits. This will broaden your debriefing options and is especially great for groups without a facilitator to enable them to effectively debrief on their own.
►
◄

(#)


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.