Copyright (C) PrepPilot™, LLC. All rights reserved.
TL;DR: The PMBOK® 8th Edition has 40 non-prescriptive processes distributed across 7 performance domains (Governance, Scope, Schedule, Finance, Stakeholders, Resources, Risk) and mapped to 5 Focus Areas (Initiating, Planning, Executing, Monitoring and Controlling, Closing). Governance is the largest domain with 9 processes spanning all 5 Focus Areas. Planning has the most processes overall (20). Most domains follow a Plan-Do-Monitor pattern. The 7 performance domains do not map 1-to-1 to the 3 ECO domains: PMBOK® describes how work is structured, while the 2026 ECO (8 People tasks, 10 Process, 8 Business Environment) describes what the exam tests. Study by domain, not by memorizing a flat list.
The PMBOK® Guide 8th Edition reintroduces processes after the 7th edition removed them entirely. The result is 40 nonprescriptive processes distributed across 7 performance domains and mapped to 5 Focus Areas.
This is the single biggest structural change in the 8th edition. For PMP® candidates targeting the exam after July 9, 2026, understanding this structure is essential. You do not need to memorize every process. You need to understand which domain each process belongs to, what Focus Area it maps to, and why it matters.
Why Did Processes Return in the 8th Edition?
The 7th edition removed all 49 processes from the 6th edition and replaced them with 12 principles and 8 performance domains. The intention was to shift from a prescriptive process checklist to a principle-based guide that worked across predictive, agile, and hybrid approaches.
Practitioners pushed back. While the principles were valuable, the absence of processes left a practical gap. New project managers had no reference for what project managers actually do day to day. Experienced project managers lost a common vocabulary for describing specific activities.
The 8th edition resolves this by bringing back processes while keeping the principle-based foundation. The 40 processes describe common project management activities without mandating a specific order, set of inputs, or rigid methodology. They are "nonprescriptive," meaning they describe what teams commonly do rather than what they must do.
How Do 8th Edition Processes Differ from the 6th Edition?
If you studied the 6th edition's 49 processes, the 8th edition will feel familiar but not identical.
| Aspect | 6th Edition (49 Processes) | 8th Edition (40 Processes) |
|---|---|---|
| Organization | 10 Knowledge Areas x 5 Process Groups | 7 Performance Domains x 5 Focus Areas |
| Approach | Prescriptive with fixed ITTOs | Nonprescriptive with flexible ITTOs |
| Methodology | Primarily predictive | Supports predictive, adaptive, and hybrid |
| Tailoring | Limited guidance | Explicit tailoring considerations per domain |
| Principles | None | 6 principles provide decision-making framework |
The key difference is flexibility. The 6th edition implied a specific sequence: initiation flows into planning, planning flows into execution. The 8th edition treats Focus Areas as overlapping activities that occur throughout the project, with the mix depending on your development approach.
What Are the 7 Performance Domains?
Performance domains are the broad areas of focus for effective project management. Each domain contains a set of related processes.
| Performance Domain | Processes | Description |
|---|---|---|
| Governance | 9 | Framework, oversight, and integration of project management activities |
| Scope | 6 | Defining and managing what the project includes |
| Schedule | 3 | Planning and controlling the timeline |
| Finance | 4 | Managing budgets, costs, and financial reporting |
| Stakeholders | 7 | Engaging stakeholders and managing communications |
| Resources | 5 | Planning, acquiring, and leading team and physical resources |
| Risk | 6 | Identifying, analyzing, and responding to uncertainty |
| Total | 40 |
Governance has the most processes because it includes cross-cutting activities like project initiation, integrated planning, execution management, quality assurance, knowledge management, change control, and project closure.
What Are the 5 Focus Areas?
The 5 Focus Areas replace the Process Groups from the 6th edition. The concepts are the same, but the name change reflects a broader scope. Focus Areas include informal practices and flexible policies, not just formal processes.
- Initiating - Starting the project or phase
- Planning - Establishing the approach and plans
- Executing - Performing the work
- Monitoring and Controlling - Tracking progress and managing changes
- Closing - Completing the project or phase
In predictive approaches, Focus Areas tend to follow a more sequential pattern with overlap. In adaptive approaches, Initiating and Closing occur at the project level, while Planning, Executing, and Monitoring and Controlling repeat within each iteration.
What Are All 40 Processes by Domain?
Governance Domain (9 Processes)
Governance provides the framework and integrative processes that coordinate all other domains. It is the most process-heavy domain because it spans the full project life cycle.
| # | Process | Focus Area | Purpose |
|---|---|---|---|
| 1 | Initiate Project or Phase | Initiating | Formally authorize the project, define initial scope, resources, and stakeholders |
| 2 | Integrate and Align Project Plans | Planning | Combine all subsidiary plans into the project management plan |
| 3 | Plan Sourcing Strategy | Planning | Determine the sourcing approach, including make-or-buy decisions |
| 4 | Manage Project Execution | Executing | Lead and perform the work defined in the project management plan |
| 5 | Manage Quality Assurance | Executing | Audit quality requirements and facilitate quality process improvement |
| 6 | Manage Project Knowledge | Executing | Utilize existing knowledge and create new knowledge for the project and organization |
| 7 | Monitor and Control Project Performance | Monitoring and Controlling | Track, review, and report overall project progress |
| 8 | Assess and Implement Changes | Monitoring and Controlling | Manage project changes through review, approval, and implementation |
| 9 | Close Project or Phase | Closing | Finalize all activities and formally complete the project or phase |
Key concepts: Governance can range from structured (formal oversight bodies, steering committees) to self-governing (team manages all aspects, common in agile contexts). Effective governance requires three components: target metrics aligned with strategic goals, clear signaling mechanisms, and defined decision-making authority.
Scope Domain (6 Processes)
Scope management ensures the project includes all the work required, and only the work required, to deliver value.
| # | Process | Focus Area | Purpose |
|---|---|---|---|
| 1 | Plan Scope Management | Planning | Define how scope will be defined, developed, monitored, controlled, and validated |
| 2 | Elicit and Analyze Requirements | Planning | Determine, document, and manage stakeholder needs and requirements |
| 3 | Define Scope | Planning | Develop a detailed description of the project and product |
| 4 | Develop Scope Structure | Planning | Subdivide deliverables and work into manageable components (WBS) |
| 5 | Monitor and Control Scope | Monitoring and Controlling | Monitor scope status and manage changes to the scope baseline |
| 6 | Validate Scope | Monitoring and Controlling | Formalize acceptance of completed deliverables |
Key concepts: Product scope (features and functions) vs. project scope (the work to deliver them). The scope baseline includes the scope statement, WBS, and WBS dictionary. In adaptive approaches, the product backlog and user stories replace the traditional WBS.
Schedule Domain (3 Processes)
Schedule management covers timely project completion through planning, developing, and controlling the project timeline.
| # | Process | Focus Area | Purpose |
|---|---|---|---|
| 1 | Plan Schedule Management | Planning | Establish policies and procedures for managing the schedule |
| 2 | Develop Schedule | Planning | Analyze sequences, durations, resource requirements, and constraints to create the schedule |
| 3 | Monitor and Control Schedule | Monitoring and Controlling | Monitor schedule status and manage changes to the schedule baseline |
Key concepts: Critical path method (CPM) identifies the longest path through the project network. Schedule compression techniques include crashing (adding resources) and fast-tracking (parallel activities). In adaptive approaches, iteration planning, velocity tracking, and burndown charts replace traditional schedule management.
Finance Domain (4 Processes)
Finance management addresses the planning, estimating, budgeting, and controlling of costs to optimize value.
| # | Process | Focus Area | Purpose |
|---|---|---|---|
| 1 | Plan Financial Management | Planning | Define how revenues and expenses will be estimated, budgeted, managed, and controlled |
| 2 | Estimate Costs | Planning | Develop approximations of costs for resources needed |
| 3 | Develop Budget | Planning | Aggregate estimated costs to establish the cost baseline |
| 4 | Monitor and Control Finances | Monitoring and Controlling | Oversee financial health by tracking expenditures and adjusting baselines |
Key concepts: Cost baseline is the approved time-phased project budget. Contingency reserves address known risks (known-unknowns). Management reserves address unforeseen work (unknown-unknowns). Earned value management (EVM) tracks cost performance through metrics like CPI, SPI, and EAC. CapEx (capital expenditures) vs. OpEx (operational expenditures) classification affects financial reporting.
Stakeholders Domain (7 Processes)
Stakeholder management covers identification, engagement planning, communication, and ongoing monitoring of stakeholder relationships.
| # | Process | Focus Area | Purpose |
|---|---|---|---|
| 1 | Identify Stakeholders | Planning | Identify all people or organizations impacted by the project |
| 2 | Plan Stakeholder Engagement | Planning | Develop approaches to involve stakeholders based on needs and impact |
| 3 | Plan Communications Management | Planning | Develop an approach and plan for project communications |
| 4 | Manage Stakeholder Engagement | Executing | Communicate and work with stakeholders to meet needs and foster engagement |
| 5 | Manage Communications | Executing | Ensure timely collection, creation, distribution, and management of project information |
| 6 | Monitor Stakeholder Engagement | Monitoring and Controlling | Monitor relationships and tailor engagement strategies |
| 7 | Monitor Communications | Monitoring and Controlling | Monitor communications to ensure information needs are met |
Key concepts: The stakeholder engagement assessment matrix compares current and desired engagement levels (Unaware, Resistant, Neutral, Supportive, Leading). The power/interest grid classifies stakeholders by authority and concern. Communications can be interactive, push, or pull. Cultural considerations are critical for projects with diverse stakeholder groups.
Resources Domain (5 Processes)
Resource management covers both human resources (the project team) and physical/virtual resources (equipment, materials, facilities, infrastructure).
| # | Process | Focus Area | Purpose |
|---|---|---|---|
| 1 | Plan Resource Management | Planning | Define how to estimate, acquire, manage, and utilize resources |
| 2 | Estimate Resources | Planning | Estimate team resources, materials, equipment, and supplies needed |
| 3 | Acquire Resources | Executing | Obtain team members, facilities, equipment, and other resources |
| 4 | Lead the Team | Executing | Improve competencies, interaction, and team environment to enhance performance |
| 5 | Monitor and Control Resourcing | Monitoring and Controlling | Ensure assigned resources are available as planned and adjust for changes |
Key concepts: Team development follows the Tuckman model (Forming, Storming, Norming, Performing, Adjourning). Conflict management approaches range from withdraw/avoid to collaborate/problem solve, with collaboration generally preferred. Emotional intelligence (self-awareness, self-management, social awareness, relationship management) is a key leadership competency. Motivation theories (Maslow, Herzberg, McGregor, McClelland) inform how project managers lead effectively.
Risk Domain (6 Processes)
Risk management addresses both threats (negative risks) and opportunities (positive risks), at both individual and overall project levels.
| # | Process | Focus Area | Purpose |
|---|---|---|---|
| 1 | Plan Risk Management | Planning | Define how risk management activities will be conducted |
| 2 | Identify Risks | Planning | Determine which risks may affect the project and document characteristics |
| 3 | Perform Risk Analysis | Planning | Prioritize risks by assessing probability and impact (qualitative and quantitative) |
| 4 | Plan Risk Responses | Planning | Develop strategies and actions to address risks |
| 5 | Implement Risk Responses | Executing | Execute agreed-upon risk response plans |
| 6 | Monitor Risks | Monitoring and Controlling | Monitor response implementation, track risks, identify new risks |
Key concepts: Threat response strategies are Escalate, Avoid, Transfer, Mitigate, Accept. Opportunity response strategies are Escalate, Exploit, Share, Enhance, Accept. Risk appetite is the degree of uncertainty an entity is willing to accept. Risk tolerance is the degree of risk it can withstand. The risk breakdown structure (RBS) organizes risks by category (technical, management, commercial, external).
How Do Focus Areas Map to Performance Domains?
This matrix shows which processes belong to each Focus Area within each domain. It is the 8th edition equivalent of the classic Process Group/Knowledge Area grid from the 6th edition.
| Domain | Initiating | Planning | Executing | M&C | Closing |
|---|---|---|---|---|---|
| Governance | 1 | 2 | 3 | 2 | 1 |
| Scope | - | 4 | - | 2 | - |
| Schedule | - | 2 | - | 1 | - |
| Finance | - | 3 | - | 1 | - |
| Stakeholders | - | 3 | 2 | 2 | - |
| Resources | - | 2 | 2 | 1 | - |
| Risk | - | 4 | 1 | 1 | - |
| Total | 1 | 20 | 8 | 10 | 1 |
Planning has the most processes (20), reflecting the depth of upfront and iterative planning required. Initiating and Closing each have 1 process, both in Governance, which makes sense since project authorization and closure are governance-level activities.
How Performance Domains Map to 2026 ECO Tasks
The PMBOK® 8th Edition's 7 performance domains describe how project management work is structured. The 2026 ECO's 3 domains (with 26 total tasks: 8 People, 10 Process, 8 Business Environment) describe what PMI tests. They are not the same lens. Use the crosswalk below to figure out where each performance domain shows up on the exam.
| Performance Domain | Primary ECO Domain | Representative ECO Tasks |
|---|---|---|
| Governance | Business Environment | Task 1 (Define and establish project governance), Task 3 (Manage and control changes), Task 6 (Continuous improvement) |
| Scope | Process | Task 1 (Develop integrated plan), Task 2 (Develop and manage scope), Task 3 (Value-based delivery) |
| Schedule | Process | Task 1 (Integrated plan), Task 8 (Plan and manage schedule), Task 9 (Evaluate project status) |
| Finance | Process | Task 1 (Integrated plan), Task 6 (Plan and manage finance), Task 9 (Evaluate project status) |
| Stakeholders | People | Task 1 (Common vision), Task 4 (Engage stakeholders), Task 5 (Align expectations), Task 6 (Manage expectations), Task 8 (Plan and manage communication) |
| Resources | Process and People | Process Task 4 (Plan and manage resources), Process Task 5 (Procurement); People Task 3 (Lead the project team) |
| Risk | Business Environment | Task 5 (Plan and manage risk), Task 4 (Remove impediments and manage issues), Task 8 (External business environment changes) |
A few patterns worth noting. Governance is the workhorse of Business Environment on the exam, since governance, change control, and continuous improvement all live there. Risk has moved entirely under Business Environment, even though its 6 processes still feel like Process-domain work in practice. Stakeholders is the biggest People-domain footprint, since five of the eight People tasks touch stakeholder engagement, alignment, or communication.
When you see an exam question, ask yourself two questions in sequence. First, which performance domain is this activity in (Scope? Risk? Governance?). Second, which ECO task does PMI file it under. The first guides the project management approach. The second guides the answer pattern PMI expects.
How Should You Study the 40 Processes?
Do not memorize all 40 processes as a list. Instead, use these strategies.
1. Learn by Domain, Not by Number
Study each domain as a coherent unit. Governance is about oversight and integration. Scope is about defining what to build. Schedule is about when. Finance is about how much. Stakeholders is about who. Resources is about who does the work and with what. Risk is about what could go wrong or go right.
2. Understand the Pattern
Most domains follow the same pattern: Plan it, Do it, Monitor it. The Planning Focus Area has a "Plan [domain] Management" process. The Executing Focus Area has a "Manage [domain]" process. The Monitoring and Controlling Focus Area has a "Monitor and Control [domain]" process. Once you see this pattern, the structure becomes predictable.
3. Focus on the Governance Domain
Governance has 9 of the 40 processes and spans all 5 Focus Areas. It is the integrative domain that ties everything together. Understanding Governance processes well gives you a framework for understanding how all other domains connect.
4. Know the Differences Between Similar Processes
Several processes sound similar but serve different purposes:
- Manage Quality Assurance (Governance) focuses on improving quality processes. Validate Scope (Scope) focuses on formal acceptance of deliverables.
- Monitor and Control Project Performance (Governance) tracks overall project progress. Monitor and Control Scope/Schedule/Finances track specific baselines.
- Manage Stakeholder Engagement focuses on working with stakeholders. Manage Communications focuses on information distribution.
5. Connect Processes to Real Work
For each process, think about what it looks like in a real project. "Estimate Costs" is what you do when building a project budget. "Identify Risks" is what happens in a risk workshop. "Lead the Team" is what you do every day as a project manager. The processes describe activities you already know if you have project management experience.
What Are the Key Takeaways?
- The 8th edition has 40 nonprescriptive processes across 7 performance domains, mapped to 5 Focus Areas
- Governance is the largest domain (9 processes) and the only one that spans all 5 Focus Areas
- The processes are not a rigid sequence. They describe common activities that can be adapted to predictive, agile, or hybrid approaches
- Planning has the most processes (20), reflecting the depth of planning work in any project approach
- Study by domain rather than memorizing a flat list. Learn the Plan-Do-Monitor pattern that most domains follow
- The 6 principles provide the decision-making framework for applying these processes
- The 8th Edition also weaves AI into project management processes across several domains, particularly in risk analysis, resource optimization, and schedule development
- For exam preparation, focus on understanding when and why to use each process, not on memorizing ITTOs
For details on how these processes connect to the 2026 ECO domains, see our ECO guide. For an in-depth look at the domain that changed the most, see our Business Environment domain guide. For a roundup of every 2026 exam change beyond processes, see our PMP® exam changes 2026 guide.
Start practicing with PrepPilot™ and test your knowledge of the PMBOK® 8th Edition performance domains and processes. Questions are calibrated by real user data, so difficulty scores reflect actual candidate performance, not guesswork.