Participants pick a postcard that represents their thoughts / feelings Source:
Bring a stack of diverse postcards - at least 4 four times as many as participants. Scatter them around the room and instruct team members to pick the postcard that best represents their view of the last iteration. After choosing they write down three keywords describing the postcard, i.e. iteration, on index cards. In turn everyone hangs up their post- and index cards and describes their choice.
This is a round-based activity. In each round you ask the team a question, they write down their answers (gives everyone time to think) and then read them out to the others. Questions proposed for Software Development teams:
When was the last time you were really engaged / animated / productive? What did you do? What had happened? How did it feel?
From an application-/code-perspective: What is the awesomest stuff you've built together? What makes it great?
Of the things you built for this company, which has the most value? Why?
When did you work best with the Product Owner? What was good about it?
When was your collaboration best?
What was your most valuable contribution to the developer community (of this company)? How did you do it?
Leave your modesty at the door: What is the most valuable skill / character trait you contribute to the team? Examples?
What is your team's most important trait? What sets you apart?
('Remember the Future' (#37) works well as the next step.)
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.