"What sort of car do you feel like after this iteration?"
Question asked at the start of Agile retrospect.
Retro is not ALL about retro, or team building. After two weeks rowdy, fuzzy, warmth work, most of people got tired. But a good and interesting question can grab everyone's attention right away from the sleepy mode.
"I feel like a Bug Convertible", our integration leader says. "I feel like a Jeep Wrangler", one tester says.
"A small car, for example, Mica", our test leader says, although he is tall and big fellow.
"Peugeot 308", a typical Business Analyst answer. Looks sleaky, shining outside, but who knows what under hood is.
"A 2nd hand car", one developer says. Now everyone feel sorry for him, "we push him too hard. He maybe breaks down anytime."
"Toyota Camry", I say. "Why"? "Because it's reliable and deliverable, but slow and boring".
"I'm an UTE with an enormous bull bar in front", our team leader.
"A caravan". This is one integration contractor's answer. "Because you have to pull it all the time. But it's still relaxed, nice and slow".
Seems this integration contractor just mucks around the work. "Another day, another payment".
"Don't worry about", people start yelling at him, "we'll soon sort it out for you ..."
I have found that after sprinting for two weeks the team can get a little tired and Retro (on a Friday afternoon) can seem like a chore.