What Order Should You Take PRINCE2, MSP, MoP and MoR In?

Every so often a delegate finishing PRINCE2 Practitioner asks the same question, almost apologetically, as if it should have an obvious answer. What's next. MSP. MoR. Or is it MoP. Nobody seems entirely sure, and the training marketplace doesn't help, because most of it is written to sell the next course rather than to answer the question honestly.

The instinct is to treat this like a syllabus with a correct running order, the way GCSEs lead to A-levels lead to a degree. Get PRINCE2 out of the way, then work through the others in whatever sequence the training provider's brochure happens to list them. That instinct is understandable. It's also the wrong model for what these four qualifications actually are.

None of them formally require any of the others. PRINCE2 Foundation has no prerequisite. MSP Foundation has no prerequisite. MoP Foundation has no prerequisite. M_o_R Foundation has no prerequisite. Each one only gates its own Practitioner level, so PRINCE2 Practitioner needs PRINCE2 Foundation, MSP Practitioner needs MSP Foundation, and so on. There is no rule anywhere in PeopleCert's certification structure that says you must hold PRINCE2 before you're allowed to sit MSP, or MoP before MoR. If someone tells you otherwise, they're describing a training provider's packaging, not an actual requirement.

That surprises people, because the four do feel like they belong on a ladder. They do, just not the kind of ladder with locked doors. It's closer to a ladder of scope.

PRINCE2 governs a single project. It gives you the roles, the stages, the tolerances, the paperwork that makes one defined piece of work controllable from initiation to closure. MSP governs a programme, a coordinated set of projects being run together to deliver a strategic outcome that no single project could deliver alone. MoP sits a level above that again. It governs the whole portfolio, the entire set of projects and programmes an organisation is running or considering running, and it's concerned with a different question entirely: not how do we deliver this well, but should we be doing this at all, and at whose expense.

That progression, project, then programme, then portfolio, is why most people's actual career order ends up matching their actual career scope. A project manager moving into programme delivery studies MSP next because their job just changed shape underneath them, not because a syllabus told them to. Someone stepping into a portfolio office or an investment decision role studies MoP because that's now genuinely the work, prioritising competing initiatives against limited funding and capacity. The order tends to track the job, not the other way round.

Where this gets more interesting is M_o_R, because it doesn't sit neatly on that same ladder at all. Risk isn't a level above programme and below nothing. It's a discipline that runs through project, programme and portfolio simultaneously. A risk on a single project can escalate into a programme risk. A concentration of similar risks across several programmes becomes a portfolio-level concern about the organisation's overall exposure. Treating MoR as the fourth stop after MoP, something to pick up once you've finished the "real" three, misreads what it's for.

In practice, the right time to take M_o_R has less to do with your position on the project-programme-portfolio ladder and more to do with how central risk conversations already are to your actual work. A project manager in a sector where risk is constantly live, construction, infrastructure, anything safety-critical, often benefits from M_o_R earlier than the theoretical ladder would suggest, sometimes straight after PRINCE2 Practitioner rather than after MSP. Someone in a lower-risk, steadier delivery environment might reasonably leave it later, or study it alongside MoP once they're thinking about risk at organisational scale rather than project scale.

There's a version of this article that would hand you a single definitive sequence and stop there, because that's the tidier answer. It wouldn't be honest. The organisations Omega works with don't send every PM through the same four qualifications in the same order, because their PMs aren't all heading to the same place.

What's genuinely worth taking from this isn't a sequence to follow. It's the underlying question the sequence is a proxy for: what does your role actually govern right now, a project, a programme, or a portfolio, and where does risk sit in relation to that. Answer that honestly and the order tends to answer itself. A project manager staying close to delivery gets more from PRINCE2 depth than from MSP theory they won't use for years. Someone already fielding programme-level escalation conversations is often better served bringing MSP forward, even ahead of finishing every PRINCE2 extension. The four qualifications aren't rungs on a fixed ladder. They're a set of lenses, and the one you need next is whichever one matches the scope of decision you're actually being asked to make.

That's a different question to sit with than "what comes after PRINCE2," and a more useful one. If you want to talk through where you actually are on that ladder and which of the four fits your next step, get in touch about your training options.

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.