Which Agile Certification Suits a PM, a BA, or a Programme Manager?

Someone will ask this in almost every cohort, usually near the end of a Foundation course, once they've realised how much ground the framework actually covers. "So which one should I have done." Not a question about content. A question about whether they picked the right certificate in the first place.

It's a fair worry, because the honest answer is that AgilePM, AgileBA and AgilePgM sit next to each other on the same accreditation page, share the same DSDM ancestry, and get talked about as though they're three difficulty settings on the same product. They aren't. They were built for three different jobs, and the confusion tends to survive right up until someone sits in the wrong course and spends three days waiting for content that was never going to arrive, because it belongs to a different role entirely.

Part of the problem is how these certifications get marketed. "Agile project management certification" sounds like the umbrella term for the whole family, so people assume AgilePM is the default and the other two are specialist add-ons for people who want to go further. That reading collapses the moment you look at who each one was actually written for. AgilePM assumes you are the person accountable for a delivery: running the project, managing the plan, answerable for the timebox slipping. AgileBA assumes you are the person in the room translating business need into something a delivery team can actually build, holding the requirements and the priorities steady while the solution takes shape. AgilePgM assumes you are neither of those. You are looking across several projects at once, worrying about whether they still add up to the outcome the organisation actually paid for.

Those are not the same worry, and a certification written for one doesn't quietly cover the other two on the side.

Take AgilePM first, since it's the one most people land on by default. It has its roots in DSDM, which predates the Agile Manifesto and was built with a project-focused, often IT-flavoured audience in mind: fixed time, fixed cost, flexible scope, delivered through timeboxed iterations rather than a single upfront plan. The Foundation qualification checks that you understand the philosophy, the lifecycle and the roles involved. Practitioner is the harder test, an open-book, scenario-based exam that asks you to apply the framework to a situation rather than recall it from a manual. If your actual job is running the delivery, being accountable for what gets built and when, this is the certification with your name on it. It sits comfortably alongside PRINCE2, which is exactly why so many plan-driven PMs end up here first: it speaks a dialect close enough to governance that the transition doesn't feel like starting over.

AgileBA belongs to a different person in that same delivery, and it's worth being specific about who. A business analyst working on an agile project isn't writing a static requirements document once at the start and stepping back. They're holding the thread between what the business actually needs and what the team is capable of building inside the timebox, re-prioritising constantly as the picture sharpens. AgileBA tests exactly that: eliciting and prioritising requirements in a fast-moving environment, working the MoSCoW technique properly rather than just naming it, understanding where a BA's authority starts and a project manager's begins. A PM who takes AgileBA hoping it will round out their delivery skills usually finds it doesn't teach delivery at all, because that was never the point. It teaches a discipline that sits beside delivery, not underneath it.

AgilePgM is the odd one out, and worth naming as such rather than treating it as "AgilePM, but bigger." Managing a single agile project and managing a programme of them are genuinely different problems. A programme manager isn't timeboxing a delivery. They're holding several deliveries in view at once, checking that the sum of what's shipping still points at the strategic outcome the organisation actually funded the work for, and making the calls about sequencing, dependency and investment that no single project team is positioned to make. The Foundation exam reflects that different altitude: fifty closed-book questions, no prerequisite, built to check that you understand programme-level thinking rather than project mechanics. Someone who has run delivery for years but never had to hold three workstreams against one business case at the same time will find this course teaching something genuinely new, not a repeat of what AgilePM already covered.

A team lead we worked with recently had exactly this pattern play out badly before it played out well. Two project managers on the same programme both went straight for AgilePM Practitioner because it was the certificate everyone else on the delivery floor already had. Six months later, one of them was quietly doing programme-level work anyway, coordinating three interdependent workstreams because nobody else was positioned to, without a certification that matched what the job had actually become. The fix wasn't more delivery training. It was AgilePgM, because the role had already outgrown the certificate.

None of this means picking one closes the door on the others. Plenty of practitioners end up holding two, usually AgilePM alongside AgileBA if they move fluidly between delivery and analysis work, or AgilePM alongside AgilePgM as they step up from project to programme accountability. What doesn't work is choosing by popularity, or by whichever course a colleague happened to recommend. The honest starting question isn't which certification is best regarded. It's what you're actually accountable for on a Monday morning, because that's the job each of these three was built to certify, and the fastest route through any of them is choosing the one that already matches the work you do rather than retrofitting the work to the certificate. If you're still weighing which of the three fits where you sit right now, get in touch about your agile training options and we'll talk it through against your actual role, not just the course catalogue.

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.