Everyone in the team states their goal for the retrospective, i.e. what they want out of the meeting. Examples of what participants might say:
I'm happy if we get 1 good action item
I want to talk about our argument about unit tests and agree on how we'll do it in the future
I'll consider this retro a success, if we come up with a plan to tidy up $obscureModule
[You can check if these goals were met if you close with activity #14.]
[The Meet - Core Protocol, which inspired this activity, also describes 'Alignment Checks': Whenever someone thinks the retrospective is not meeting people's needs they can ask for an Alignment Check. Then everyone says a number from 0 to 10 which reflects how much they are getting what they want. The person with the lowest number takes over to get nearer to what they want.]
Draw a table with 3 columns. Head the first one 'Destination', the second one 'Delay' and the last one 'Announcement'.
Introduce the scenario: 'You are at a train station. Where is your train going? (It can be anything, a fictional or a real place.) How much of a delay does the train currently have? And what is the announcement? Why is there a delay? (This can be a real reason or modeled after the typical announcements.)'
Each team member fills out 3 sticky notes, 1 for each column. Going around the circle, each team member posts their notes and explains briefly, why they're going to destination X and why there's a delay (or not).
Trains and train delays are very familiar in Germany. Depending on your country and culture you might want to pick a different mode of transportation.
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.