Why Coaches Need Coaching: Growing as an Agile Mentor

Why Agile Coaching Can Stall Without Self-Development

Agile coaching can become stale when coaches spend all their energy helping others grow but forget to work on their own self-development. I have seen this happen in busy teams, growing startups, and larger organisations where the coach becomes the person everyone leans on, but no one asks, “Who is helping the coach improve?” That matters because good coaching is not just about knowing Scrum, running workshops, or asking clever questions. It is about staying useful, grounded, honest, and human.

As an Agile Coach and former CTO, I have learned that mentorship and leadership growth are not one-way streets. The best coaches I know keep learning from other coaches, mentors, leaders, teams, and yes, occasionally from spectacular mistakes. The Agile Alliance describes agile coaching as a practice that blends coaching, facilitating, teaching, and mentoring to help clients using agile approaches, which is exactly why coaches need their own support system too.

Takeaways

Coaches Are Not Finished Products

A coach who thinks they have finished learning is probably the one who needs coaching the most.

That sounds blunt, but it is true. Agile coaching is not a certificate you frame on the wall and then coast on for the next ten years. It is a craft. Like leadership, facilitation, communication, and mentoring, it needs practice.

In my years as a CTO, I have worked with teams where the coach was technically right but emotionally unhelpful. They knew the framework. They could quote Scrum events, roles, and artefacts. But they struggled to read the room, handle conflict, or adapt their approach to the business in front of them.

That is where self-development becomes practical, not fluffy.

A coach might need to improve how they:

• Listen without jumping in too early.
• Challenge leaders without embarrassing them.
• Help teams take ownership instead of creating dependence.
• Move between teaching, mentoring, coaching, and advising.
• Notice when their own bias is shaping the conversation.

The Scrum Guide describes the Scrum Master as accountable for helping the Scrum Team improve its practices and effectiveness. That is a high bar. It means a coach or Scrum Master needs to keep improving too, because they influence how others improve.

Agile Coaching Is About People Before Process

My core belief is simple. People before technology.

That applies just as strongly to agile coaching. Agile methods can help teams deliver faster, reduce waste, and make better decisions. But methods alone do not fix trust issues, unclear priorities, poor leadership, fear, or burnout.

A business owner might think, “We need Agile.” Often, what they really need is better communication, shorter feedback loops, clearer ownership, and a safer way to talk about what is not working.

The coach’s job is to help with that.

That means the coach must understand people. Not just process. Not just tools. Not just Jira boards with enough columns to make your eyes water.

Good agile coaching helps a team ask better questions:

• What are we trying to achieve?
• Who are we serving?
• What is slowing us down?
• What can we test quickly?
• What are we avoiding?
• What behaviour needs to change?

A coach who is being coached is more likely to ask these questions with humility. They are less likely to turn every problem into a process lecture.

The Risk of Becoming the “Agile Expert” in the Room

There is a quiet trap in agile coaching. People start treating you as the expert.

At first, it feels good. You are invited into meetings. Leaders ask for your opinion. Teams look to you for direction. You become the person who “knows Agile”.

Then the trap closes.

The coach starts answering instead of exploring. They solve instead of developing capability. They become the shortcut. The team stops thinking for itself.

That is not mentorship. That is dependence dressed up as help.

This is why coaches need coaching. A good external mentor or peer coach can ask, “Are you helping the team grow, or are you becoming the team’s safety blanket?”

It is a hard question. It is also a useful one.

In consulting, I have learned that the best client work often involves making yourself less needed over time. That does not mean walking away too early. It means helping people become more confident and capable.

For agile coaches, the same principle applies. Success is not being the smartest person in the room. Success is helping the room get smarter.

Coaching, Mentoring, Teaching, and Advising Are Different

One reason agile coaching is hard is that the coach often has to change stance.

Sometimes you coach. Sometimes you mentor. Sometimes you teach. Sometimes you advise. Sometimes you just shut up and let the team wrestle with the problem. That last one can be surprisingly difficult.

Scrum Alliance explains that agile coaches use different stances, such as facilitating, teaching, and leading, depending on the situation.  

Here is a simple way to think about it.

Stance	What It Means	When It Helps
Coaching	Helping someone find their own answer	When the person has enough context but needs clarity
Mentoring	Sharing experience to guide growth	When someone is developing in a role
Teaching	Explaining a concept or practice	When there is a knowledge gap
Advising	Recommending a path based on expertise	When risk is high or time is tight
Facilitating	Helping a group work through a topic	When the group needs structure and safety

The problem starts when a coach uses only one stance for every situation.

A pure coach may avoid giving advice when the team genuinely needs direction. A pure adviser may become too directive and stop people learning. A pure teacher may turn every meeting into a classroom. Nobody wants a surprise lecture before lunch.

Self-development helps coaches notice which stance they are using and whether it is helping.

Why Self-Development Matters for Agile Coaches

Self-development is not about collecting badges. It is about improving your judgement.

That matters because agile coaching involves messy human situations. Teams disagree. Leaders change their minds. Customers complain. Budgets tighten. Delivery pressure rises. Someone says, “We are Agile now,” while still demanding a fixed scope, fixed date, fixed cost, and a miracle.

A coach needs more than theory.

They need:

• Self-awareness: Knowing how their own habits affect the room.
• Emotional control: Staying calm when conversations get tense.
• Business understanding: Connecting agile practices to outcomes.
• Ethical judgement: Knowing when to challenge, when to support, and when to step back.
• Mentorship: Having someone more experienced to test ideas with.

The International Coaching Federation groups its coaching competencies into areas such as foundation, relationship, communication, and learning growth. That is a useful reminder that coaching is a professional discipline, not just a personality trait.

A coach who invests in these areas becomes more useful to clients. They are better at helping a retailer improve stock flow, a healthcare provider reduce patient admin delays, a startup improve delivery focus, or a professional services firm reduce internal handover pain.

Different industries have different pressures. The coaching principles may be similar, but the business context matters.

Leadership Growth Starts With Being Coachable

Leadership growth starts with one uncomfortable truth. You cannot help others grow if you refuse to be challenged yourself.

That applies to founders, CTOs, managers, Scrum Masters, and agile coaches.

Being coachable means you are willing to hear things that might sting a little. It means you can say, “I may be wrong here.” It means you can reflect on your behaviour without turning it into a personal crisis.

I have worked with leaders who improved quickly once they became coachable. They stopped defending every decision. They started asking better questions. Their teams became more honest with them because it finally felt safe to speak.

Agile coaches need the same mindset.

A coach might ask a team to inspect and adapt every sprint. But do they inspect and adapt their own coaching? Do they review their own habits? Do they ask for feedback? Do they have someone who can call out their blind spots?

If not, the coach is asking the team to do something they are avoiding themselves.

That rarely ends well.

What Good Mentorship Looks Like for Agile Coaches

Good mentorship is not someone telling you how brilliant they are for an hour.

Real mentorship is practical. It helps you think better, act better, and serve your clients better.

For an agile coach, mentorship might include:

• Reviewing a difficult team situation.
• Practising how to challenge a senior leader.
• Discussing ethical boundaries.
• Planning a workshop.
• Reflecting on a failed facilitation session.
• Understanding when agile language is confusing the business.
• Learning how to link agile practices to money, risk, customer value, or staff wellbeing.

A mentor does not need to have all the answers. But they should have enough experience to ask grounded questions.

For example:

• What outcome does the business need here?
• What does the team already understand?
• What are you assuming?
• Where might you be over-helping?
• What would happen if you said less?
• Are you coaching the problem, or reacting to the noise around it?

That last question is a good one. I have had to ask it of myself more than once.

The Best Agile Mentors Stay Close to Real Work

Some agile advice sounds good in a conference talk but falls apart inside a real business.

That is why agile mentors need to stay close to delivery, customers, operations, risk, and leadership pressure. A small business owner does not care whether a process looks perfect on paper. They care whether customers are happier, staff are less stressed, costs are controlled, and work gets done.

For startups, agile coaching often means helping people focus. Founders are full of ideas. That is part of the fun. It is also part of the danger.

For SMEs, agile coaching might mean reducing meeting overload, making priorities clearer, or helping a team finish work before starting more.

For larger organisations, it may involve navigating governance, reporting, dependencies, and leadership habits that have built up over years.

The coach must adapt to the environment without losing the core principles.

That is why self-development should include business awareness. Agile is not the goal. Better business outcomes are the goal.

Signs an Agile Coach Needs Coaching

Every coach needs development. But there are warning signs that coaching has become especially important.

You may need coaching or mentoring if you notice yourself doing any of these:

• You give advice too quickly. You solve the problem before the team has understood it.
• You use agile language people do not understand. The room nods politely, then does nothing.
• You feel frustrated that “they just don’t get it.” That may be a sign your approach needs to change.
• You avoid difficult conversations. You keep the peace but leave the real issue untouched.
• You over-identify with one team. You become their defender rather than their coach.
• You push the framework harder than the outcome. The process becomes more important than the people.
• You stop asking for feedback. That is when blind spots start multiplying like rabbits.

None of these mean you are a bad coach. They mean you are human.

The point of mentorship is not to shame coaches. It is to keep them sharp, useful, and grounded.

Agile Coaching Ethics Matter

Agile coaches often work in sensitive spaces. They hear what teams say when leaders are not in the room. They hear what leaders worry about when teams are not in the room. They may know about delivery risks, staff concerns, budget pressure, and internal conflict.

That creates responsibility.

The Agile Alliance has published an Agile Coaching Code of Ethical Conduct to help raise standards and guide professional behaviour in coaching situations.

Ethics are not just about avoiding obvious bad behaviour. They are about judgement.

For example:

• Are you clear about your role?
• Are you respecting confidentiality?
• Are you creating dependence?
• Are you pushing a method because it suits you, or because it helps the client?
• Are you being honest about what you can and cannot do?
• Are you making the client stronger?

These questions matter because agile coaching works with people, trust, and change.

A mentor or coach can help you work through ethical grey areas before they become messy problems. And in business, messy problems have a habit of arriving on a Friday afternoon. Very considerate of them.

How Coaching Helps Coaches Handle Conflict

Conflict is part of teamwork. It is not always bad. In fact, healthy disagreement can improve decisions.

The problem is unmanaged conflict.

In agile teams, conflict often appears around priorities, quality, estimates, ownership, technical debt, unclear roles, or pressure from leadership.

A coach who is not supported may respond in one of three unhelpful ways:

• Avoid the conflict.
• Take sides too quickly.
• Try to smooth it over without addressing the cause.

Coaching helps the coach pause and choose a better response.

For example, instead of saying, “The team needs better communication,” a coached coach might ask:

• What conversation is being avoided?
• Who has power in this situation?
• What outcome does each person care about?
• What facts are missing?
• What agreement needs to be made explicit?

That is where agile coaching becomes leadership work. It helps people talk about real problems in a way that improves action, not blame.

Self-Development Makes Coaches Better Listeners

Most people listen just long enough to prepare their reply.

Coaches are supposed to do better than that. But even coaches can fall into the trap, especially when they have seen similar problems before.

A founder says, “The team is slow,” and the coach immediately thinks, “Ah, backlog problem.”

Maybe. Maybe not.

It might be unclear strategy. It might be too much work in progress. It might be poor hiring. It might be a fear of saying no. It might be a product owner who is really three people in a trench coat pretending to be one role.

Better listening creates better diagnosis.

A coach who receives coaching is more likely to notice their assumptions. They learn to slow down. They ask cleaner questions. They stop treating every situation as a repeat of the last one.

That is a big part of professional growth.

Mentorship Helps Coaches Connect Agile to Business Value

A common weakness in agile coaching is talking too much about agile and not enough about business value.

Most SME owners do not wake up thinking, “I hope our Sprint Review maturity improves this quarter.”

They think about cash flow, customers, staff, sales, service quality, delivery delays, missed opportunities, and whether the business can keep growing without becoming chaotic.

So the coach needs to translate.

Instead of saying:

“We need to improve backlog refinement.”

Say:

“We need a clearer way to decide what matters next, so the team stops wasting time on low-value work.”

Instead of saying:

“Your Definition of Done is weak.”

Say:

“We need clearer quality expectations, so work does not bounce back later and cost more to fix.”

Instead of saying:

“You lack psychological safety.”

Say:

“People do not feel safe raising problems early, so issues stay hidden until they become expensive.”

That is where mentorship is powerful. A good mentor helps coaches simplify their message without dumbing it down.

Building a Personal Development Plan as an Agile Coach

Self-development works best when it is deliberate.

You do not need a 40-page plan. In fact, please do not create one unless you enjoy punishing yourself with admin. A simple plan is enough.

Start with four questions:

1. What kind of coach am I becoming?
   Are you focused on teams, leaders, delivery, culture, product, technical practices, or organisational change?
2. Where am I strong?
   Name the skills you can rely on. Facilitation, delivery experience, executive conversations, mentoring, conflict work, technical fluency, or business strategy.
3. Where do I need support?
   Be honest. Maybe you struggle with difficult leaders. Maybe you talk too much. Maybe you avoid commercial conversations.
4. Who can help me improve?
   Find a mentor, peer group, supervisor, or coach who can challenge you with care.

A useful development rhythm might look like this:

• One monthly mentoring conversation.
• One quarterly review of coaching goals.
• One observed session every few months.
• Regular feedback from teams and leaders.
• A small learning goal for each engagement.

Keep it practical. The goal is better coaching, not a beautiful spreadsheet.

Questions Agile Coaches Should Ask Themselves

Reflection is one of the cheapest and most useful development tools available.

After a coaching session, workshop, leadership meeting, or difficult conversation, ask yourself:

• Did I help the client think more clearly?
• Did I talk too much?
• Did I avoid the real issue?
• Did I respect the client’s context?
• Did I make the team more capable?
• Did I push my preferred method too hard?
• Did I understand the business outcome?
• What would I do differently next time?

These questions are simple. They are also uncomfortable when answered honestly.

That is the point.

Good coaches do not need to be perfect. They need to be awake to their own impact.

How Business Owners Benefit When Coaches Are Coached

This topic is not just for coaches. It matters to business owners too.

If you hire an agile coach, mentor, or consultant, you want someone who is still learning. You want someone who can adapt to your industry, your people, your size, your budget, and your stage of growth.

A coached coach is more likely to:

• Listen before prescribing.
• Explain things in plain English.
• Respect your commercial reality.
• Help your people grow.
• Challenge you without grandstanding.
• Leave useful habits behind.
• Avoid turning Agile into theatre.

That last one matters. Businesses do not need agile theatre. They need better ways of working.

If you are a founder or SME owner, ask potential coaches how they develop themselves. Ask who challenges their thinking. Ask how they handle feedback. Ask what they have changed in their practice over the last year.

Their answers will tell you a lot.

Frequently Asked Questions

What is agile coaching?

Agile coaching helps people, teams, and leaders improve how they work, make decisions, and deliver value. It often combines coaching, mentoring, teaching, facilitation, and practical advice.

Why do agile coaches need coaching?

Agile coaches need coaching because they also develop habits, assumptions, and blind spots. External coaching or mentorship helps them stay effective, ethical, and useful to the people they support.

Is mentorship the same as agile coaching?

No. Mentorship usually involves sharing experience and guidance. Agile coaching often focuses on helping people discover their own answers, although good agile coaches may use both approaches depending on the situation.

How does self-development improve agile coaching?

Self-development improves agile coaching by helping coaches listen better, handle conflict, adapt to different teams, and connect agile practices to real business outcomes.

What should business owners look for in an agile mentor?

Look for someone who explains ideas clearly, understands business pressure, listens well, and can show how their work improves team confidence, delivery, and leadership growth.

Final Thoughts

The best coaches keep learning because the work keeps changing. Teams change, leaders change, markets change, and people bring new challenges into the room every day.

A strong agile mentor does not need to know everything. They need the humility to keep growing, the courage to ask better questions, and the discipline to put people before process. That is why coaches need coaching, and why agile coaching works best when self-development, mentorship, and leadership growth stay at the centre of the craft.