Key Takeaways
Coach teams to deliver value, then make yourself less necessary
From control to coaching. Agile coaching is more than keeping Scrum ceremonies on schedule. It draws on teaching, facilitation, mentoring, conflict navigation, and problem solving so a team can use agile deeply and deliver work that matters. Adkins tells how her first agile team built useful functionality in 30 days, work that her previous project-management approach would have taken months to produce. The experience challenged her belief that complex projects need a manager coordinating every part.
Change the coach’s job. The coach’s success is not control of the plan, but a team’s growing ability to solve problems, improve its work, and own its decisions. Agile practices provide structure; the coach helps people make that structure useful without becoming the team’s hub.
What's striking is the reversal of a familiar leadership signal: visible activity is not necessarily value. A coach may contribute most by improving the conditions under which other people think and coordinate. This resembles systems leadership, where changing feedback loops and decision rights can outperform directing each task. The principle has a boundary, though. Stepping back is not automatically empowering if the team lacks skill, authority, or organizational support. Effective coaching pairs restraint with active work on those constraints.
Practice self-command before asking a team to self-organize
Notice your reflexes. Coaches bring old habits into agile, especially the impulse to take over when a team hesitates. Adkins calls this command-and-control-ism: directing people, solving problems for them, or quietly steering them toward the coach’s preferred answer. She recommends noticing conflict reactions, emotional triggers, and the impact of one’s words before choosing how to respond.
Create room to think. Preparation can be simple: a quiet walk, breathing, music, or a short reflection on what would best serve the group. In the moment, listen fully, wait before speaking, and tolerate silence. When a problem appears, reflect observations without judgment and invite the team to interpret them. The coach’s example matters: acknowledging a mistake openly can make it safer for others to do the same.
Self-regulation is not a decorative leadership virtue here; it is an operational condition for distributed decision-making. If the coach reacts to uncertainty by taking control, the team learns that initiative is risky and escalation is rewarded. A pause creates space between stimulus and intervention, but restraint should not become passivity. Coaches need to distinguish discomfort from danger: ordinary ambiguity can belong to the team, while harm, discrimination, or other serious safety concerns require action.
Make high performance a journey the team defines, not a score imposed
Offer a compelling image. High performance is presented as ongoing improvement, not a fixed state or a target the coach can prescribe. The High Performance Tree gives teams a way to build their own picture: values form its roots, collaborative behaviors its growth, and useful business results its fruit. The coach can ask where the roots seem weak or what fruit the team wants to produce next.
Keep the path theirs. A team might discover that it rushes to the first idea instead of hearing alternatives, then choose to practice genuine agreement. Another might connect missed sprint goals with distractions and decide how to protect its commitments. Setbacks are expected when people, goals, and organizational conditions change. Progress includes recovering together, not just reaching a temporary peak.
The metaphor makes an abstract ambition discussable without pretending that every team should look alike. It also links culture to outcomes: values are not ornaments if they shape how people make decisions and deliver work. The caution is that a metaphor can become wallpaper if it is not tied to observable behavior. A useful image should generate concrete experiments and be revisited against actual results, rather than becoming a cheerful substitute for addressing poor quality or unrealistic demands.
Teach the rules, coach their meaning, then let teams rewrite them
Match the team’s maturity. Adkins uses Shu Ha Ri, a model of learning through practice, reflection, and independent expression. A team first learns a practice reliably, then examines the principle behind it, and eventually may create a different practice that serves the same purpose. Scrum’s stand-up, for instance, should not be changed before the team understands how it supports coordination and commitment.
Change your coaching style. Teach firmly when people are new or have lost the purpose of a practice. Ask questions and support experiments when the basics are working. Offer advice, then step back, when the team can monitor and improve itself. These stages are not linear or uniform: a team may understand one practice deeply while learning another from scratch. If a change hides dysfunction rather than improving the work, return to the underlying principle.
This model captures a productive tension between fidelity and adaptation. Practices can carry knowledge that beginners cannot yet see, while rigid imitation can turn them into empty rituals. The distinction between changing a practice to deepen its purpose and changing it to avoid a difficult problem is especially valuable. It also calls for humility from the coach: stage labels are rough guides, not diagnoses of a whole team, and people may need different levels of support in different parts of their work.
Pair agile expertise with coaching that leaves ownership with people
Use both kinds of help. Agile coaching combines mentoring, which shares knowledge of agile, with coaching, which helps people find their own next steps. The work happens with individuals and with the team as a whole. In a one-on-one conversation, the coach listens for the real concern, asks questions that open up options, and helps the person choose an action. The coach may offer agile expertise, but does not claim to be the expert on someone else’s life.
Support the whole system. Product owners need help prioritizing by business value, making timely decisions, and protecting the team’s focus. Managers need to support self-organization and remove organizational barriers. The coach should establish confidentiality, with clear exceptions for serious harm, and partner with managers without exposing private conversations. Role clarity matters: the coach must not quietly become a substitute product owner or project manager.
The distinction between coaching and mentoring prevents two opposite failures: withholding useful expertise in the name of neutrality, and prescribing every answer because the coach knows agile. The method depends on clear power boundaries, especially when managers control reviews or job security. Confidentiality can create trust, but it cannot be absolute where safety or legal obligations are at stake. Coaching is strongest when the person retains agency while the surrounding organization is also made accountable for conditions that constrain that agency.
Facilitate meetings toward their purpose, then retreat from the center
Make the purpose visible. Each agile event has a job. A stand-up coordinates daily work and exposes obstacles. Sprint planning establishes a shared commitment and a workable amount of work. A review shows real output and gathers feedback. A retrospective examines how the team worked and chooses improvements. The coach supplies enough structure for these purposes to be met, then lets the team run the meeting.
Choose interventions carefully. During a sprint, protect the team’s focus and save most broad improvement conversations for the retrospective. In the review, observe how the team interacts with stakeholders instead of acting as its emcee. In conversations, use observations, open questions, and challenges to reveal patterns or invite better ideas. Silence can be useful: the coach does not need to answer first, or at all, if the team can answer for itself.
The idea of a meeting as a container is useful because it separates process from content: the facilitator protects the conditions, while participants do the thinking. That distinction is easy to lose when a skilled facilitator starts performing for the room. Purpose also offers a safeguard against ritual worship. A meeting that follows its format but produces no coordination, learning, feedback, or decision has not succeeded simply because the calendar says it happened.
Bring problems to the team instead of carrying their commitments
Pause before solving. The book’s problem-solving rubric is simple: notice a problem, reflect on it, bring it to the team, and let the team decide what to do. The coach can examine three angles: whether agile practices are working, whether the product is valuable and sound, and whether the team’s dynamics help it work well. Health checks or questions about roles, authority, boundaries, and tasks can reveal issues that are difficult to see directly.
Use evidence, not rescue. If a team’s sprint review leaves stakeholders confused, the fix may be to restate the meeting’s purpose and show value before technical detail, not add a new status report. Potential problems that have not happened yet may disappear without intervention. Serious safety issues are different and call for immediate action. Otherwise, help the team see causes and consequences rather than quietly taking responsibility away from them.
The approach treats teams as capable problem-solving systems rather than machines awaiting expert repair. It also recognizes that premature intervention can create the very dependency the coach hopes to remove. A useful distinction is between preserving learning and abandoning people: allowing a bounded experiment to fail can teach, while tolerating repeated harm or unmanageable risk cannot. The coach’s judgment therefore matters, but it should be used to improve the team’s view of the problem, not to claim ownership of every outcome.
Treat conflict as information and teach teams to de-escalate it
Read the level, not just the volume. The Five Levels of Conflict describes movement from a concrete problem, through guarded disagreement and contests over who is right, toward entrenched campaigns and destructive hostility. The coach looks at complaints, the emotional feel of the room, and the language people use. Specific, present-focused talk suggests a more workable disagreement; general accusations and factional thinking suggest escalation.
Help people face one another. First allow time for the team to handle conflict itself. If intervention is needed, the coach can clarify the issue, reconnect the discussion to agile principles, or teach the team the conflict model so it can self-correct. When someone complains about a colleague, encourage a direct conversation rather than carrying the accusation. Some recurring disagreements may not disappear; teams can reduce their damage through better listening, shared purpose, and more positive interactions.
The key move is reframing conflict from evidence of team failure into information about competing needs, assumptions, or goals. That makes constructive disagreement possible without romanticizing hostility. The book also reports positivity-to-negativity ratios from team research, but such figures should not be treated as universal diagnostic thresholds. Relationship quality is difficult to reduce to a single count. The practical test is whether people can speak candidly, hear objections, and return to coordinated work without suppressing real concerns.
Build collaboration when innovation needs ideas no one could create alone
Know the difference. Cooperation helps people coordinate their contributions and deliver shared work. Collaboration goes further: people build on one another’s ideas until a result emerges that no one had planned individually. It is more demanding, so teams do not need it for every task. When innovation is important, the coach can help individuals become better collaborators by making it safe to ask for help, speak honestly, and contribute without needing every idea to win.
Conduct, then step aside. The coach can invite quiet voices, temper dominant ones, and encourage people to develop ideas rather than immediately attack them. Games, improvisation, or silent mind mapping can loosen stale conversations and generate a surplus of possibilities. Adkins compares early collaboration to a band that needs a conductor, then to a quartet that can play together without one. The point is not endless facilitation, but a team able to manage its own creative exchange.
The distinction avoids treating collaboration as a moral upgrade for every kind of work. Coordination can be faster and sufficient when tasks are understood; deep idea-building earns its cost when uncertainty and novelty matter. The musical analogy also highlights that collaboration is a capability, not a meeting format. Games may help people loosen habitual responses, but they cannot manufacture trust or erase unequal authority. Their value depends on whether participants can disagree and still build on what others offer.
Measure coaching by the team's growing independence, not your visibility
Watch the effect. Coaches can slip into failure modes such as the Expert who supplies answers, the Hub who becomes indispensable, or the Nag who polices every practice. These patterns often grow from fear, ego, distraction, or divided attention. Trust and close observation help a coach notice the pattern, recover, and practice more useful responses. Adkins also recommends pairing with peers and treating the coach’s own work as something to inspect and adapt.
Make invisible work legible. Because coaching results are shared with the team, managers may struggle to see an individual coach’s contribution. The book advises coaches to keep a weekly record of value delivered and to review their own impact honestly. Rachel Davies’s journey shows the value of patience and small steps; other coaches describe learning to stop managing and start listening. The aim is not to claim the team’s success, but to understand how coaching helped it grow.
A coach’s influence is often indirect, so outcome measures based only on personal deliverables can reward the wrong behavior: visible intervention over durable capability. The proposed self-review helps make subtle work more concrete, but it should not become self-congratulation. Team independence, product quality, learning, and stakeholder value provide stronger evidence than the coach’s sense of having been useful. The deeper test is whether the team can maintain good decisions and healthy working practices when the coach is not at the center.
Analysis
The book’s central argument is that agile is not a lighter project-control machine. It is a framework in which a team can learn, decide, and adapt, provided the coach resists taking back authority whenever uncertainty becomes uncomfortable. That gives the book its distinctive tension: the coach must know enough to teach practices and challenge harmful compromises, yet must not confuse expertise with the right to decide for everyone. Its strongest guidance lies in that practical balancing act.
The structure follows a useful widening spiral. First the coach examines personal habits, then develops skills for team interaction, and finally looks at organizational roles, failure patterns, and professional growth. The repeated return to self-awareness is not padding. It links the interpersonal tools to the same inspect-and-adapt logic that governs agile work. Stories, such as a team delivering useful functionality in 30 days or managers unintentionally rewarding individual competition, show how process and incentives shape behavior more powerfully than slogans.
The most important qualification is that team autonomy is not achieved by simply stepping away. Teams need clear goals, decision authority, resources, psychological safety, and organizational protection. The book recognizes managers and sponsors as part of the system, but its coach-centered perspective can make difficult structural constraints look more coachable than they are. Some impediments require formal authority, not another question in a retrospective. Likewise, frameworks such as conflict levels and collaboration stages are maps, not objective measurements of people.
The lasting value is a model of leadership through capability-building. The coach teaches, facilitates, mentors, and sometimes intervenes, but each intervention should leave the team better able to see and act for itself. This is neither hands-off laissez-faire nor benevolent micromanagement. It is deliberate support with a clear direction: help teams deliver meaningful products while becoming less dependent on the person who helped them start.
Review Summary
Coaching Agile Teams receives high praise for its comprehensive guidance on agile coaching. Readers appreciate its practical advice, real-world examples, and focus on personal growth. Many consider it essential reading for agile practitioners, especially those transitioning from project management. The book is lauded for its insights on team dynamics, collaboration, and conflict resolution. While some find it dense or repetitive in parts, most reviewers value its depth and applicability. It's seen as a valuable resource for both new and experienced coaches.
People Also Read
Glossary
Agile coaching
Agile mentoring plus coachingA role that combines agile expertise with coaching skills. The coach teaches practices and principles, facilitates team learning, and helps individuals and groups improve their performance. Unlike a project manager who directs and controls delivery, an agile coach aims to help teams own decisions, solve problems, and work toward stronger results.
High Performance Tree
A team-growth metaphorA visual metaphor for a team’s development. Values are represented as roots, collaborative behaviors as growth, and valuable results as fruit. The image gives a team a shared way to identify what is supporting its work, what needs attention, and what kind of result it wants to pursue next.
Shu Ha Ri
Stages of learning masteryA learning model used to describe how teams develop their use of agile. Learners first practice established methods, then examine the principles behind them and experiment, and ultimately express those principles in ways suited to their context. The stages can overlap across different skills and are not a rigid timetable.
Business value microdefinition
The next business objectiveA short-term business objective that guides the product owner’s immediate choices while the larger product vision remains in view. It gives the team a practical basis for prioritizing work and assessing trade-offs. It is meant to connect near-term decisions to meaningful business value rather than to habit, personal preference, or schedule pressure alone.
Five Levels of Conflict
A conflict-escalation modelA framework for recognizing how conflict shifts from a specific problem people can discuss toward hostility and destructive opposition. As conflict escalates, participants tend to move from clear facts to guarded interpretations, blame, and entrenched positions. A coach uses the framework to gauge the situation and choose whether and how to intervene.
BART analysis
A team-dynamics diagnosticA group-relations framework that examines boundaries, authority, roles, and tasks. Applied to agile teams, it helps identify unclear responsibilities, misplaced decision rights, conflicting roles, and confusion about the team’s purpose or work. These conditions can generate problems that appear personal but are rooted in how the team is organized.
Control by release
Trust within agile safeguardsAn approach to leadership that gives a team room to act within a clear agile framework instead of directing each move. Timeboxed work, regular coordination, and inspect-and-adapt practices provide checkpoints and limits. The manager or coach retains appropriate oversight while allowing the team to exercise judgment and creativity.
Green Zone and Red Zone
Collaborative and defensive stancesA model of individual attitudes that support or undermine collaboration. The Green Zone represents openness, responsibility, and willingness to work with others. The Red Zone represents defensive behaviors that obstruct cooperation. The framework encourages team members, including coaches, to notice their stance and consciously return to more collaborative behavior.
Fist of Five
A visible agreement checkA group technique for quickly showing how much support people have for a proposal. Participants simultaneously raise one to five fingers, with lower numbers signaling reservations and higher numbers stronger support. The facilitator invites people with concerns to explain them, helping surface hesitation that may not emerge in ordinary discussion.
FAQ
What's Coaching Agile Teams about?
- Focus on Agile Coaching: Coaching Agile Teams by Lyssa Adkins is a guide for ScrumMasters, Agile Coaches, and Project Managers transitioning to agile methodologies, emphasizing the role of coaching in team performance.
- Role of the Coach: It outlines various roles an agile coach can take, such as teacher, facilitator, and conflict navigator, and highlights the importance of emotional intelligence.
- Practical Techniques: The book provides practical techniques and frameworks to help teams navigate challenges and foster continuous improvement.
Why should I read Coaching Agile Teams?
- Enhance Coaching Skills: It is essential for improving coaching skills within agile environments, offering insights into effective techniques for better team performance.
- Broaden Understanding of Agile: The book deepens understanding of agile principles and practices, aiding in their effective implementation.
- Real-World Applications: Adkins shares experiences and lessons learned, providing relatable examples for readers to apply in their own coaching situations.
What are the key takeaways of Coaching Agile Teams?
- Agile Coaching Matters: Agile coaching is crucial for teams to thrive in complex environments, helping them navigate challenges and unlock potential.
- Self-Organization: Teams must be self-organizing, with the coach facilitating this process rather than dictating actions.
- Continuous Learning: Both coaches and teams should embrace continuous learning and adaptation, fostering a mindset of growth and exploration.
What are the best quotes from Coaching Agile Teams and what do they mean?
- “A ScrumMaster who takes teams beyond getting agile practices up and running into their deliberate and joyful pursuit of high performance is an agile coach.”: Highlights the transformative role of an agile coach in fostering continuous improvement.
- “It’s the team’s commitment, not yours.”: Emphasizes that success responsibility lies with the team, encouraging empowerment and ownership.
- “The art of teaching is the art of assisting discovery.”: Underscores the coach's role as a facilitator of learning, guiding teams to find their own solutions.
What is the Shu Ha Ri model mentioned in Coaching Agile Teams?
- Stages of Mastery: Describes three stages of mastery in agile practices: Shu (following the rules), Ha (breaking the rules), and Ri (being the rules).
- Non-Linear Progression: Progression is not linear; teams may exhibit characteristics of multiple stages simultaneously, allowing for nuanced understanding.
- Application in Coaching: Coaches tailor their approach based on the team's current stage, providing appropriate support and guidance.
How does Coaching Agile Teams define collaboration versus cooperation?
- Collaboration Defined: Involves team members building on each other's ideas, leading to innovative outcomes requiring trust and openness.
- Cooperation Defined: Characterized by working together towards a common goal without deep collaboration, focusing on smooth coordination.
- Importance of Both: While cooperation is essential for basic teamwork, collaboration is necessary for breakthrough results, requiring a balance.
What are the different roles of an agile coach as described in Coaching Agile Teams?
- Teacher Role: Involves simplifying complex concepts and ensuring everyone understands their roles, especially during team start-ups.
- Facilitator Role: Guides discussions and decision-making processes, fostering collaboration and ensuring all voices are heard.
- Conflict Navigator: Helps teams address and resolve conflicts constructively, promoting healthy dialogue and team dynamics.
How can I effectively coach individuals one-on-one as described in Coaching Agile Teams?
- Establish a Safe Environment: Create a space for open dialogue by guaranteeing confidentiality and safety, encouraging sharing without fear of judgment.
- Use Powerful Questions: Employ open-ended questions that invite introspection and self-discovery, helping individuals explore their own solutions.
- Set Clear Goals: Help identify specific actions for improvement, establishing accountability to ensure follow-through and progress.
How does Coaching Agile Teams suggest handling conflict within teams?
- Recognize Conflict as Natural: Conflict is a natural part of team dynamics, and coaches should help teams navigate it constructively.
- Use Conflict as a Learning Opportunity: Encourage viewing conflict as an opportunity for growth, leading to deeper understanding and stronger relationships.
- Facilitate Open Conversations: Help team members express feelings and perspectives, leading to resolution and a healthier team environment.
What techniques does Coaching Agile Teams recommend for facilitating agile meetings?
- Set Clear Agendas: Establish clear agendas to keep the team focused, maximizing productivity and engagement.
- Encourage Participation: Use techniques like round-robin sharing to ensure all voices are heard and valued.
- Hold Timeboxes: Maintain strict timeboxes to keep discussions concise and focused, respecting everyone's time.
How can I support my own growth as an agile coach according to Coaching Agile Teams?
- Continuous Learning: Engage in ongoing education and self-improvement through workshops, courses, and relevant literature.
- Seek Feedback: Regularly seek feedback from peers and team members to identify areas for improvement and enhance coaching effectiveness.
- Practice Self-Reflection: Reflect on coaching experiences to recognize patterns, successes, and areas for growth, aiding personal development.
What is the significance of emotional intelligence in agile coaching as discussed in Coaching Agile Teams?
- Understanding Team Dynamics: Emotional intelligence helps coaches understand team emotions and motivations, crucial for navigating conflicts and fostering collaboration.
- Self-Awareness: Coaches with high emotional intelligence are more self-aware, recognizing biases and triggers, enabling effective responses.
- Empathy and Support: Fosters empathy, allowing coaches to support team members through challenges, creating a safe and valued environment.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.