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!

Preparing your first remote retrospective? This might help.
Plan-ID:
Replaced by JS

Postcards (#42)

Participants pick a postcard that represents their thoughts / feelings
Source: Corinna Baldauf
Bring a stack of diverse postcards - at least 4 four times as many as participants. Scatter them around the room and instruct team members to pick the postcard that best represents their view of the last iteration. After choosing they write down three keywords describing the postcard, i.e. iteration, on index cards. In turn everyone hangs up their post- and index cards and describes their choice.

Retro Wedding (#89)

Collect examples for something old, new, borrowed and blue
Source: Jordan Morris, via Todd Galloway
Analogue to an anglo-american wedding custom ask the team to give examples for the following categories:
  • Something Old
    Positive feedback or constructive criticism on established practice
  • Something New
    Positive feedback or constructive criticism on experiments in progress
  • Something Borrowed
    Tool/idea from another team, the Web or yourself for a potential experiment
  • Something Blue
    Any blocker or source of sadness
One example per sticky note. There's only one rule: If someone contributes to the 'Something Blue' column, s/he must also have a positive comment in at least 1 other column.

Everyone posts their stickies in the appropriate column on the board and describes it briefly.

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.

Outside In (#124)

Turn blaming others into actions owned by the team
Source: Ralph Miarka and Veronika Kotrba
If your team has a tendency to see obstacles outside of their team and influence and primarily wants others to change, you can try this activity:

Draw a big rectangle on the board and another rectangle inside of it, like a picture frame. Hang all complaints and grievances that surfaced in previous phases into the frame.

Now comes the interesting twist: Explain that if they want anything in the outside frame to change, they will have to do something themselves to affect that change. Ask the team to come up with actions they can do. Put these actions into the inner rectangle (near the outer sticky they are addressing).

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. As Integral Coach and Agile Coach he coaches executives, managers, product owners and scrum masters. 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.