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).
Each participant tells a story about the last iteration that contains certain words Source:
Provide everyone with something to write down their story. Then introduce the shaping words, which influence the story to be written:
If the last iteration could have been better: You set a couple of shaping words, e.g. such as 'mad, sad, glad' or 'keep, drop, add'. Additionally they have to write their story in first person. This avoids blaming others.
If the last iteration was successful: The team can either choose their own set of words or you can provide random words to unleash the team's creativity.
Now each participant writes a story of no more than 100 words about last iteration. They have to use each shaping word at least once. Timebox this to 5-10 minutes. When everyone's finished, they read out their stories. Afterwards lead a discussion about common themes of the stories.
Split a large group into smaller ones that create posters Source:
Unknown, adapted by Corinna Baldauf, inspired by Michal Grzeskowiak
After you've identified an important topic in the previous phase you can now go into detail. Have the larger group split up into groups of 2-4 people that will each prepare a poster (flip chart) to present to the other groups. If you have identified more than one main topic, let the team members select on which they want to work further. Give the teams guidelines about what the posters should cover / answer, such as:
What exactly happens? Why is that a problem?
Why / when / how does this situation happen?
Who benefits from the current situation? What is the benefit?
Possible solutions (with Pros and Cons)
Who could help change the situation?
... whatever is appropriate in your setting ...
The groups have 15-20 minutes to discuss and create their posters. Afterwards gather and each group gets 2 minutes to present their results.
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.