--- title: "Standards and methods: PMBOK 8, PRINCE2 7, ISO 21502 and…" description: "The map in one table Framework Type Current edition (check before relying on it) Best used for --- --- --- --- PMBOK Guide (PMI), with The Standard for…" url: https://optimizeall.com/learn/project-management-leadership-with-ai/standards-and-methods-landscape updated: 2026-10-05 --- Project Management Leadership with AI · Project governance, lifecycles and the business case · lesson 2 of 21 · 16 min # Standards and methods: PMBOK 8, PRINCE2 7, ISO 21502 and Scrum ## The map in one table | Framework | Type | Current edition (check before relying on it) | Best used for | |---|---|---|---| | **PMBOK Guide** (PMI), with The Standard for Project Management | Body of knowledge and standard | Eighth edition, released November 2025 | Comprehensive reference; principles, performance domains and process guidance; PMI credentials | | **PRINCE2** (PeopleCert/AXELOS) | Method | PRINCE2 7 (2023) | How to organise, govern and run a project: principles, practices, processes, people | | **ISO 21502** | International standard (guidance) | ISO 21502:2020 | Organisation-wide policy alignment; procurement and maturity references | | **APM Body of Knowledge** (Association for Project Management) | Body of knowledge | Check apm.org.uk for the current edition | UK-centred professional reference and APM qualifications | | **Scrum Guide** (Schwaber and Sutherland) | Framework definition | 2020 edition remains current | Empirical, iterative product development with small teams | Related ISO documents include ISO 21500 (context and concepts), ISO 21503 (programme management), ISO 21504 (portfolio management), ISO 21505 (governance), ISO 21508 (earned value management) and ISO 21511 (work breakdown structures). ## PMBOK Guide, eighth edition, at a glance - **Six principles:** adopt a holistic view; focus on value; embed quality; be an accountable leader; integrate sustainability; build an empowered culture. - **Seven performance domains:** governance, scope, schedule, finance, stakeholders, resources, risk. - **Five focus areas:** initiating, planning, executing, monitoring and controlling, closing, containing 40 non-prescriptive processes. It builds on the seventh edition's principles-based approach while restoring practical structure. PMI has also been updating its certification exams; check pmi.org for current exam content outlines rather than relying on third-party summaries. ## PRINCE2 7 at a glance - **Seven principles** (for example continued business justification, manage by exception, tailor to suit the project). - **Seven practices** (previously "themes"): business case, organising, plans, quality, risks, issues, progress. - **Seven processes** from starting up to closing a project. - A new emphasis on **people**, plus sustainability and digital and data management. ## Worked example: translating one need across frameworks | Need | PRINCE2 7 | PMBOK Guide 8 | Scrum | |---|---|---|---| | Decide whether to continue | Managing a stage boundary; board authorises next stage | Governance domain; phase-gate decisions | Sprint Review evidence informs release and funding decisions | | Control deviations | Tolerances and exception reports | Monitoring and controlling focus area | Sprint Goal, Product Goal and transparency of artefacts | | Define what "done" means | Product descriptions and quality criteria | Scope and quality (embed quality principle) | Definition of Done | ## Hands-on: a tailoring statement template ```text Project: ____ Sponsor: ____ Date/version: ____ CONTEXT Size and duration | Regulatory constraints | Where uncertainty sits | Team experience | Contract model CHOICES Governance (board, tolerances, gates) | Lifecycle per workstream | Controls (EVM, burnup, milestones) | Risk approach | Reporting rhythm and format | Standards referenced (e.g. ISO 21502-aligned policy) RATIONALE One sentence per choice: why it fits this context REVIEW Revisited at each stage boundary or release decision; changes logged ``` ## Prompt template: a glossary across frameworks (approved AI tool) ```text Create a two-column glossary for our project that maps these terms to plain-English definitions and notes which framework each comes from: tolerance, stage boundary, performance domain, product backlog, Definition of Done, exception report, increment, baseline. Cite the framework and edition for each. Mark any term whose meaning you are unsure of in the current edition as [VERIFY]. ``` Verify every definition against the official publication before circulating it. ## Second worked example: a blended approach at a Dubai insurer *Illustrative.* A regional insurer headquartered in Dubai, with teams in Karachi and London, runs a 12-month customer platform programme. Its PMO policy is aligned to ISO 21502, which the group's auditors recognise. Governance borrows from PRINCE2 7: a five-person board, tolerances (±5% cost, ±3 weeks on key milestones) and stage boundaries at funding points. The mobile and web app is built by Scrum teams following the Scrum Guide, each with a Product Goal and a Definition of Done. The legacy data migration is planned predictively with a detailed cut-over rehearsal schedule. Every quarter, the PMO reviews the programme against the PMBOK Guide's seven performance domains (governance, scope, schedule, finance, stakeholders, resources, risk) as a checklist, looking for gaps rather than compliance. When a new sponsor joined halfway through and asked "what methodology are we using?", the programme manager handed over the one-page tailoring statement; the conversation took ten minutes instead of a workshop. ## Common mistakes - **Rulebook thinking:** applying a framework mechanically, including parts that add cost without value in your context. Every major framework explicitly calls for tailoring. - **Outdated editions:** describing the PMBOK Guide as purely process-based, PRINCE2 as having "themes", or quoting old exam outlines. Check the publisher's site for the current edition before you rely on a summary. - **Vocabulary clashes:** mixing terms from several frameworks without a shared glossary, so "stage", "phase", "release" and "gate" mean different things to different people. - **Certification as capability:** assuming a certificate in one framework means someone can run a project well. Credentials show knowledge of a framework; judgement comes from practice and reflection. - **Standards as a shield:** using "the method says so" to avoid making a decision. Frameworks inform decisions; accountable people still make them. ## How to measure success - Every project has a one-page tailoring statement reviewed at each stage boundary. - The team uses one agreed glossary. - Policies and training materials cite current editions. ## Video lecture: Standards and methods: PMBOK 8, PRINCE2 7, ISO 21502 and Scrum Lecture coming soon · 9 chapters · about 8 minutes. Read the full transcript below. 1. Which framework should we use? 2. Why it matters 3. PMBOK Guide, eighth edition 4. PRINCE2 7 and ISO 21502 5. APM, Scrum and scaling frameworks 6. Worked example one: mapping a term across frameworks 7. Worked example two: a Dubai insurer's blended approach 8. Watch me do it: a one-page tailoring statement 9. Common mistakes, recap and try this now ## Lecture transcript ### 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. ### 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. ### 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. ### 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. ### 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. ### 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. ### 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. ### 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. ### 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. ## Key takeaways - The PMBOK Guide 8th edition (November 2025) combines six principles, seven performance domains and five focus areas with 40 processes. - PRINCE2 7 (2023) is a method: seven principles, seven practices, seven processes, with people at its centre. - ISO 21502:2020 gives international project management guidance often referenced in policies and procurement. - The Scrum Guide 2020 remains the definition of Scrum; check current editions before relying on any framework. - Frameworks do different jobs; a one-page tailoring statement explains your choices and why. ## Try it Write a one-page tailoring statement for a project you know: context, choices for governance, lifecycle, controls and reporting, and a one-sentence rationale for each. - [Previous: Project governance and decision rights](https://optimizeall.com/learn/project-management-leadership-with-ai/project-governance) - [Next: Choosing a delivery lifecycle: predictive, agile or hybrid](https://optimizeall.com/learn/project-management-leadership-with-ai/choosing-a-lifecycle) - [All lessons of Project Management Leadership with AI](https://optimizeall.com/learn/project-management-leadership-with-ai)