A visual guide to complete pmbok 8 process reference: all 40 processes explained for the 2026 PMP Exam
PMP Cheat Sheet 2026: The Complete 40 Processes List
PMBOK 7 had zero processes. PMBOK 8 has 40 non-prescriptive processes organised across 5 Focus Areas. Planning carries ~20, Executing ~8, Monitoring & Controlling ~7, with Initiating and Closing holding ~2 each. "Non-prescriptive" means you tailor which apply — you don't skip them without justification. These processes are the practical how-to layer of the entire framework.
PMBOK 7 had zero processes. PMBOK 8 has 40. Here's your complete reference guide — organised by Focus Area, with exam relevance ratings so you know where to spend your study time.
Let me be direct about how to use this article. Don't read it trying to memorise every process name. Use it to understand the pattern — which Focus Area is heaviest (Planning), which processes are the backbone of the whole framework (Project Management Plan, Integrated Change Control, Close Project), and why the sequence makes logical sense. Pattern recognition is what the PMP exam actually tests.
PMP Exam 2026: What "Non-Prescriptive" Means
In PMBOK 6, you were expected to apply all 49 processes to every project. In PMBOK 8, the 40 processes come with a critical qualifier: non-prescriptive. You tailor which processes you apply based on project complexity, type, and organisational context.
What you cannot do is skip a process simply because it seems inconvenient. Skipping Identify Risks because your project "feels safe" is not tailoring — it's negligence. Tailoring means applying processes at the appropriate level of rigour and formality for your context. A small project might use a one-page risk log instead of a full risk breakdown structure. That's valid. Having no risk process at all is not.
Non-prescriptive does NOT mean optional. The exam will test this distinction. Scenarios that suggest skipping a governance or closing process because the project is "small" are trap answers. Governance (charter, change control) and Closing are never optional regardless of project size.
PMP July 2026: Initiating (~2 Processes)
Initiating formally authorises the project and identifies its stakeholders. It's compact by design — the project doesn't exist yet, so there's limited work to do. But these two processes carry enormous exam weight because everything downstream depends on getting them right.
| Process | Purpose | Key Output | Exam Weight |
|---|---|---|---|
| Develop Project Charter | Formally authorises the project; appoints the PM | Project Charter | ★★★★★ |
| Identify Stakeholders | Identifies all parties with an interest or impact on the project | Stakeholder Register | ★★★★★ |
PMP July 2026: Planning (~20 Processes)
Planning is the powerhouse of PMBOK 8. Half the processes live here — and for good reason. A well-planned project is a well-managed project. Every other Focus Area draws from planning outputs. The Project Management Plan is the single most referenced document in the entire framework.
| Process | Purpose | Key Output | Exam Weight |
|---|---|---|---|
| Develop Project Mgmt Plan | Integrates all subsidiary plans into the master reference | Project Management Plan | ★★★★★ |
| Plan Scope Management | Defines how scope will be defined, validated, and controlled | Scope Management Plan | ★★★ |
| Collect Requirements | Captures stakeholder needs, expectations, and constraints | Requirements Documentation | ★★★★ |
| Define Scope | Creates the detailed project scope statement | Project Scope Statement | ★★★★ |
| Create WBS | Decomposes deliverables into manageable components | Scope Baseline (WBS + Dictionary) | ★★★★★ |
| Plan Schedule Management | Defines schedule methodology and control thresholds | Schedule Management Plan | ★★★ |
| Define Activities | Identifies specific actions to produce deliverables | Activity List | ★★★ |
| Sequence Activities | Documents logical relationships between activities | Project Schedule Network Diagram | ★★★★ |
| Estimate Activity Durations | Estimates work periods for each activity | Duration Estimates | ★★★ |
| Develop Schedule | Creates the schedule model from all scheduling inputs | Schedule Baseline | ★★★★★ |
| Plan Cost Management | Defines cost estimation, budgeting, and control approach | Cost Management Plan | ★★★ |
| Estimate Costs | Develops cost approximations for completing activities | Cost Estimates | ★★★★ |
| Determine Budget | Aggregates cost estimates to establish cost baseline | Cost Baseline | ★★★★ |
| Plan Quality Management | Identifies quality requirements and how to achieve them | Quality Management Plan | ★★★★ |
| Plan Resource Management | Defines approach for acquiring, developing, managing resources | Resource Management Plan | ★★★ |
| Estimate Activity Resources | Estimates type and quantity of resources per activity | Resource Requirements | ★★★ |
| Plan Communications Mgmt | Defines stakeholder communication approach and cadence | Communications Management Plan | ★★★★ |
| Plan Risk Management | Defines risk management approach for the project | Risk Management Plan | ★★★★ |
| Identify Risks | Identifies individual and overall project risks | Risk Register | ★★★★★ |
| Plan Procurement Management | Documents procurement decisions and identifies potential sellers | Procurement Management Plan | ★★★ |
A visual guide to complete pmbok 8 process reference: all 40 processes explained for the 2026 PMP Exam
PMP July 2026: Executing (~8 Processes)
Executing is where the work actually happens — and where most of the budget gets spent. The PM's job here shifts from planning to enabling: removing blockers, managing quality, coordinating resources, and keeping stakeholders engaged. Direct and Manage Project Work is the hub that everything else feeds.
| Process | Purpose | Key Output | Exam Weight |
|---|---|---|---|
| Direct & Manage Project Work | Leads and performs the planned work; generates performance data | Work Performance Data, Deliverables | ★★★★★ |
| Manage Project Knowledge | Uses existing knowledge and creates new knowledge | Lessons Learned Register | ★★★ |
| Manage Quality | Translates quality management plan into executable activities | Quality Reports, Test Results | ★★★★ |
| Acquire Resources | Obtains team members, equipment, and materials | Physical Resource Assignments | ★★★ |
| Develop Team | Improves team competencies and interaction | Team Performance Assessments | ★★★★ |
| Manage Team | Tracks performance, resolves conflict, manages changes | Change Requests, Project Updates | ★★★★ |
| Manage Communications | Ensures timely creation and distribution of project information | Project Communications | ★★★★ |
| Conduct Procurements | Selects sellers and awards contracts | Selected Sellers, Agreements | ★★★ |
PMP July 2026: Monitoring & Controlling (~7 Processes)
M&C runs parallel to every other Focus Area — it never stops from project start to finish. This is the control layer: comparing actuals to plan, identifying variances, triggering change requests, and keeping the project on the right trajectory. Perform Integrated Change Control is the most governance-heavy process in the entire framework.
| Process | Purpose | Key Output | Exam Weight |
|---|---|---|---|
| Monitor & Control Project Work | Tracks overall project performance against the plan | Work Performance Reports | ★★★★★ |
| Perform Integrated Change Control | Reviews, approves, and manages changes to project documents | Approved Change Requests | ★★★★★ |
| Validate Scope | Formalises acceptance of completed deliverables | Accepted Deliverables | ★★★★ |
| Control Scope | Monitors scope and manages changes to the scope baseline | Change Requests, WPI | ★★★★ |
| Control Schedule | Monitors schedule status and manages changes | Schedule Forecasts, Change Requests | ★★★★ |
| Control Costs | Monitors project costs and manages changes to cost baseline | Cost Forecasts (EAC, ETC) | ★★★★ |
| Monitor Risks | Monitors risk status, identifies new risks, evaluates responses | Risk Register Updates, Change Requests | ★★★★ |
PMP July 2026: Closing (~2 Processes)
Closing is the most skipped Focus Area in real-world practice — and that's exactly why the exam loves to test it. Closing is non-negotiable in PMBOK 8. No matter how small the project, you close it formally. Lessons learned must be documented. Contracts must be closed. Stakeholders must formally accept the final deliverable.
| Process | Purpose | Key Output | Exam Weight |
|---|---|---|---|
| Close Project or Phase | Finalises all activities; transfers product; archives records | Final Product / Service / Result, Lessons Learned | ★★★★★ |
| Close Procurements | Completes and settles each project procurement | Closed Procurements, Procurement Documentation | ★★★ |
July 2026 PMP Exam: Most Critical PMBOK 8 Processes
Based on ECO 2026 domain weightings and the types of situational questions the exam consistently generates, these 10 processes carry disproportionate weight. Master these before drilling the full 40.
- 1Develop Project Charter — The formal start of everything. Questions about PM authority, sponsor role, and project authorisation trace here.
- 2Identify Stakeholders — Early stakeholder mapping is a recurring exam theme. Missing a stakeholder in Initiating always causes downstream problems.
- 3Develop Project Management Plan — The master reference. Almost every M&C process uses it as an input. Know its role as an integrated document, not just a schedule.
- 4Create WBS — The Scope Baseline (including WBS Dictionary) is the definitive scope reference. Scope disputes always resolve here.
- 5Develop Schedule — Critical path, schedule baseline, and float calculations are tested regularly. Know the difference between total and free float.
- 6Identify Risks — Risk identification is never a one-time event in PMBOK 8. Continuous risk identification throughout the project is explicitly tested.
- 7Direct & Manage Project Work — The executing hub. Work Performance Data flows from here into every monitoring process.
- 8Monitor & Control Project Work — Produces Work Performance Reports that go to stakeholders. Distinct from the raw data generated in execution.
- 9Perform Integrated Change Control — Every scope, schedule, or cost change must pass through the CCB. No exceptions. The exam tests this boundary repeatedly.
- 10Close Project or Phase — Formally completing the project — including lessons learned, stakeholder acceptance, and records archiving — is non-negotiable in PMBOK 8.
Map the 40 processes to a simple grid: rows = 5 Focus Areas, columns = 7 Performance Domains. Then trace which domain each process primarily serves. You'll see immediately that Planning processes are spread across all 7 domains, while Closing processes concentrate in Governance and Scope. This domain-process mapping is how the exam thinks — and how you should think when answering scenario questions.
PMP Exam 2026: How to Use This Reference
This is a reference article, not a reading-order article. Here's the study sequence I recommend to my students: start with the 10 exam-critical processes above, understand their inputs and outputs cold, then work outward to the adjacent processes in the same Focus Area. By the time you've covered the top 10 thoroughly, you'll find the remaining 30 are much easier to understand because you already know the framework they connect to.
The single most common mistake I see: candidates study processes in isolation. Integrated Change Control makes no sense unless you understand that changes originate in Executing, flow through M&C, and update Planning outputs. The processes are a network, not a list. Study the network.
Which PMBOK 8 process produced the document that serves as the authoritative reference for resolving this scope dispute?
Why C is correct
The Create WBS process (Planning Focus Area) produces the Scope Baseline — comprising the Project Scope Statement, Work Breakdown Structure, and WBS Dictionary. The WBS Dictionary is the most granular and authoritative scope reference in PMBOK 8. If a deliverable is described in the WBS Dictionary, it is in scope — full stop. This is the document that resolves scope disputes because it was formally approved at the planning baseline.
Why the others are wrong
A — The Project Charter provides high-level scope boundaries, not detailed deliverable definitions. It cannot resolve a specific deliverable dispute. B — Requirements documentation captures stakeholder needs but is an input to scope definition, not the authoritative baseline. D — Validate Scope is a Monitoring & Controlling process that confirms acceptance of completed deliverables — it doesn't produce the scope reference document.
📋 ECO 2026: Process (~50%) · Scope Domain · Planning Focus Area
