In Agile Retrospectives: Making Good Teams Great, Esther Derby and Diana Larsen offer a practical and powerful guide to one of the most valuable yet often overlooked practices in Agile: the retrospective. The book shows how regular, structured reflection enables teams to continuously improve, strengthen collaboration, and adapt effectively in complex environments. Retrospectives help teams transform from merely good to truly great by building a culture of learning, trust, and experimentation.
The authors, both experienced facilitators and Agile coaches, share hands-on techniques, tools, and activities that can be applied immediately to any team. The book is built around a simple but robust framework that helps teams move from reflection to real, measurable improvement.
Why Retrospectives Matter
Agile development is founded on the principle of continuous improvement. The twelfth principle of the Agile Manifesto states that “at regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly.” This is the essence of retrospectives.
Derby and Larsen argue that retrospectives are far more than end-of-project post-mortems or checkbox exercises. They are focused, recurring opportunities for teams to examine how they work, identify patterns, and decide what to change. While automated tests and sprint reviews focus on improving the product, retrospectives focus on improving the process and the people doing the work.
A well-run retrospective helps a team learn faster, strengthen relationships, and increase both productivity and satisfaction. It creates a safe space where everyone’s voice is heard and where continuous improvement becomes part of the team’s rhythm.
The Structure of a Retrospective
The book introduces a five-stage structure that can be applied to retrospectives of any length or scale. These stages ensure that discussions remain focused, balanced, and productive.
Set the Stage
The first step is to prepare the team mentally and emotionally. The goal is to create psychological safety so everyone feels comfortable sharing openly. The facilitator sets expectations, clarifies the purpose, and establishes working agreements. This is where simple check-in activities can help the team shift attention from daily work to reflection.
Gather Data
In this phase, the team collects information about what happened during the iteration. Facts, feelings, and observations are all valuable. Data can include metrics like defect counts or velocity, as well as qualitative input such as team morale or communication challenges. The purpose is to ensure everyone sees the same picture before diving into analysis.
Generate Insights
Once data is gathered, the team explores causes, patterns, and connections. The goal is to understand why things happened as they did, not just to list problems. Structured exercises such as brainstorming, root-cause analysis, or mind mapping help the team identify both strengths and improvement areas.
Decide What to Do
Insights are only useful if they lead to action. In this stage, the team agrees on one or two concrete experiments or improvements to implement in the next iteration. The authors emphasise that teams should avoid overloading themselves with too many changes at once. Small, focused experiments are more likely to succeed and build momentum.
Close the Retrospective
Finally, the team reflects on the session itself, captures learnings, and expresses appreciation. This closure reinforces accountability and leaves participants with a sense of completion. It also builds trust and motivation for future retrospectives.
This structure can be applied to short iteration retrospectives, release retrospectives, or even large-scale organisational reviews.
Designing Retrospectives That Fit Your Team
No two teams are identical, and the book encourages tailoring retrospectives to fit the team’s context. Factors such as team size, iteration length, maturity, and organisational culture all influence how a retrospective should be designed. Derby and Larsen explain how to shape goals for retrospectives based on the team’s current challenges. For example, a new team might focus on building trust and establishing working agreements, while a mature team may concentrate on improving cross-functional collaboration or optimising workflow. They also highlight the importance of creating a physical and emotional environment that supports open discussion. A neutral space, visual aids such as flip charts or whiteboards, and time away from daily work help participants engage more fully.
The Role of the Retrospective Leader
A key message in the book is that retrospectives need effective facilitation. The retrospective leader, often the Scrum Master, is responsible for creating conditions where the team can think, talk, and learn together. The leader’s role is not to lecture or dictate outcomes, but to guide the process, manage group dynamics, and ensure psychological safety. This requires balancing structure with flexibility and keeping discussions productive without suppressing disagreement. Good facilitation is about neutrality, empathy, and observation. The leader must be aware of power dynamics, encourage quieter voices, and handle conflict constructively. The book provides practical advice on managing time, using visual tools, and debriefing activities to extract learning.
Activities for Every Phase
One of the book’s most useful aspects is its extensive library of activities that can be used throughout the five retrospective phases. These are practical, repeatable exercises designed to keep sessions engaging and effective. Activities like ESVP (Explorers, Shoppers, Vacationers, Prisoners) help gauge participants’ attitudes at the start. Timelines and satisfaction histograms help gather data visually. Root-cause analysis and brainstorming help generate insights. Techniques such as “Dot Voting” or the “Retrospective Planning Game” support decision-making and prioritisation. The variety ensures that retrospectives never become stale. Changing formats regularly helps maintain engagement, encourages creativity, and provides new perspectives.
Turning Insight into Action
The authors warn against what they call the “do-nothing retrospective,” where discussions happen but no change follows. To avoid this, teams must ensure that outcomes are specific, actionable, and integrated into daily work. A retrospective is successful when it produces experiments or behavioural changes that are tracked and reviewed in the next iteration. These can be added to the team’s backlog or incorporated into sprint planning. The key is to ensure ownership and follow-up. Derby and Larsen recommend using visible reminders such as posters or digital boards to track improvement actions. These help the team stay accountable and celebrate progress.
Avoiding Common Pitfalls
Not every retrospective delivers value, and the book identifies common mistakes to watch out for.
Some teams treat retrospectives as complaint sessions, focusing only on what went wrong. Others skip them entirely when they are under pressure, assuming that improvement can wait. Both behaviours undermine learning.
Another frequent issue is repeating the same format every time. When retrospectives feel repetitive, engagement drops and discussions become shallow. Varying the format keeps the energy alive and encourages deeper reflection.
A more subtle pitfall is focusing solely on external problems, such as management or other departments. Teams have limited control over those factors. The authors encourage teams to start with what they can change themselves. Even small internal improvements often influence the wider system over time.
Scaling Retrospectives
While the book focuses primarily on short iteration retrospectives, it also explores how to adapt the process for larger contexts such as release or project retrospectives.
These broader sessions involve multiple teams and stakeholders and look at long-term patterns rather than short-term delivery. They help uncover systemic issues that go beyond a single team’s influence, such as cross-departmental communication or organisational policies.
For large retrospectives, careful preparation is essential. The facilitator must design activities that include all perspectives and ensure the session results in actionable outcomes. The authors advise using visual tools like swim lanes and timelines to help participants see how their work intersects.
Supporting Change After the Retrospective
Making improvements stick requires more than good ideas. People naturally revert to familiar habits, so the team and organisation must support new behaviours. The authors suggest introducing new practices as small, safe-to-fail experiments rather than major transformations. Teams should track results, review progress regularly, and adjust as they learn. Managers and leaders can help by providing time and resources for improvement work, recognising positive change, and removing organisational obstacles. Sustainable improvement depends on shared responsibility, not just facilitation skill.
Continuous Learning and Improvement
At its heart, Agile Retrospectives is about learning. The practice of pausing, reflecting, and adjusting transforms not only teams but also individuals. Over time, regular retrospectives build a culture of openness, trust, and accountability. Derby and Larsen emphasise that improvement is a continuous journey. The real power of retrospectives lies in creating a feedback loop where teams inspect and adapt continuously, aligning with Agile’s empirical foundation. They also remind readers that retrospectives benefit from experimentation. No single technique or structure works in every situation. Teams should evolve their approach, adding creativity and personalisation as they grow.
Do You Want To Learn Scrum & Agile?
Learn Scrum & Agile at lost cost and online. Our 5-star rated Ultimate Scrum & Agile eLearning Courses can take you from beginner to advanced at your own pace.
Prepare and practice for the assessments from the major Scrum & Agile providers. Our 5-star rated Ultimate Scrum & Agile Practice Assessments will help you gain certification.
About TheScrumMaster.co.uk
