Examples & writing guide
Agile Coach CV example and writing guide
Updated 30 June 2026
This agile coach CV example shows how to turn coaching work into credible evidence of changed behaviour, smoother delivery and better collaboration. Use it to shape a focused application, whether you coach individual teams or work across a wider organisation.
Examples by experience level
Junior Agile Coach
TemplateTeal Signal2 / 5
Why this works
This agile coach CV sample turns early coaching experience into credible evidence through team-level scope, practical methods and defensible delivery metrics.
Continue writing your CVAgile Coach
TemplateGrey Frame5 / 5
Why this works
This agile coach CV sample shows a clear progression from delivery work into coaching, with credible scope and measured improvements across several teams.
Continue writing your CVSenior Agile Coach
TemplateBlue Horizon3 / 5
Why this works
Shows enterprise-wide coaching scope, leadership influence, capability building and measurable improvements across several teams.
Continue writing your CVJunior vs senior: what changes
| Aspect | Junior | Senior |
|---|---|---|
| Coaching scope | Focus on supporting one or two teams and give clear examples of facilitating communication, collaboration and agile practices. | Show work across several teams or organisational levels, with the scale of the remit stated clearly. |
| Evidence of impact | Use modest, traceable measures such as workshop attendance, impediments resolved or changes in a team's delivery pattern. | Connect coaching to broader outcomes such as throughput gains across teams, fewer open dependencies or progress against transformation milestones. |
| Stakeholder reach | Emphasise day-to-day work with team members and nearby stakeholders. | Show partnership with senior stakeholders and coaching for leaders on decision-making, delegation and psychological safety. |
| Change work | Describe how you helped a team review and adjust its process using stakeholder feedback. | Explain how you co-designed change strategies, shaped current-state and target-state work, and supported adoption across the organisation. |
| Capability building | Show contributions to workshops, team learning and the practical adoption of agile principles. | Demonstrate mentoring and learning programmes for Scrum Masters, Product Owners and Engineering Managers, with the audience, content and results made clear. |
| CV emphasis | Lead with transferable facilitation, communication, problem-solving and learning evidence where direct coaching experience is limited. | Lead with systems coaching, transformation scale, leadership development and measurable outcomes across teams. |
How to write an agile coach CV
Use a reverse-chronological CV and aim for two pages. A longer document may be justified if you have an extensive, directly relevant consulting history, but edit hard: recent coaching work deserves more space than older delivery or operational roles.
Put contact details first, then your personal statement, skills, employment, education and relevant professional development. Keep the layout simple, with clear headings, consistent dates and an ordinary, readable typeface. Do not include a photograph or date of birth.
| Section | What to include |
|---|---|
| Personal statement | Coaching scope, relevant methods and one defensible result |
| Experience | Actions connected to changes in delivery, collaboration or capability |
| Skills | Methods and tools you have used, tailored to the vacancy |
| Education | Exact qualification or course names, providers and dates |
| Extras | Relevant mentoring, speaking, volunteering or published work |
Tailor the first third of your agile coach CV to the vacancy. Make practical knowledge of Scrum, Kanban and Lean easy to find where the post asks for it, along with genuine experience of JIRA and Confluence. In employment entries, explain whom you coached, the issue you tackled and what changed. State the scale clearly, whether that was one team, several squads or a wider organisational programme.
Avoid graphics, proficiency bars and crowded columns. They take up space without proving anything. Three or four strong bullets for each recent role will usually communicate more than a long list of routine duties.
Personal statement examples
Agile Coach with seven years' experience supporting product and engineering teams through practical changes to planning, collaboration and continuous improvement. Coached six squads through dependency mapping and joint refinement, reducing open cross-team dependencies by 31% over two quarters. Confident facilitating teams and leaders, applying Scrum, Kanban and Lean, and using JIRA and Confluence to make delivery patterns visible.
Enthusiastic Agile Coach who is passionate about transformation and helping people succeed. I am a good communicator, work well with everyone and understand many agile ways of working. I am looking for an exciting role where I can use my skills and continue learning.
Writing your experience
An Agile Coach experience section should answer a simple question: what changed because of your work? Build each bullet around action + coaching scope + intervention + measured result. Scope gives the reader context, so name the teams, squads, leaders or practitioners involved. Then connect your work to an observable change in throughput, unresolved dependencies, cycle time, adoption or capability.
| Too vague | Stronger version |
|---|---|
| Helped teams improve agile processes. | Coached four product squads through fortnightly retrospectives and impediment reviews, cutting unresolved blockers older than ten days from 18 to 7 within one quarter. |
| Facilitated collaboration across departments. | Introduced monthly dependency mapping and joint refinement across five squads, reducing open cross-team dependencies by 28% over six months. |
| Trained colleagues in agile methods. | Designed six workshops on story slicing and facilitation for 24 delivery practitioners; 19 participants applied the techniques within eight weeks. |
These rewrites work because each gives the intervention, audience and result. They do not pretend that coaching caused every business outcome. When several factors influenced the result, say that your work "contributed to" it or specify the portion you owned. Use figures taken from records, feedback or agreed measures, never estimates created for the CV.
For team-level work, evidence may cover teaching agile principles and processes, strengthening communication, addressing impediments or helping teams focus on customer value. A broader post may call for examples of systems coaching, transformation across organisational levels, leadership development or jointly designed change strategies. Senior candidates should make their reach visible, perhaps through the number of teams supported, the leaders coached, transformation milestones reached or cross-team dependencies reduced.
Strong verbs include coached, facilitated, mentored, diagnosed, introduced, redesigned, mapped, advised, taught and removed. Follow the verb with the people affected and the practical result. "Responsible for coaching teams" only repeats a duty; "Coached three squads to establish weekly blocker reviews, reducing aged impediments by 40%" supplies scale and movement.
Use three or four substantial bullets for each recent role. Give older positions fewer, retaining only the achievements that support your current level. If you are moving into coaching from a project manager role, draw on real examples of facilitation, stakeholder engagement, teaching or process improvement, but describe the original context honestly.
Key skills & ATS keywords
Hard skills
Soft skills
ATS keywords
Education & certifications
Put education and professional development after employment unless recent study is your strongest evidence for moving into Agile coaching. List items in reverse-chronological order, using the exact title, provider and completion year. If study is unfinished, state that clearly and give the expected completion date rather than implying that you already hold the award.
Do not use education as a substitute for applied evidence. Connect relevant learning with workshops delivered, teams coached, stakeholder conversations facilitated or organisational problems addressed. Career changers can draw on earlier work involving facilitation, organisational change and stakeholder engagement, provided they explain the connection accurately instead of relabelling previous duties as coaching.
AgilePM® Practitioner certification is an optional professional-development route. It develops practical Agile-methodology knowledge and may support progression towards senior Agile project roles, including Enterprise Agile Coach. Present the exact title if you hold it, but do not frame it as an entry requirement.
ICP-ACC, issued by IC Agile, addresses coaching of individuals, teams and organisations as distinct scopes. Candidates who hold it should use the exact credential and issuer names, then support the listing with employment evidence showing the coaching scopes they have actually handled. Attendance alone should not be presented as completed certification.
For an Enterprise Agile Coach CV, give more weight to evidence of scale than to a long course list. Relevant career guidance supports describing experience across multiple large and complex Agile transformations, with the organisational context stated precisely. Add internal learning programmes, mentoring or workshops only when they help a reader understand your capability. Leave out generic webinars that add no useful evidence.
Common mistakes to avoid
AvoidListing ceremonies and workshops without showing what changed for the teams involved.
InsteadConnect each coaching action to a defensible result, such as improved throughput, fewer open dependencies or a measurable change in team practice.
AvoidDescribing the remit vaguely, with no indication of how many teams, squads or engineers were supported.
InsteadState the coaching scope wherever possible, using only figures you can defend.
AvoidPresenting JIRA, Confluence, Scrum, Kanban and Lean as a keyword block with no evidence of their use.
InsteadPlace tools and methods in achievement bullets that explain the problem, intervention and outcome.
AvoidWriting a senior Agile Coach CV entirely around team ceremonies.
InsteadAdd evidence of leadership coaching, transformation roadmaps, organisational change and work across multiple levels when that reflects your experience.
AvoidClaiming ownership of team results without explaining the coaching contribution.
InsteadUse precise verbs such as coached, facilitated, mentored and co-designed, then distinguish your intervention from the team's delivery.
AvoidUsing unsupported percentages or estimates to make coaching work sound more impressive.
InsteadUse only figures you can defend. If no reliable metric exists, give concrete scope, frequency and an observable before-and-after change.
Frequently asked questions
Two pages is a sensible target for most candidates. Keep it shorter only if you are early in your career; senior candidates should still edit firmly and retain the evidence that shows coaching scope, leadership reach and outcomes.
Use examples from delivery, facilitation, mentoring or change work where you helped teams adopt agile practices, improve collaboration or address impediments. Make your contribution explicit and avoid presenting participation in ceremonies as coaching experience on its own.
Use figures that show how teams visibly changed, such as defensible throughput gains, reductions in open dependencies, the number of teams supported or progress against transformation milestones. Never estimate a number simply to strengthen the CV.
A senior CV should show work across multiple levels, systems coaching, transformation roadmap delivery and leadership development. A junior CV can concentrate on team facilitation, communication, collaboration, impediment work and continuous improvement.
No. A British-style CV does not need either; use the space for relevant experience, skills and measurable evidence.
Match your evidence to the vacancy's scope rather than copying phrases wholesale. If the post stresses team coaching, prioritise facilitation and impediment work; if it covers enterprise change, bring forward transformation, systems coaching and senior stakeholder evidence.
From example to application
Turn this agile coach example into a CV that sounds like you.
Keep the structure that works. Tailor the details around your experience, strengths, and the role you want.