Agile Retrospectives

9.3 Leading Release and Project Retrospectives

Coaches and team leads may lead iteration retrospectives. But when it comes to the release or project retrospective, all team members have part of the story and need to participate, not lead. Enlist a lead or coach from another team or bring in a facilitator from outside the team. Likewise, if you’ve led iteration retrospectives, other teams may call on you to lead their release retrospectives.

If leading a large retrospective is a one-time event for you, find a mentor. Collaborate on the design, and seek advice on managing a larger group for a longer time. If you plan to do more than one large retrospective, invest in training for yourself.

Here are some differences to consider:

Managing Activities    Many activities that work for iteration retrospectives will work in release or project retrospectives. The trick is to use small groups so that people can actually converse rather than attempting discussions with the entire group.

Managing Dynamics    People are people. You’ll see the same behaviors in a large group as in a small group. But the effects are more pronounced. When things go awry, they go bad faster and with more explosive power. The retrospective leader must attend to the process and dynamics. Stay on top of working agreements, and be prepared to name disruptive behavior.

Watch for side conversations in large groups. Side conversations may indicate hidden information, factions, or that someone is undermining the ...