PMP vs Prince2

What two credentials tell you about a field

Originally published at https://pmfieldnotes.substack.com.

A PMP holder has demonstrated knowledge of an integrated body of project management concepts — initiating, planning, executing, monitoring, closing — across ten knowledge areas, with an emphasis on professional judgement applied across them. A Prince2 holder has demonstrated familiarity with a defined methodology — seven principles, seven themes, seven processes — applied through a specific procedural framework. These are not the same skill. The two credentials produce two different kinds of practitioner.

The PMBOK — the body of knowledge PMP is anchored to — is structured around concepts rather than procedures. It tells you what a risk register is, what earned value management is, what scope creep is, why critical path matters. It doesn’t tell you, in much detail, how to run any of these things on a Tuesday morning. The application is left to the practitioner, who is assumed to read the body of knowledge as a foundation and then apply judgement to whatever situation arises.

The exam reflects this. Most questions are scenario-based: a situation is described, four possible responses are offered, and the candidate has to pick the response a competent PM would make. The “competent PM” implied by the exam is someone who knows the framework well enough to apply it intelligently, not someone who follows a fixed procedure.

The methodology is structured around process, not knowledge. It tells you, in detail, what documents to produce, what roles to staff, what stages to pass through, what gates to clear. The “Project Initiation Document,” the “Stage Plan,” the “Exception Plan” — these are named artefacts with prescribed contents. A Prince2-run project produces a particular shape of paper trail, regardless of who’s running it.

The exam reflects this. Many questions test whether the candidate knows what artefact belongs in what stage, what role is responsible for what decision, what the methodology says to do when a particular event occurs. The “competent PM” implied by Prince2 is someone who follows the procedure correctly. The procedure is the discipline.

The strength of this approach is consistency. A Prince2 project run by a junior PM and a Prince2 project run by a senior PM produce the same documentation, follow the same stages, escalate the same way. For organisations that need predictable project governance — government departments, regulated industries, large public-sector contractors — this is genuinely valuable. The methodology compensates for variation in practitioner skill by standardising the work.

If project management were principally a body of knowledge, PMP would be the dominant credential and Prince2 would be a niche specialism within procurement-heavy industries. If project management were principally a methodology, Prince2 would be the dominant credential and PMP would read as too vague to be useful. Neither has happened. Both credentials hold meaningful market share. Some practitioners hold both. Hiring managers list either as acceptable.

What this means is that the field hasn’t agreed on its own foundations. Project management is, depending on who’s asked, a discipline of knowledge applied with judgement (PMP’s frame), a methodology applied with discipline (Prince2’s frame), or — in the most honest answer — both, depending on the project, the organisation, and the practitioner.

The honest answer doesn’t help with credentialing. Credentialing requires a definition of what’s being certified. PMP defines it one way, Prince2 defines it another, and the field has tacitly agreed that both definitions are valid, which is the same as saying neither definition is decisive.

A practitioner with PMP only, applying for a role in a Prince2-defaulted market, reads as partially qualified. The credential isn’t rejected — most hiring managers in those markets will accept it — but it’s read as the foreign credential, the one that needs explaining. The reverse is also true. A Prince2 holder applying in a PMP-defaulted market reads similarly.

Practitioners who work across markets often end up holding both. This is sometimes framed as “stacking credentials” but the underlying reason is that the credentials operate as passports — each one grants access to a particular market, and a practitioner planning to work across markets needs the ones that match their geography. Holding both is less about competence and more about market access. The work behind both credentials is the same; the credential is what unlocks the market.

More field notes on schedule recovery, project controls, and the gap between the plan and the work itself: pmfieldnotes.substack.com

Originally published at https://pmfieldnotes.substack.com.