Agile Coach CV example and writing guide

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.

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.

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.

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.

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.