Do Don't Try

Martin Jul writes about a retrospective activity in the post “Retrospectives - Adapting to Reality.” He describes an interesting process for highlighting issues in the Generating Insights part of a retrospective session.

Park Bench

I’ve used “Park Bench” at the end of workshops as a way of reflecting on the day or as a debriefing technique after a training exercise to uncover group discoveries. You may be surprised that I hadn’t thought of it for retrospectives. I was. Luckily, Michael thought of it.

Retrospectives

Avoidable Heroism

Today I invented a phrase (at least I think I invented it because I haven't heard anyone else say it): "Avoidable Heroism."

I invented it in response to a question, "Should my team work on the weekend to meet a commitment made under their control?"

Now, I don't know the background behind this question. Maybe it's perfectly reasonable for them to work on the weekend. Maybe they have no agreement about sustainable pace. And, it raises a few questions in my mind. How often does this happen? How far from the commitment are they? When was the first, best opportunity to...

Agile Teams

Circles and Soup

Sometimes teams get stuck at the point of “deciding what to do” in retrospectives. Team members may begin to point fingers and describe things that the ubiquitous “they” must do before the team can move forward or make improvements,. This may lead to a team-as-victim, “poor us, we’re stuck” syndrome, or blame and finger-pointing. “It’s their fault we’re in this mess!” Blame kills retrospectives and the perception of persecution stalls any hope of forward motion, so the retrospective leader has to shift this conversation, and fast! Team members also may perceive so much room for improvement they become paralyzed and can’t decide where to start improving their lot.

When victim-talk, blaming or overwhelm surfaces, I reach into my retrospective leaders toolbox and pull out a technique to help teams identify the kinds of action the team can take.

Retrospectives

Categories