The release of the PMBOK Guide — Eighth Edition marks the most significant restructuring of project management’s flagship standard in over a decade. If you studied for a previous PMP exam using the familiar Knowledge Areas and Process Groups grid, much of what you knew has been reorganized, renamed, and in some cases consolidated. This guide walks through exactly what changed, what the new structure looks like, and how to use it as the foundation for your PMP exam preparation.
If you are preparing for the PMP exam, knowing which process belongs to which Performance Domain is one of the most tested — and most confused — areas. You can practice here at PMBOK 8th Edition Process Chart Game
Why the 8th Edition Is Different
Previous editions of the PMBOK Guide organized project management around ten Knowledge Areas (Integration, Scope, Schedule, Cost, Quality, Resources, Communications, Risk, Procurement, and Stakeholder Management) mapped against five Process Groups (Initiating, Planning, Executing, Monitoring & Controlling, and Closing). This produced a 10×5 grid of 49 processes that became the backbone of PMP study for years.
The 8th Edition moves away from that grid entirely. The ten Knowledge Areas have been replaced by seven Performance Domains. The five Process Groups have been reimagined as five Focus Areas. The process count has been reduced from 49 to 40, with several processes consolidated, renamed, or absorbed into broader activities. The result is a framework that is deliberately more adaptable — designed to work across predictive, agile, and hybrid project environments rather than being optimised primarily for waterfall delivery.
The Six Project Management Principles
Before the Performance Domains, the 8th Edition establishes six principles that underpin all project management practice. These are not prescriptive rules — they are guiding values that shape how a project manager approaches every decision.
Adopt a Holistic View means understanding that projects operate within wider systems — organisational, environmental, and human — and that decisions made in one area ripple into others. A change to the schedule is never just a schedule change; it touches resources, finances, stakeholder expectations, and risk.
Focus on Value shifts the measure of project success away from delivery of outputs and towards realisation of outcomes and benefits. Delivering a project on time and on budget is not success if the result creates no value for the organisation or its customers.
Embed Quality Into Processes and Deliverables treats quality as something built in from the start rather than inspected at the end. It applies equally to the way the team works and to what the team produces.
Be an Accountable Leader places responsibility on the project manager not just to manage tasks but to demonstrate ethical behaviour, take ownership of decisions, and serve the project team as much as they direct it.
Integrate Sustainability Within All Project Areas is new to this edition and reflects a maturation in the profession’s understanding of its responsibilities. Projects have environmental, social, and long-term organisational consequences that deserve deliberate consideration throughout the project lifecycle.
Build an Empowered Culture recognises that the best project outcomes come from teams that are trusted, supported, and given the autonomy to make decisions within their area of expertise. Culture is not a soft topic — it directly determines whether a project team performs.
Read the full in depth pmbok guide here -> PMBOK Guide 8th Edition: The Complete Practitioner’s Guide
The Seven Performance Domains
Performance Domains replace the old Knowledge Areas as the primary organising structure of the PMBOK® Guide. Each domain represents a grouping of related activities and concerns that, together, drive project success. They are not sequential phases — they operate in parallel throughout the project, with varying degrees of emphasis at different points.
Governance Performance Domain
Governance is the broadest of the seven domains, covering the structures, decisions, and processes that direct and oversee the project from initiation to closure. It includes establishing how the project will be authorised, how plans will be integrated, how execution will be managed, how quality will be assured, how knowledge will be captured, how performance will be monitored, how changes will be handled, and how the project will be formally closed.
This domain contains nine processes: Initiate Project or Phase, Integrate and Align Project Plans, Plan Sourcing Strategy, Manage Project Execution, Manage Quality Assurance, Manage Project Knowledge, Monitor and Control Project Performance, Assess and Implement Changes, and Close Project or Phase.
With nine processes, Governance is the largest domain and reflects its role as the connective tissue of the entire project management framework.
Scope Performance Domain
Scope management is about defining and controlling what the project will and will not deliver. The 8th Edition retains the core logic of scope management but streamlines it into six processes: Plan Scope Management, Elicit and Analyze Requirements, Define Scope, Develop Scope Structure, Monitor and Control Scope, and Validate Scope.
The language shift from “Collect Requirements” to “Elicit and Analyze Requirements” is deliberate — requirements don’t simply exist to be gathered; they need to be drawn out and examined critically. Similarly, “Develop Scope Structure” replaces the old “Create WBS” to acknowledge that not every project organises its scope through a traditional Work Breakdown Structure.
Schedule Performance Domain
The Schedule domain is the most streamlined in the framework, covering just three processes: Plan Schedule Management, Develop Schedule, and Monitor and Control Schedule. Previous editions contained more granular processes for defining activities, sequencing them, and estimating durations as separate steps. In the 8th Edition, these activities are embedded within Develop Schedule rather than treated as independent processes.
This consolidation reflects a practical reality: in most project environments, the act of scheduling involves all of these sub-activities in an iterative, often simultaneous way rather than as discrete sequential steps.
Finance Performance Domain
Finance covers the identification, planning, estimation, and control of project costs. Its four processes are Plan Financial Management, Estimate Costs, Develop Budget, and Monitor and Control Finances.
The rename from “Cost Management” to “Finance” signals a broader scope — this domain is not just about tracking expenditure but about understanding the project’s financial context, funding arrangements, and the relationship between project spend and the value being created. “Monitor and Control Finances” replaces the previous “Control Costs” for the same reason.
Stakeholders Performance Domain
With seven processes, Stakeholders is the second largest domain. It covers the full lifecycle of stakeholder engagement: Identify Stakeholders, Plan Stakeholder Engagement, Plan Communications Management, Manage Stakeholder Engagement, Manage Communications, Monitor Stakeholder Engagement, and Monitor Communications.
Previous editions split stakeholder management and communications management across two Knowledge Areas. The 8th Edition brings them together under one domain, recognising that communication and engagement are two aspects of the same fundamental activity — maintaining the relationships and information flows that keep a project aligned with the needs and expectations of its people.
Resources Performance Domain
Resources covers the planning, acquisition, and management of the people and physical assets that execute the project. Its five processes are Plan Resource Management, Estimate Resources, Acquire Resources, Lead the Team, and Monitor and Control Resourcing.
“Lead the Team” is a significant addition and marks a shift in emphasis from managing resources as assets towards developing and leading people as the project’s most important capability. This aligns with the principle of building an empowered culture — resources aren’t just things to be acquired and tracked; they are professionals to be led.
Risk Performance Domain
Risk management follows a logical six-step sequence: Plan Risk Management, Identify Risks, Perform Risk Analysis, Plan Risk Responses, Implement Risk Responses, and Monitor Risks.
The consolidation of qualitative and quantitative risk analysis into a single process — Perform Risk Analysis — is the most notable change from previous editions. Rather than mandating two separate analytical steps, the 8th Edition leaves the depth and type of analysis to the project team’s judgement, consistent with the guide’s broader emphasis on tailoring.
The Five Focus Areas
The five Focus Areas — Initiating, Planning, Executing, Monitoring and Controlling, and Closing — will be immediately familiar to anyone who studied under a previous edition. They are the Process Groups, renamed and repositioned.
The reframing matters. In previous editions, Process Groups implied a structured sequence that every project should follow. Focus Areas carry the same underlying logic but without the prescriptive sequencing — they describe areas of activity that exist throughout the project lifecycle rather than phases to be entered and exited in order. Processes from every domain map across multiple Focus Areas, and Focus Areas themselves overlap significantly in practice.
How the Domains, Principles, and Focus Areas Connect
The relationship between these three layers is what gives the 8th Edition its coherence. The six principles provide the values that guide how practitioners think and behave. The seven Performance Domains describe what activities need to be happening across a project. The 40 processes within those domains provide the specific, actionable steps that translate principles and domain knowledge into real project work. The five Focus Areas provide a way of understanding when and in what context those processes are most active.
No single layer works in isolation. A project manager who knows all 40 processes but has not internalised the principles will execute correctly but without judgment. One who understands the principles but cannot navigate the processes will have good intentions without practical traction.
Preparing for the PMP Exam With the 8th Edition
The PMP exam tests your ability to apply this framework in context, not to recall it in isolation. Multiple-choice questions will present scenarios where you need to identify the right process, the right domain lens, or the right principle — and the distractors will frequently be processes or concepts that are adjacent to the correct answer but belong somewhere else in the framework.
The most reliable study approach combines three things: understanding the logic behind the framework (why each domain exists and how it connects to the others), memorising the structure (which processes sit in which domain), and practising application (working through scenario questions that require you to navigate the framework under pressure).
The PMBOK® 8th Edition Process Chart Game on ProjInsights is designed specifically for the second of those three. Drilling the 40 processes into their correct domains through active, repeated recall builds the structural knowledge that underpins both the understanding and the application layers. Use it alongside your primary study materials and scenario practice, and you will find that the framework stops feeling like something to be memorized and starts feeling like something you actually know.
Visit us at projinsights.com for more resources, templates, and articles.