Where Did the Agile Coach Go? Reflections on the Role, Challenges, and Future of Agile Coaching

Two years ago a senior manager introduced a newly promoted manager, Tara, who had previously served as the company's agile coach; a year later she left, and the author began questioning whether hiring an agile coach would truly help the team improve.

The author recalls that Scrum began to appear sporadically in China around 2006, quickly leading to a surge in CSM certifications and the creation of Scrum Master roles that evolved into agile coaching positions, often rebranded to reflect broader responsibilities beyond pure Scrum.

As agile practices merged with Kanban, automated testing, extreme programming, and later continuous delivery, DevOps emerged as the dominant buzzword, encompassing the entire software delivery pipeline and blurring the line between development and operations.

From this evolution a clear split among agile coaches has formed: a technical stream (DevOps, extreme programming, TDD, refactoring) and a non‑technical stream (facilitation, visual coaching, organizational and executive coaching, Kanban).

The essay highlights several persistent challenges: coaches often fall into the trap of treating transformation as a one‑off event rather than a continuous improvement journey; certification‑driven coaches may lack real experience; and many coaches are expected to be universal generalists despite limited technical expertise.

Another dilemma is the unclear responsibility of coaches—while teams deliver business value, coaches are left to merely run meetings, creating a mismatch between what the team needs and what the coach provides.

Self‑organization is frequently misunderstood; true self‑organization requires clear strategic goals and the ability to decompose them continuously, a condition most teams do not meet.

The author argues that most agile coaches, often former individual contributors, are asked to manage without possessing strategic thinking, leading to a gap between what they excel at and what the organization actually needs.

Identifying the team's evolving needs, especially technical bottlenecks, is crucial, yet many coaches lack the technical insight to do so.

In personal reflection, the author describes how senior leadership trusts him because he consistently identifies strategic needs and acts on them, even when it means stepping away from his own strengths.

The core recommendation is to maintain continuous leadership—an ongoing effort to recognize and address team needs, align with strategic objectives, and provide lasting value beyond short‑term coaching interventions.