Nobody hires a coach for knowing the Scrum Guide by heart. They hire you because you can walk into a stuck team, read what's really going on from a Jira board and one retro, and change it without taking over. Here's the order to build those skills in.
| Certificate | Best for | Effort | Worth it? |
|---|---|---|---|
| ICAgile Certified Professional in Agile Coaching (ICP-ACC) | Scrum Masters making the jump to their first coaching role | a multi-day workshop, then practice on the job | The certificate most coaching postings name. It teaches actual coaching stances, not just framework rules, so it's worth doing first. |
| Scrum Alliance Certified Team Coach (CTC) | Coaches with a solid track record across several teams | months of documented coaching and a peer review | Hard to earn and respected for that reason. Go for it once you have stories to fill the application, not before. |
| SAFe Practice Consultant (SPC) | Coaches aiming at large companies running SAFe | an intensive course plus an exam | Opens doors at SAFe shops and little else. Skip it unless the jobs you want name it. |
| ICF Associate Certified Coach (ACC) | Coaches who do a lot of one-on-one work with managers | coach training plus logged coaching hours | Not agile-specific, which is the point. It proves you can coach a person, and it sets you apart from coaches who only know frameworks. |
Requirements, fees, and renewal rules change, so check each provider's own site before you sign up.
Agile Coach responsible for supporting teams with Scrum ceremonies and agile best practices.
Coached 6 Scrum teams and 4 Scrum Masters through a move from fixed release plans to quarterly outcome goals, cutting average lead time from 21 days to 9 over two quarters.
It helps, but the practice matters more than the badge. Most coaches spent real time as a Scrum Master or team lead first, because you can't coach a sprint you've never run.
Jira or Azure DevOps for boards and flow data, Miro or Mural for workshops, and Confluence for playbooks. You should be able to build a useful dashboard yourself.
More than people admit. Knowing what continuous integration, trunk-based development, and automated testing look like lets you spot why a team can't finish work inside a sprint. Engineers also trust a coach who understands their build pipeline.
Staying quiet. You'll see the fix before the team does, and saying it feels helpful. Learning to ask the question that gets them there themselves is slow, and it's what separates a coach from a process police officer.