Can You Upgrade Your AgilePM v2 Certificate to v3?


Can You Upgrade Your AgilePM v2 Certificate to v3?

A delegate asked us this after checking her v2 Foundation certificate against a v3 Practitioner course she wanted to book. She'd assumed the two versions would simply line up, the way a driving licence stays a driving licence whichever year you passed. She was part way through the booking form when the prerequisite field rejected her v2 certificate outright, and she came to us more confused than annoyed, wanting to know what she'd actually got wrong.

Nothing, as it turns out. The confusion is built into how AgilePM v3 was rolled out, not into anything she missed reading.

Here is the part most people get right instinctively: a v2 certificate does not expire. If you passed Foundation or Practitioner under the old scheme, that credential stays on your CV and stays valid, with no renewal date attached and no clock quietly running down in the background. Nobody is going to email you to say it has lapsed, because it hasn't, and it won't.

Here is the part almost nobody gets right on first guess: none of that means your certificate has become, or will become, a v3 certificate. There is no conversion process running behind the scenes. Passing v2 Foundation does not automatically register you as v3 Foundation certified, and it never will, however long you wait. The two schemes sit side by side rather than one quietly turning into the other.

This matters most at the exact point our delegate hit it: the Practitioner prerequisite. AgilePM v3 Practitioner has one accepted route in, and that route is a v3 Foundation pass. A v2 Foundation certificate, however solid, is not accepted as the prerequisite. If your plan is to sit Practitioner under the new scheme, the certificate you already hold does not shorten that path at all. You start the Foundation stage again, this time under v3 content.

That is easy to hear as bad news, and worth sitting with for a moment rather than rushing past. Nobody enjoys being told a qualification they worked for doesn't carry forward the way they assumed. But it is worth separating two different questions that tend to get run together: whether your existing certificate still counts for anything, and whether it gets you further into v3. The answer to the first is yes, unreservedly. The answer to the second is no, and pretending otherwise doesn't change the booking form.

The genuinely useful piece, and the one that rarely makes it into the panic, is that nobody expects you to treat this as starting from zero. Training providers accredited to teach AgilePM v3 typically offer a shorter conversion route specifically built for v2 certificate holders: a condensed course, sometimes as little as a day, that focuses on what actually changed rather than re-teaching material you already know cold. It leads into the same v3 Foundation exam everyone else sits, often at a reduced rate for people who can show an existing v2 certificate, but it is genuinely faster than approaching v3 with no prior AgilePM background at all. What it is not is a rubber stamp. You still sit the exam. You still need to pass it. The shortcut is in the study time, not in the credential itself.

It also helps to know what you're actually being asked to learn, rather than treating v3 as a vague refresh. The most substantial shift is in what the framework is optimised around. Version 2 was built primarily around delivering agreed products to an agreed timebox. Version 3 pushes that further, toward delivering measurable business value and asking the project team to hold some genuine leadership over how that value gets realised, not just how the work gets scheduled. Scrum sits more explicitly inside the delivery mechanics than it did before, and there's more structured guidance for running multiple teams against the same plan, which reflects how a lot of AgilePM work actually looks in practice now compared to a decade ago.

None of that is a reason to treat your v2 background as wasted effort. The underlying discipline, timeboxing, MoSCoW prioritisation, the roles and responsibilities model, carries across in spirit even where the emphasis has moved. Most v2 holders who go through the conversion route describe it as building on what they know rather than replacing it, which is exactly what a bridging course is designed to do.

What isn't available, and what's worth being direct about, is a route that gets you from v2 to v3 without sitting an exam. If your current plan assumes there's a form to fill in, a fee to pay, and a new certificate to arrive in the post, that plan is based on a version of AgilePM that doesn't exist. The honest starting point is simpler than that: decide whether you actually need v3, based on what your next role or your current employer is asking for, and if the answer is yes, book the conversion route rather than the certificate you already hold. If you're weighing that decision against what a specific employer or contract actually requires, get in touch about your AgilePM training options and we'll talk it through against your situation rather than the general case.

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.