Retromat: Lessons Learned Agenda Guide: 36-133-50-125-15

◄

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

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

Wish granted (#50)

A fairy grants you a wish - how do you know it came true?
Source: Lydia Grawunder & Sebastian Nachtigall

Give participants 2 minutes to silently ponder the following question: 'A fairy grants you a wish that will fix your biggest problem at work overnight. What do you wish for?' Follow up with: 'You come to work the next morning. You can tell, that the fairy has granted your wish. How do you know? What is different now?' If trust within the group is high, let everyone describe their 'Wish granted'-workplace. If not, just tell the participants to keep their scenario in mind during the next phase and suggest actions that work towards making it real.

►

◄

Decide what to do

Three by Three (#125)

Build on each other's ideas to create a great action item
Source: Simon Tomes

This silent brainstorming technique helps the team come up with truly creative solutions and gives quiet people equal footing:

Everyone writes 3 sticky notes with 1 action idea each
Go around the room and pitch each idea in 15 seconds
Gather all stickies so that everyone can see them
Each team member adds their name to the sticky note that inspires them the most
Take off all ideas without a name on them

Repeat this process 2 more times. Afterwards, everyone can dot vote to determine which action(s) the team is going to implement.

►

◄

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.

►

Appreciative Goal (#36)

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

Wish granted (#50)

Three by Three (#125)

Appreciations (#15)

(#)

Created by Corinna Baldauf

Co-developed by Timon Fiddike