Retromat: Agile Post Mortem Structure: 32-133-69-117-15

◄

Emoticon Project Gauge (#32)

Help team members express their feelings about a project and address root causes early
Source: Andrew Ciccarelli

Prepare a flipchart with faces expressing various emotions such as:

shocked / surprised
nervous / stressed
unempowered / constrained
confused
happy
mad
overwhelmed

Let each team member choose how they feel about the project. This is a fun and effective way to surface problems early. You can address them in the subsequent phases.

►

◄

Gather data

Tell me something I don’t know (#133)

Reveal everyone's hidden knowledge with a game show
Source: Adapted by Kai Alexander Lohr

Instruct participants as follows: ‘There’s a game show called ‘Tell me something I don’t know’. In it a guest states a fact, poses a related question and then the hosts ask questions in order to guess the right answers.

Here’s an example: ‘In the US you always sing along to the national anthem. In Spain no one does. Can you guess why?’ The hosts ask questions such as ‘Does it have to do with the Franco era?’, ‘Are the lyrics in a foreign language e.g. Latin?’ etc. They either guess the answer or the guest reveals it (‘The Spanish anthem doesn’t have any lyrics’).

We’re going to play this game now. Each of you will be the guest once with all the others asking questions. Reflect on the past iteration. Use the next 5 minutes to think of a fact and question.’

The fact has to fulfill 3 criteria. Write them down on a board or reveal a pre-written flipchart:

It must be something that only you know and most other team members don’t know (or are unaware of)
It must be worth knowing
It must be actionable, i. e. have the potential to spark anything along the lines of "Let's do more/less of this.", "Watch out this doesn't happen to you.", "That was awesome. Do try it yourself.", ...

Let them write down their fact on an index card. When everyone is ready, ask the first participant to hang up their index card on the board and present their fact and question to the audience. (People who feel uncomfortable with the game flair don’t have to ask a question. They can also just tell the story around their fact without questions from the ‘audience’.) The audience asks questions to guess the answer. Short discussions are okay. The Scrum Master may also ask questions and gently steer the conversation towards possible actions. Document any actions identified during the discussion on the board. Then move on to the next participant. Use about 5 minutes per participant.

Once all the facts have been presented, the team dot-votes which fact fulfilled the 3 criteria best. The winner receives a framed “Certificate of impressive knowledge”. It documents that “$name has impressed $team with their impressive knowledge”.

The facts and actions can be input for "Generate insight" or use the actions for "Decide what to do”.

►

◄

Generate insights

The Worst We Could Do (#69)

Explore how to ruin the next iteration for sure
Source: Corinna Baldauf

Hand out pens and sticky notes. Ask everyone for ideas on how to turn the next iteration / release into a certain desaster - one idea per note. When everyone's finished writing, hang up all stickies and walk through them. Identify and discuss themes.
In the next phase turn these negative actions into their opposite.

►

◄

Decide what to do

Maximize Follow Through (#117)

Think about how the team will follow up and set yourselves up for success
Source: Chris Rimmer

Prepare a flip chart with 4 columns titled 'Action', 'Motivation', 'Ease' and 'Reminder'. Write down the list of actions the team wants to take in the first column. Read out each action and fill in the other columns by asking:

Motivation - How can we motivate ourselves to do this?
Examples: 'Jane will own this and report back at the next retrospective', or 'We'll reward ourselves with cake on Friday if we do this every day'

Ease - How can we make it easy to do?
Example: For an action 'Start involving Simon in the stand up' a possibility could be 'Move the task board next to Simon's desk'

Reminder - How will we remember to do this?
Examples: 'Richard will put a reminder in Google Calendar' or 'We'll do this after the stand up each day'

Actions do not require all of the above. But if there are no suggestions for any of the columns, ask the team if they really think they will do it.

►

◄

Close the retrospective

Appreciations (#15)

Let team members appreciate each other and end positively
Source: Agile Retrospectives who took it from 'The Satir Model: Family Therapy and Beyond'

Start by giving a sincere appreciation of one of the participants. It can be anything they contributed: help to the team or you, a solved problem, ...Then invite others and wait for someone to work up the nerve. Close, when no one has talked for a minute.

►

Emoticon Project Gauge (#32)

Tell me something I don’t know (#133)

The Worst We Could Do (#69)

Maximize Follow Through (#117)

Appreciations (#15)

(#)

Created by Corinna Baldauf

Co-developed by Timon Fiddike