Was this sample helpful? Rate it!
Average: 4.8 (29 votes)
Contents
Key Takeaways for an Agile Project Manager Resume
Why This Agile Project Manager Resume Works
How to Write an Agile Project Manager Resume That Gets Interviews
What to Include in an Agile Project Manager Resume
Agile Project Manager Resume Summary Examples
Agile Project Manager Work Experience Examples
Top Agile Project Manager Skills
Agile Project Manager Certifications
Common Agile Project Manager Resume Mistakes
Agile Project Manager Resume FAQs
Summary
Agile project manager with eleven years delivering software through agile teams for technology companies in Leeds. Runs agile delivery end to end — facilitating Scrum, coaching teams, managing backlog, risk and stakeholders, and removing the blockers that slow delivery. Led an agile transformation across teams that improved predictability and shortened delivery cycles. Acts as Scrum Master and delivery lead, runs ceremonies and planning, manages dependencies and reporting, and keeps stakeholders aligned and teams focused. Strong on both the agile craft and the people and stakeholder skills delivery demands. Servant-leader by instinct and calm when priorities shift. Looking for an agile-project-manager, Scrum Master or delivery-lead role with a team that wants to ship reliably and keep improving.
Work History
Agile Project Manager
Leeds Technology Group, Leeds, UK
Apr 2016 – Present
- Run agile delivery end to end, facilitating Scrum and coaching delivery teams.
- Led an agile transformation across teams that improved predictability and shortened delivery cycles.
- Run ceremonies, planning and backlog management and remove blockers for the team.
- Manage dependencies, risk and stakeholder reporting across deliveries.
- Keep stakeholders aligned and teams focused on the highest-value work.
- Coach teams toward better agile practice and continuous improvement.
Scrum Master / Project Lead
Yorkshire Software Solutions, Leeds, UK
Aug 2010 – Mar 2016
- Facilitated Scrum teams and led delivery on software projects.
- Managed backlog, ceremonies and stakeholder communication for teams.
- Learned agile delivery, facilitation and scaling on the job.
- Gained Scrum and SAFe certification and an agile-PM role.
Qualification
BSc (Hons) Computer Science, Computer Science
University of Leeds
Sep 2007 – Jun 2010
- Computer science degree covering software, systems and delivery, with a placement. The placement led into software delivery and agile. Built the technical foundation behind delivery leadership.
Professional Scrum Master & SAFe Certification, Agile Delivery
Scrum.org / Scaled Agile
Jan 2013 – Aug 2013
- Professional Scrum Master and SAFe certification covering agile delivery, facilitation and scaling. They formalised the agile frameworks used daily. Applied directly to running agile teams and the transformation.
Highlights
Agile transformation
- Led an agile transformation across teams that improved predictability and shortened delivery cycles. Helping teams deliver more reliably is exactly what agile delivery is for.
Unblocks the team
- Removes blockers and keeps teams focused on the highest-value work as a servant-leader. A good agile PM makes the team's job easier, not harder.
Certifications
Professional Scrum Master & SAFe
Scrum.org / Scaled Agile
Aug 2013 – Present
- Professional Scrum Master and SAFe certification covering agile delivery, facilitation and scaling. They formalised the agile frameworks used daily. Applied directly to running agile teams and the transformation.
Multi-Team Agile Transformation
Multi-Team Agile Transformation
Jan 2018 – Jun 2019
- Led an agile transformation across several delivery teams, introducing consistent ceremonies, metrics and backlog practice, which improved delivery predictability and shortened cycle times across the department.
Languages
- English (UK) — Native or Bilingual Proficiency
- German — Limited Working Proficiency
Technical Skills
- Agile Delivery
- Scrum Facilitation
- Backlog Management
- Team Coaching
- Dependency Management
- Risk Management
- Stakeholder Management
- SAFe / Scaling
- Delivery Reporting
- Continuous Improvement
Personal Skills
- Servant Leadership
- Communication
- Composure
- Facilitation
- Pragmatism
Activities & Interests
- Ski
- Cooking
- Play Piano
- Pool
- Socialising
Key Takeaways for an Agile Project Manager Resume
Before the detail, here is what a delivery manager screening your resume is really looking for:
- Show delivery outcomes, not ceremony attendance. Predictability, cycle time and throughput matter more than "facilitated daily standups".
- Name your framework and scale. Scrum, Kanban, SAFe or LeSS, and whether you ran one team or coordinated many, sets your level immediately.
- Prove you remove blockers. The core of the job is unblocking teams and managing dependencies, so make that visible with real examples.
- Quantify with agile metrics. Velocity stability, lead time, escaped defects, release frequency and sprint predictability are the numbers that read as credible.
- Balance the craft and the people. Stakeholder management and coaching sit alongside the mechanics of Scrum, and strong candidates show both.
- Signal servant leadership over command. Hiring teams screen out project managers who run agile like a Gantt chart, so frame yourself as an enabler.
Why This Agile Project Manager Resume Works
The sample lands because it reads like a delivery leader who improves teams, not a ceremony administrator. Here is what it gets right:
- The summary states outright that the person runs delivery end to end and names the real work: facilitation, coaching, backlog, risk, stakeholders and blocker removal.
- It leads its headline achievement with a transformation that improved predictability and shortened delivery cycles, which are the two outcomes delivery managers actually reward.
- It positions the person as both Scrum Master and delivery lead, so a reader knows they operate at the team and the programme level.
- The progression from Scrum Master to agile project manager, with Scrum and SAFe certification earned along the way, tells a coherent growth story.
- The Multi-Team Agile Transformation project is scoped and time-boxed, showing scaling work across several teams rather than a vague claim of "agile experience".
- The servant-leader framing runs through the whole document, which is exactly the instinct that separates an agile PM from a traditional one.
How to Write an Agile Project Manager Resume That Gets Interviews
A delivery manager scanning your resume wants to see framework, scale and evidence you make teams deliver more reliably. Write for that:
State your framework and scale in the first line
Open with what you run and how big it is: "Agile project manager running four Scrum teams under SAFe" tells the reader your world instantly. Naming Scrum, Kanban or SAFe and the number of teams sets your level before they read a single bullet.
Lead achievements with delivery outcomes
Frame wins around predictability, speed and quality. "Improved sprint predictability from 60 to 90 percent and cut lead time from 21 to 12 days by rebalancing team dependencies" reads far stronger than "ran sprint planning and retrospectives."
Make blocker removal and dependency management visible
The heart of this role is clearing the path for the team. Show it: "unblocked a stalled release by renegotiating a shared-service dependency, recovering a two-sprint slip" demonstrates the judgement hiring managers screen for.
Quantify with metrics that agile people trust
Velocity stability, cycle and lead time, release frequency, escaped defect rate and sprint predictability all read as credible. Avoid inventing precise velocity points; use trends and percentages that a delivery manager would recognise as real.
Show the coaching and stakeholder side
Agile delivery is half craft and half people. Reference coaching teams toward better practice and keeping stakeholders aligned when priorities shift, which signals you lead the human system, not just the board.
Want the layout handled so you can focus on delivery outcomes? Draft yours in minutes with our free resume builder and keep the structure recruiters expect.
What to Include in an Agile Project Manager Resume
Beyond the usual sections, these carry particular weight for a delivery hire:
The frameworks you actually run (Scrum, Kanban, SAFe, LeSS) and the scale, since a single team and a scaled programme are different jobs.
Your tooling: Jira, Azure DevOps, Confluence and any reporting or metrics dashboards you built.
A named transformation or scaling project with a measurable delivery outcome, like the sample's multi-team transformation.
Certifications from Scrum.org, Scrum Alliance, PMI or Scaled Agile, which are close to table stakes for interviews.
Delivery metrics woven into the bullets: predictability, cycle time, release cadence and quality trends.
Agile Project Manager Resume Summary Examples
Model the top of your resume on these, matched to your level and whether you work at team or programme scale:
Entry-level resume summary example
Certified Scrum Master with three years facilitating two software delivery teams in a product organisation. Runs the full ceremony set of planning, daily standups, reviews and retrospectives, and manages a backlog of 200-plus items alongside the product owner. Improved one team's sprint predictability from 55 to 85 percent over four months by tightening story sizing and cutting mid-sprint scope changes. Comfortable in Jira and Confluence, and used to surfacing dependencies and impediments early. Holds a Professional Scrum Master I certification and coaches developers new to agile on estimation and definition of done. Looking to grow into an agile project manager or delivery lead role coordinating multiple teams.
Mid-level resume summary example
Agile project manager with seven years delivering software through Scrum and Kanban teams in fintech and SaaS. Runs delivery end to end for three teams, managing backlog, risk, dependencies and stakeholder reporting while coaching teams toward stronger practice. Led an agile transformation across a department that lifted delivery predictability from 60 to 90 percent and shortened average lead time by a third. Fluent in Jira, Azure DevOps and flow metrics, and trusted to keep stakeholders aligned when priorities shift. Servant-leader by instinct and calm under changing scope. Seeking a delivery lead or agile PM role with a team that wants to ship reliably and keep improving.
Senior-level resume summary example
Senior agile delivery lead with twelve years scaling software delivery across multiple teams and programmes. Runs delivery for a 40-person engineering group under SAFe, coordinating a program increment cadence, managing cross-team dependencies and reporting delivery health to executives. Led two agile transformations that improved release frequency from quarterly to fortnightly and cut escaped defects by 40 percent. Coaches Scrum Masters and product owners, and pairs deep agile craft with the stakeholder and risk management that programme delivery demands. SAFe and Professional Scrum certified, servant-leader in style, and looking for a head of delivery or agile programme lead role where predictable, improving delivery is the mandate.
Agile Project Manager Work Experience Examples
Model your bullets on these, matched to your framework and scale. Each pairs a delivery action with a measurable outcome:
Scrum Master / single team
- Facilitated the full Scrum ceremony set for a nine-person team, improving sprint predictability from 58 to 88 percent over two quarters by tightening story sizing and reducing mid-sprint scope change.
- Cut average lead time from 19 to 11 days by mapping the team's end-to-end workflow and removing two recurring handoff bottlenecks between development, the product owner and QA that had quietly stalled delivery.
- Coached five developers new to agile on estimation, work-in-progress limits and definition of done, which lifted the team's forecast accuracy and steadily cut carried-over work sprint over sprint.
- Surfaced and cleared impediments daily, escalating a shared-service dependency that had blocked two committed stories and recovering a full sprint of work by renegotiating the delivery order with another team.
Scaled agile / SAFe programme
- Coordinated program increment planning across four Scrum teams under SAFe, managing cross-team dependencies that had previously caused a 30 percent quarterly slip down to near zero.
- Introduced consistent flow metrics and a shared delivery dashboard across the programme, giving stakeholders a single, trusted view of delivery health each fortnight and ending the weekly round of status-chasing meetings.
- Ran a dependency and risk cadence with release train engineers that improved on-time feature delivery from 65 to 92 percent over three program increments, with no increase in overtime or weekend work.
- Facilitated inspect-and-adapt workshops that produced concrete, team-owned process changes, cutting the programme's average defect escape rate by a third and shortening the time to resolve cross-team blockers.
Agile transformation / delivery lead
- Led an agile transformation across six delivery teams, standardising ceremonies, backlog practice and metrics, which improved delivery predictability and shortened average cycle time by 40 percent.
- Moved a department from quarterly to fortnightly releases by introducing continuous delivery practices and rebalancing team dependencies, with no rise in production incidents across the following two quarters.
- Coached and mentored four Scrum Masters and three product owners on facilitation and backlog practice, raising the group's agile maturity assessment scores measurably over a single year.
- Rebuilt stakeholder reporting around delivery outcomes rather than task status, which restored executive confidence in the teams and secured continued investment in the transformation for a second year.
Top Agile Project Manager Skills
Name the frameworks, tools and delivery disciplines explicitly so both the hiring manager and the ATS pick them up:
Hard skills
- Scrum facilitation
- Kanban and flow management
- SAFe and scaled agile
- Backlog management and refinement
- Sprint and release planning
- Dependency management
- Risk and issue management
- Agile metrics (velocity, lead and cycle time, throughput)
- Jira administration
- Azure DevOps
- Confluence
- Stakeholder management and reporting
- Team coaching and agile maturity
- Continuous improvement and retrospectives
- Roadmap and delivery forecasting
- Impediment and blocker removal
- Estimation and capacity planning
- CI/CD and continuous delivery awareness
Soft skills:
- Servant leadership
- Facilitation
- Composure under changing priorities
- Clear communication
- Pragmatism
- Conflict resolution
- Coaching mindset
Agile Project Manager Certifications
Agile certifications are close to table stakes for interviews, so list the ones that match your framework and scale:
-
PSM I
— Scrum.org Rigorous, no-expiry Scrum credential; PSM II signals deeper mastery for senior roles.
-
CSM
— Scrum Alliance The most widely recognised entry Scrum Master cert; requires a course and renews every two years.
-
SAFe Agilist
— Scaled Agile The credential to hold when you work at programme scale; the sample's SAFe certification sits here.
-
PMI-ACP
— Project Management Institute Framework-agnostic; useful when you span Scrum, Kanban and hybrid delivery and want a PMI-backed credential.
-
PSPO I
— Scrum.org Optional but valuable if you partner closely on backlog and product decisions.
Common Agile Project Manager Resume Mistakes
These are the errors that make an experienced delivery lead read like a process administrator:
- Listing ceremonies as achievements. "Ran standups, planning and retrospectives" is a duty, not a result. Attach a delivery outcome to the facilitation instead.
- Hiding the framework and scale. If a reader cannot tell whether you ran one team or a scaled programme, they cannot place your seniority.
- Running agile like a Gantt chart. Command-and-control language ("assigned tasks", "tracked to plan") signals you missed the point of servant leadership.
- No delivery metrics. Without predictability, cycle time or release cadence figures, the resume reads as activity with no evidence of impact.
- Inventing precise velocity numbers. Fabricated velocity points read as false to any agile practitioner; use trends, percentages and time-based metrics that hold up.
- Ignoring the stakeholder and coaching side. Focusing only on mechanics misses half the job, since aligning stakeholders and coaching teams is what senior roles reward.
- Certification soup with no context. Ten acronyms with no delivery evidence behind them looks like box-ticking; pair each credential with real work.
Agile Project Manager Resume FAQs
The questions candidates most often search when writing an agile project manager resume:
Lead with Scrum and Kanban facilitation, backlog and dependency management, agile metrics and stakeholder management, plus your tooling (Jira, Azure DevOps). Pair those with servant leadership and team coaching, since the people side is half of the job.
Name the frameworks you run and the scale (one team or a scaled programme), then attach delivery outcomes such as improved predictability or shorter lead time. Certifications and a named transformation project make the experience concrete rather than claimed.
It is not strictly required, but a Scrum (PSM or CSM) or SAFe certification is close to expected at interview stage. They confirm you know the framework properly, and SAFe in particular matters once you work across multiple teams.
Use sprint predictability, cycle and lead time, throughput, release frequency and escaped defect rate. These read as credible to a delivery manager; avoid inventing exact velocity points, which experienced practitioners spot as fabricated.
One page for under ten years of experience, two once you are running programmes and coaching other Scrum Masters. Keep it to two at most and front-load the delivery outcomes so the impact is visible fast.
A Scrum Master resume centres on facilitating and coaching a single team. An agile project manager resume adds delivery ownership across teams: dependencies, risk, stakeholder reporting and often scaling, so it should show breadth beyond one team's ceremonies.
Yes. Name Jira, Azure DevOps and Confluence explicitly, because recruiters and applicant tracking systems match on exact tool names. If you built dashboards or configured workflows, say so, since that signals hands-on delivery control.
Get Started With Our
Free Resume Creator today!
Free sign-up. No credit card required.
