Retromat: Inspect & Adapt Event Activities: 85-133-91-38-44

◄

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.

►

◄

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

Poster Session (#91)

Split a large group into smaller ones that create posters
Source: Unknown, adapted by Corinna Baldauf, inspired by Michal Grzeskowiak

After you've identified an important topic in the previous phase you can now go into detail. Have the larger group split up into groups of 2-4 people that will each prepare a poster (flip chart) to present to the other groups. If you have identified more than one main topic, let the team members select on which they want to work further.
Give the teams guidelines about what the posters should cover / answer, such as:

What exactly happens? Why is that a problem?
Why / when / how does this situation happen?
Who benefits from the current situation? What is the benefit?
Possible solutions (with Pros and Cons)
Who could help change the situation?
... whatever is appropriate in your setting ...

The groups have 15-20 minutes to discuss and create their posters. Afterwards gather and each group gets 2 minutes to present their results.

►

◄

Decide what to do

Dot Voting - Keep, Drop, Add (#38)

Brainstorm what behaviors to keep, drop & add and pick the top initiatives
Source: Agile Retrospectives

Divide a flip chart into boxes headed with 'Keep', 'Drop' and 'Add'. Ask your participants to write concrete proposals for each category - 1 idea per index card. Let them write in silence for a few minutes. Let everyone read out their notes and post them to the appropriate category. Lead a short discussion on what the top 20% beneficial ideas are. Vote on it by distributing dots or X's with a marker, e.g. 1, 2, and 3 dots for each person to distribute. The top 2 or 3 become your action items.

►

◄

Close the retrospective

Take a Stand - Closing (#44)

Participants take a stand, indicating their satisfaction with the retrospective
Source: Corinna Baldauf, inspired by Christoph Pater

Create a big scale (i.e. a long line) on the floor with masking tape. Mark one end as 'Great' and the other as 'Bad'. Let participants stand on the scale according to their satisfaction with the retrospective. Ask people what they notice.
Psychologically, taking a stand physically is different from just saying something. It's more 'real'.
See activity #43 on how to begin the retrospective with the same scale.

►

Greetings from the Iteration (#85)

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

Poster Session (#91)

Dot Voting - Keep, Drop, Add (#38)

Take a Stand - Closing (#44)

(#)

Created by Corinna Baldauf

Co-developed by Timon Fiddike