Retromat: Scrum Post Mortem Directory: 85-97-8-11-138

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.

#tweetmysprint (#97)

Produce the team's twitter timeline for the iteration
Source: Thomas Guest

Ask participants to write 3 or more tweets on sticky notes about the iteration they've just completed. Tweets could be on the iteration as a whole, on individual stories, a rant, or shameless self-promotion - as long as they are brief. Hash tags, emoticons, attached pictures, @usernames are all welcome. Allow ten minutes to write the tweets, then arrange them in a timeline and discuss themes, trends etc. Now invite participants to favorite, retweet and write replies to the tweets, again following up with discussion.

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.

Circle of Questions (#11)

Asking and answering go around the team circle - an excellent way to reach consensus
Source: Agile Retrospectives

Everyone sits in a circle. Begin by stating that you'll go round asking questions to find out what you want to do as a group. You start by asking your neighbor the first question, e.g. 'What is the most important thing we should start in the next iteration?' Your neighbor answers and asks her neighbor a related question. Stop when consensus emerges or the time is up. Go around at least once, so that everybody is heard!

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.

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.