How Is AgilePM v3 Different From v2?

A delegate asked me last month whether her AgilePM Foundation certificate, taken under v2, still meant anything. She had seen a training provider's email announcing v3 and assumed, reasonably enough, that the framework underneath her had shifted while she wasn't looking.

It's a fair question, and it comes up more than once a quarter now. AgilePM has been the standard combination of structure and flexibility for UK project managers working in agile or hybrid environments since 2010, and for most of that time the framework barely moved. Then the Agile Business Consortium and APMG International released v3, and the update has been rolling through training providers, exam schedules and reference material for the best part of two years.

The instinct, when a certification body announces a new version, is to assume everything underneath has changed and start worrying about whether existing knowledge has quietly expired. That instinct is usually wrong, and it's worth resisting here too. But it's also worth being precise about what actually did change, because the answer isn't nothing.

Start with what didn't move. The framework is still built on DSDM Atern as its underlying method. The eight principles that define AgilePM thinking, prioritise ruthlessly, deliver on time, never compromise quality and the rest, are the same eight principles. The lifecycle phases haven't been restructured, and the set of defined roles across the project, whether you're the Business Sponsor, the Team Leader or the Business Ambassador, are the roles you already know. MoSCoW prioritisation still sits at the centre of how scope gets managed. If you learned AgilePM properly under v2, you didn't learn a framework that has since been quietly retired underneath you. The scaffolding is intact.

What did change sits mostly in emphasis and integration rather than structure. The most significant shift is that Scrum is now built into the delivery engine as a core component, not referenced alongside AgilePM as a separate discipline a practitioner might also happen to know. For anyone working in an organisation where delivery teams already run sprints inside a governance wrapper, that's less a new idea than a formal acknowledgement of what was already happening on the ground. Version 2 assumed you'd bring your own delivery mechanics. Version 3 assumes Scrum is one of them and teaches it as part of the syllabus rather than leaving it as a gap the practitioner has to fill from elsewhere.

The second real change is where the emphasis sits: outputs versus value. AgilePM v2 was, in practice, easy to teach and easy to apply as a project that delivers defined products on time. V3 pushes harder on the distinction between delivering a product and delivering the value that product was meant to create, which sounds like a subtle reframing until you watch it play out in a live project. I've sat through governance reviews where a team proudly reports every deliverable shipped on schedule, and the sponsor's actual question is whether the business changed as a result. V3 builds that question into the framework itself rather than leaving it as something a good practitioner happens to ask anyway.

There's also a genuine shift toward multi-team and scaled delivery. AgilePM was originally built with something closer to a single project team in mind. As organisations have grown their agile footprint, running several delivery teams against one programme of work has become the normal case rather than the exception, and v3's guidance reflects that, with clearer material on coordinating across teams rather than assuming one team, one board, one rhythm.

None of this changes whether a v2 certificate is still valid. It is. Anyone holding a v2 Foundation or Practitioner certificate keeps it, and organisations that recognise AgilePM as a qualification still recognise the v2 version sitting on someone's CV. What has changed is availability going forward. V2's English-language exams were originally scheduled to retire in the summer of 2025, then the date moved as the v3 Practitioner exam release itself was delayed, and the final English v2 exams were retired in November 2025. If you haven't started AgilePM yet, v2 isn't an option any more, and the practical question isn't whether to learn v3, it's simply what v3 now covers that v2 didn't.

The one genuine complication sits at the Foundation to Practitioner boundary. If you hold a v2 Foundation pass but haven't yet sat Practitioner, you can't carry that straight into a v3 Practitioner exam. APMG requires a v3 Foundation pass before you can sit v3 Practitioner, which means anyone caught mid-qualification when the version changed has to requalify at Foundation level under the new syllabus before progressing. It's a genuine cost in time for a small group of people, and it's the detail that catches candidates out when they assume "I've already done Foundation" settles the question.

For a delegate deciding where to start now, the practical answer is simple. You're learning v3, because that's the only version being examined. What matters is understanding it as an evolution of a framework you may already half know from working in a hybrid environment, not a new discipline to master from nothing. The structure is familiar. The emphasis has moved toward what a team actually running Scrum inside AgilePM governance already needed the framework to say.

If you're weighing up AgilePM against another route into agile and hybrid delivery, or you're not sure which certification actually matches the way your organisation runs projects, get in touch about your training options and we can talk through what fits.

Andre Malowney is a project management trainer accredited across PMI, APMG, APM and PeopleCert frameworks, working with both traditional plan-driven practitioners and Agile delivery teams. Find him on LinkedIn: www.linkedin.com/in/andremalowney.