Walk through each story handled by the team and look for possible improvements Source:
Preparation: Collect all stories handled during the iteration and bring them along to the retrospective. In a group (10 people max.) read out each story. For each one discuss whether it went well or not. If it went well, capture why. If not discuss what you could do differently in the future. Variants: You can use this for support tickets, bugs or any combination of work done by the team.
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.
Prepare a flip chart with 3 columns titled 'What', 'Who', and 'Due'. Ask one participant after the other, what they want to do to advance the team. Write down the task, agree on a 'done by'-date and let them sign their name. If someone suggests an action for the whole team, the proposer needs to get buy-in (and signatures) from the others.
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.