How do participants feel at the retro: Explorer, Shopper, Vacationer, or Prisoner? Source:
Prepare a flipchart with areas for E, S, V, and P. Explain the concept:
Explorer: Eager to dive in and research what did and didn't work and how to improve.
Shopper: Positive attitude. Happy if one good things comes out.
Vacationer: Reluctant to actively take part but the retro beats the regular work.
Prisoner: Only attend because they (feel they) must.
Take a poll (anonymously on slips of paper). Count out the answers and keep track on the flipchart for all to see. If trust is low, deliberately destroy the votes afterwards to ensure privacy. Ask what people make of the data. If there's a majority of Vacationers or Prisoners consider using the retro to discuss this finding.
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.)
Hand out pens and paper. Pose the question 'What if the company / department / team was territory? What would a map for it look like? What hints would you add for save travelling?' Let participants draw for 5-10 minutes. Hang up the drawings. Walk through each one to clarify and discuss interesting metaphors.
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.