April 08, 2019
Other than agile itself, perhaps the most important aspect of agile software development is the retrospective. This is where the iteration becomes recursive and folds the process back on itself. The problem that the retrospective seeks to solve is how to solve problems. Agile Retrospectives: Making Good Teams Great by Esther Derby and Diana Larsen is widely viewed as the handbook on how to lead an agile retrospective. The following book summary is a combination of my notes and quotes. Let’s get meta!
Note: Amazon links are affiliate.
When we say retrospective, here’s what we have in mind: a special meeting where the team gathers after completing an increment of work to inspect and adapt their methods and teamwork. Retrospectives enable whole-team learning, act as catalysts for change, and generate action. Retrospectives go beyond checklist project audits or perfunctory project closeouts. And, in contrast to traditional postmortems or project reviews, retrospectives focus not only on the development process, but on the team and team issues. And team issues are as challenging as technical issues—if not more so.
During retrospectives, teams discover real solutions that they can implement without waiting for management’s permission. Since experiments and changes are chosen, not imposed from above, people are more invested in their success.
The structure of a retro:
The learning belongs to the team, and team members: not the coach, not the team lead, and not you as the retrospective leader. The team needs to own them.
The authors claim their tried-and-true structure will help the team do the following:
Lastly, and perhaps most importantly, “…perform a retrospective on the retrospective. Look at what went well and what you could do differently in the next retrospective. ‘Inspect and adapt’ applies to retrospectives, too.”
A useful goal helps answer the question, what will achieve value for the time invested?
Shortcutting time means cheating results.
Activities are time-boxed processes that help the team move through the phases of the retrospective.
The bulk of Agile Retrospectives is filled with activities suitable for any team and duration.
Retrospective leaders focus on the process and structure of the retrospective. They attend to the needs and dynamics of the group and help the group reach a goal. Retrospective leaders remain neutral in discussion, even when they have strong opinions.
As the retrospective leader, you have two tasks during an activity: be available to answer questions about the activity, and monitor the room.
Here’s a simple, four-step method to debrief almost any activity:
The key to managing group dynamics is not technique but in understanding and managing your own emotional state and responses. If you aren’t managing your own state, no technique or strategy will help. When emotions are high, your team needs someone to stay outside the turmoil. That someone is you, the retrospective leader.
Agile retrospectives are an important problem-solving tool that help you identify which problems need to be solved. If you’re a technical manager or leader, I recommend reading Agile Retrospectives: Making Good Teams Great by Esther Derby and Diana Larsen.
Want to level up your problem solving skills? I write a weekly newsletter about programming, problem solving and lifelong learning. Join now