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.]
Give positive, as well as non-threatening, constructive feedback Source:
Inspired by Satu Rekonen
Hang up two flip charts, one headed 'I like' and the other 'I wish'. Give the participants 5-10 minutes to silently write down what they liked about the past iteration and the team and what they wish was different (and how it should be different) – one point per sticky note. When everyone is finished, go around the circle and everybody reads out their 'I like' items and hangs them up. Repeat the same for the 'I wish' stickies. Either debrief or use the stickies as input for the next phase.
What would make the next iteration a perfect 10 out of 10? Source:
Prepare a flip chart with 2 columns, a slim one for 'Rating' and a wide one for 'Actions'. Everyone rates the last iteration on a scale from 1 to 10. Then they have to suggest what action(s) would make the next iteration a perfect 10.
Asking and answering go around the team circle - an excellent way to reach consensus Source:
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!
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.