Standards and methods: PMBOK 8, PRINCE2 7, ISO 21502 and Scrum

0:00 Which framework should we use?

At some point, every project leader hears the question: are we a PMBOK shop or a PRINCE2 shop? Should we be doing Scrum? Do we need to comply with ISO? It sounds like a choice between rival religions. It isn't. These frameworks do different jobs, and most mature organisations blend them. In this lecture you'll get a clear, current map of the main standards and methods: the PMBOK Guide's eighth edition, PRINCE2's seventh edition, the international standard ISO 21502, the APM Body of Knowledge, and the Scrum Guide. You'll learn what each one is for, how they fit together, and how to tailor them to your project. By the end, you'll be able to explain your organisation's approach in two minutes, and justify it.

0:54 Why it matters

Why does this matter? First, shared language. When your organisation, your suppliers and your client use the same terms, such as baseline, tolerance, product backlog and stage gate, far less time is lost to misunderstanding. Second, credentials and careers. Many roles ask for certification against one or more of these frameworks, and knowing the current editions matters. And third, and most important, tailoring. No framework should be applied mechanically. Each one says so explicitly. Your job as a project leader is to understand the building blocks well enough to select and adapt them for your context, and to explain why.

1:37 PMBOK Guide, eighth edition

Let's start with PMI's PMBOK Guide. The eighth edition was released in November twenty twenty-five, together with The Standard for Project Management. The seventh edition had moved to a principles-based approach. The eighth keeps that foundation but simplifies it and brings back more practical structure. It has six principles: adopt a holistic view, focus on value, embed quality, be an accountable leader, integrate sustainability, and build an empowered culture. It has seven performance domains: governance, scope, schedule, finance, stakeholders, resources and risk. And it reintroduces five focus areas that anyone who studied earlier editions will recognise, initiating, planning, executing, monitoring and controlling, and closing, containing forty non-prescriptive processes. Think of it as a comprehensive body of knowledge: a reference, not a step-by-step method.

2:30 PRINCE2 7 and ISO 21502

PRINCE2 is a method: it tells you how to organise and run a project. The seventh edition, released by PeopleCert in twenty twenty-three, keeps seven principles and seven processes, renames the former themes as practices, business case, organising, plans, quality, risks, issues and progress, and adds a strong emphasis on people, alongside sustainability and digital and data management. Tolerances and management by exception, which we covered in the governance lecture, come straight from PRINCE2. Then ISO 21502, published in twenty twenty, gives internationally agreed guidance on project management that any organisation can use for any type of project. It sits in a family: ISO 21500 for context and concepts, standards for programme and portfolio management and for governance, and ISO 21508 for earned value. ISO is often what procurement and maturity assessments reference.

3:28 APM, Scrum and scaling frameworks

Three more you'll meet often. The APM Body of Knowledge, from the Association for Project Management, the UK's chartered professional body, is another comprehensive reference, widely used in the UK and beyond. The Scrum Guide, by Ken Schwaber and Jeff Sutherland, defines Scrum; its current version is still the twenty twenty edition, which is deliberately short. Kanban practices, flow metrics and scaled agile frameworks such as SAFe add further options for flow-based and multi-team work. These evolve, so a simple rule: before you rely on any framework in a contract, a policy or an exam, check which edition is current. And be careful with what you read online, because many summaries still describe older editions.

4:18 Worked example one: mapping a term across frameworks

Let's make this concrete with a simple example. Every project needs an evidence-based decision to continue, or not. In PRINCE2, that's managing a stage boundary: the project board reviews the stage report and the updated business case and authorises the next stage. In the PMBOK Guide's eighth edition, it sits in the governance domain, as phase-gate decisions and oversight. In Scrum, there's no formal gate, but the Sprint Review inspects a working increment with stakeholders every sprint, and that evidence informs release and funding decisions made by the organisation. Three vocabularies. One underlying need. Once you see frameworks this way, as different names for recurring needs, you stop arguing about labels and start designing the governance your project actually requires.

5:10 Worked example two: a Dubai insurer's blended approach

Now a realistic scenario, illustrative. A regional insurer headquartered in Dubai, with teams in Karachi and London, runs a twelve-month programme to build a unified customer platform. Its PMO policy is aligned to ISO 21502, which the group's auditors recognise. Governance borrows from PRINCE2: a small board, tolerances and stage boundaries at funding points. The mobile and web app is built by Scrum teams following the Scrum Guide. The data migration from legacy systems is planned predictively, with a detailed cut-over plan. And the PMO uses the PMBOK Guide's seven performance domains as a quarterly review checklist: governance, scope, schedule, finance, stakeholders, resources and risk. Is this cheating? Not at all. It's tailoring, and every one of these frameworks explicitly encourages it.

6:03 Watch me do it: a one-page tailoring statement

Let me show you the one-page tailoring statement I write at the start of every project. First, context: size, duration, risk level, regulatory constraints and where the uncertainty sits. Second, choices: the governance model, the lifecycle for each workstream, the control mechanisms such as tolerances or burnups, and the reporting rhythm. Third, and this is the column most people skip, rationale: why each choice fits this context. For example: Scrum for the app, because requirements will emerge and users are available for feedback; a predictive plan for migration, because cut-over has hard dependencies and little room for experimentation. Finally, a footer: this statement is reviewed at every stage boundary. When an auditor, a new sponsor or a supplier asks 'what methodology do you use?', you hand them this page.

6:59 Common mistakes, recap and try this now

The common mistakes: treating any framework as a rulebook to follow mechanically; quoting outdated editions, such as describing PMBOK as purely process-based or PRINCE2 as having themes; and mixing vocabularies from several frameworks without a shared glossary, so people talk past each other. So, to recap. The PMBOK Guide's eighth edition, from November twenty twenty-five, combines six principles, seven performance domains and five focus areas with forty processes. PRINCE2 7 gives you a method built on principles, practices and processes, with people at its centre. ISO 21502 provides international guidance that policies and procurement often reference. The APM Body of Knowledge and the Scrum Guide complete the map. Your try-this-now: write a one-page tailoring statement for a project you know, with context, choices and a rationale for each.