What Does an Agile Coach Do? Roles, Stances and Scope
An agile coach helps teams and organizations get better at agile ways of working by moving between teaching, mentoring, facilitating and professional coaching.
The Agile Coach · Last reviewed October 21, 2026 · 6 min read
"Agile coach" is a job title that means different things in different companies. In one organization it describes someone who works side by side with two or three teams every day. In another it describes a person who advises executives on how the whole company plans, funds and delivers work. Both are legitimate versions of the role, and they share a common purpose: helping people work in a more adaptive, collaborative way and keep getting better at it.
What an agile coach is not, at least in a healthy version of the role, is a process police officer or a substitute manager. A good coach builds a team's own capability so that, over time, the team needs the coach less. That goal shapes almost everything about how coaches spend their days.
This guide walks through what agile coaches actually do, the different stances they move between, and how the work changes at the team level compared with the enterprise level.
The Core Purpose of the Role
The Manifesto for Agile Software Development includes a principle that captures much of a coach's focus: "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly." An agile coach helps make that reflection real, useful and continuous rather than a box-ticking ritual.
In practice, coaches help with three broad areas.
- How the team works: planning, prioritizing, limiting work in progress, getting early feedback and improving its own process.
- How the team works together: communication, conflict, decision making and shared ownership.
- How the team fits into the wider organization: dependencies, stakeholder relationships, and policies that help or get in the way.
A coach rarely owns any of these outcomes directly. The team owns its work. The coach's job is to help people see their situation more clearly and widen the range of options they have for improving it.
Four Stances Coaches Move Between
Practitioners often describe agile coaching as a blend of distinct skills, sometimes called stances. One common breakdown, used for example by the accreditation body ICAgile, names four core coaching skills: professional coaching, facilitating, mentoring and teaching. Lyssa Adkins' 2010 book "Coaching Agile Teams" covers similar ground, with chapters on the coach as coach-mentor, facilitator, teacher, problem solver, conflict navigator and collaboration conductor.
Teaching is the most direct stance. The coach has knowledge the team needs and shares it. Explaining how a Kanban board works, what a Definition of Done is for, or why small batches of work reduce risk are all teaching moments. Teaching is most valuable when a team is new to a practice.
Mentoring is advice drawn from the coach's own experience. A coach who has worked as a developer, tester or Scrum Master can say, in effect, "Here is what I have seen work, and here is what tends to go wrong." Mentoring is personal and often one-on-one.
Facilitating means designing and guiding a conversation so a group can do its best thinking, while the facilitator stays neutral on the content. Retrospectives, planning sessions and difficult decision meetings all benefit from someone who keeps the process on track so everyone else can focus on the problem.
Professional coaching is where the coach asks rather than tells. The International Coaching Federation (ICF) defines coaching as "partnering with clients in a thought-provoking and creative process that inspires them to maximize their personal and professional potential." In an agile setting, that might mean helping a team lead think through why a recurring problem keeps happening, without handing over an answer.
Choosing the Right Stance
The real skill is less about any single stance and more about knowing which one fits the moment. Some rough guidance follows.
- When a team lacks basic knowledge, teaching saves time and frustration.
- When someone wants a perspective from experience, mentoring helps, as long as you label it as your opinion.
- When a group needs to make a decision or surface ideas, facilitate and stay out of the content.
- When a person or team already has the knowledge but feels stuck, coaching questions often unlock more than advice does.
A common trap is staying in teaching or advising mode too long. It feels productive, but it can make a team dependent on the coach. Consider a hypothetical example: a coach notices that a team keeps missing its sprint goal. Rather than announcing the cause, the coach might facilitate a retrospective focused on the pattern, then ask the team lead open questions about what they have noticed, and offer a mentoring view only if asked. The team ends up with an explanation it believes in, and a habit of investigating its own problems.
Team-Level Coaching
Team-level coaches work closely with one team or a small number of teams. Typical activities include the following.
- Observing team events such as planning, daily check-ins, reviews and retrospectives, and giving feedback afterward.
- Helping the team make its work visible, for example on a physical or digital board.
- Pairing with a Scrum Master or team lead to build their facilitation and coaching skills.
- Helping the team work through conflict and agree on explicit working agreements.
- Spotting impediments the team cannot remove on its own and raising them with the right people.
Success at this level looks like a team that runs its own events well, improves its process without being prompted, and handles disagreement constructively. A useful test is to ask what would happen if the coach stepped away for a month. If the team would carry on improving, the coaching has done its job.
Enterprise-Level Coaching
Enterprise or organizational coaches work with leaders, groups of teams and the systems around them. Their "client" is often the organization itself. Work at this level can include coaching executives, helping restructure teams around products or customer journeys, rethinking budgeting or approval processes that slow teams down, and building internal communities of practice so coaching skills spread beyond a few specialists.
The stances are the same, but the content changes. An enterprise coach might teach leaders how flow metrics work, facilitate a portfolio prioritization session, or coach a director who is learning to stop assigning tasks to individuals.
Many problems that teams experience actually originate at this level. A team cannot become truly cross-functional if hiring practices and reporting lines keep specialists in separate departments, and it cannot release frequently if every change needs a monthly approval board. Enterprise coaching addresses those structural causes, which team-level coaching alone often cannot reach.
What Good Agile Coaching Looks Like
Regardless of level, effective coaches tend to share a few habits. They start by observing and listening before recommending anything. They are open about which stance they are in, saying something like "Let me put my mentor hat on for a minute." They focus on outcomes the team cares about, not on compliance with a framework. They respect the team's ownership of decisions, even when they would have chosen differently. And they deliberately work to make themselves less necessary over time.
When you are evaluating coaching, whether you are receiving it or providing it, those habits are a better signal of quality than any particular method or toolkit.
Key takeaways
- An agile coach helps teams and organizations build their own capability for adaptive, collaborative work.
- Coaches move between teaching, mentoring, facilitating and professional coaching, and choosing the right stance for the moment is the core skill.
- Team-level coaching focuses on the daily practices of a few teams, while enterprise coaching focuses on leadership, structure and organizational systems.
- Good coaches listen first, respect team ownership and aim to become less necessary over time.
Sources
Spotted something out of date? Let us know.