â–¶How is agile coaching different from Scrum Master?
A Scrum Master owns one team's process and ceremonies. An agile coach works across multiple teams and organizational levels to drive cultural and systemic change. Coaches help discover problems, executives align on vision, and teams adopt sustainable agile practices. It's the difference between facilitating sprints and designing the org's entire operating model.
â–¶Can I become an agile coach without Scrum Master experience?
No. You need 2–3 years as a hands-on Scrum Master or agile practitioner first to understand what works in the trenches. Then pivot to coaching: learn GROW model, study organizational psychology, and practice coaching conversations (not just facilitating ceremonies). Certifications like ICP-ACC require documented coaching hours.
â–¶What's the fastest path to ICP-ACC?
Foundation: ICAgile cert ($300, 1 week). Then: 2–3 months deliberate coaching practice + mentorship + documented reflections. Exam covers GROW, systems thinking, change management, and coaching ethics. Budget $3–5k total (courses + mentorship). Total time: 4–6 months if you're practicing intensely.
â–¶How do I know if I'm good at this?
Metrics: Do teams improve their velocity, quality, and psychological safety after you coach them? Can you identify root causes of dysfunction (org silos, unclear strategy, skill gaps) vs. just improving ceremonies? Do leaders act on your recommendations? Testimonial: 'She helped us see our real blocker wasn't sprints—it was stakeholder alignment.'
â–¶What's the salary difference between Scrum Master and agile coach?
Scrum Master: $80–130k (team-focused, execution). Agile Coach: $110–170k (org-wide, transformation). VP of Agile: $170–280k. The jump comes from scope (org-wide), impact (lasting culture change), and rarity (fewer people master this).
â–¶Is SAFe / LeSS required?
Not required, but valuable context. SAFe teaches enterprise scaling patterns; LeSS teaches lean thinking. Master one after you've coached 2–3 teams. Don't start with frameworks—start with coaching fundamentals and real team dynamics. Frameworks are tools, not the goal.
â–¶How do I handle resistance from teams or execs?
Resistance is data. Instead of pushing, ask: 'What are you protecting by saying no?' Listen for fear (job safety, visibility), confusion (unclear value), or legitimate constraints (time, budget). Address the real concern, not the surface objection. Best coaches earn trust by solving the problems executives care about, not just improving ceremonies.