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.]
Brainstorm what to repeat and what behaviours to avoid Source:
Head 2 flip charts with 'Repeat' and 'Avoid' respectively. The participants write issues for the columns on sticky notes - 1 per issue. You can also color code the stickies. Example categories are 'People', 'Process', 'Technology', ... Let everyone read out their notes and post them to the appropriate column. Are all issues unanimous?
Find the source of problems whose origins are hard to pinpoint and lead to endless discussion Source:
Write the problem you want to explore on a sticky note and put it in the middle of a whiteboard. Find out why that is a problem by repeatedly asking 'So what?'. Find out the root causes by repeatedly asking 'Why (does this happen)?' Document your findings by writing more stickies and showing causal relations with arrows. Each sticky can have more than one reason and more than one consequence Vicious circles are usually good starting points for actions. If you can break their bad influence, you can gain a lot.
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!
Gauge participants' satisfaction with the retro on a scale from 1 to 5 in minimum time Source:
ALE 2011, Corinna Baldauf
Put sticky notes on the door with the numbers 1 through 5 on them. 1 is the topmost and best, 5 the lowest and worst.When ending the retrospective, ask your participants to put a sticky to the number they feel reflects the session. The sticky can be empty or have a comment or suggestion on it.