Ask each team member to briefly describe how their right neighbour felt during the iteration. Their neighbour confirms or corrects the guess. Once all participants shared their best guess about how their teammates felt, you get an idea of how connected they are, how communication is flowing in your team and if people are aware of the feelings expressed, in some way, by others.
Explain an example of Value Stream Mapping. (If you're unfamiliar with it, check out this video or this printable 1-pager.) Ask the team to draw a value stream map of their process from the point of view of a single user story. If necessary, ask them to break into small groups, and facilitate the process if they need it. Look at the finished map. Where are long delays, choke points and bottlenecks?
If your boss had witnessed the last iteration, what would she want you to change? Source:
Imagine your boss had spent the last iteration - unrecognized - among you. What would she think about your interactions and results? What would she want you to change? This setting encourages the team to see themselves from a different angle.
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.