Place a circle or sphere in the middle of a free space. Let the team gather around it. Explain that the circle is the center of approval: If they agree to a statement they should move towards it, if they don't, they should move as far outwards as their degree of disagreement. Now read out statements, e.g.
I feel I can talk openly in this retrospective
I am satisfied with the last iteration
I am happy with the quality of our code
I think our continuous integration process is mature
Watch the constellations unfold. Ask questions about people's observations, such as which constellations were surprising. This can also be a closing activity (#53).
Set up a 'retrospective mailbox' at the beginning of the iteration. Whenever something significant happens or someone has an idea for improvement, they write it down and 'post' it. (Alternatively the 'mailbox' can be a visible place. This can spark discussion during the iteration.) Go through the notes and discuss them. A mailbox is great for long iterations and forgetful teams.
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.