A visual guide to pmbok 8 focus areas: replacing traditional process groups for the 2026 PMP Exam
PMBOK 8 Focus Areas in 60 Words
PMBOK 8 introduces 5 Focus Areas — Initiating, Planning, Executing, Monitoring & Controlling, and Closing — which are the functional return of the classic Process Groups that PMBOK 7 removed. They house all 40 non-prescriptive processes and apply to predictive, agile, and hybrid projects. The key upgrade: Focus Areas are explicitly designed to overlap and run concurrently, not sequentially.
PMP July 2026: Why Process Groups are back as Focus Areas
They called it a bold move. PMI called it feedback-driven evolution. Either way, removing Process Groups from PMBOK 7 was one of the most controversial decisions in the guide's history.
The original intent was sound: Process Groups had become rigid boxes that encouraged candidates to think about project management as a linear, checklist-driven activity. PMI wanted PMs to think in principles and outcomes, not phases. So in 2021, PMBOK 7 stripped the groups out entirely — 49 processes, gone. 5 Process Groups, gone.
What happened next was predictable to anyone who's trained exam candidates. Students panicked. Without a structural framework to hang the content on, studying for the PMP became significantly harder. Practitioners pushed back because the groups provided a practical language for organizing work. Training organizations complained they had nothing concrete to build curriculum around.
PMI listened. PMBOK 8 brings the structure back — just with a smarter name and a more flexible framing.
When I first read the PMBOK 8 draft, I was genuinely relieved. I've coached over 3,000 PMP candidates, and the most common struggle with PMBOK 7 was the absence of a process scaffold. Process Groups weren't perfect, but they gave candidates a mental map. Focus Areas restore that map — and the new framing is actually more honest about how projects behave.
PMP Exam 2026: Difference Between Focus Areas & Process Groups
Let me be direct about this: for exam purposes, Focus Areas and Process Groups are functionally the same. The five areas are identical. The processes that sit inside them are organized the same way. If you studied PMBOK 6 Process Groups, you already know the skeleton of PMBOK 8 Focus Areas.
The difference is in the framing — and the framing matters for how you answer scenario questions. Process Groups implied a sequence: you Initiate, then Plan, then Execute, then Monitor, then Close. Focus Areas acknowledge that in real projects — and especially in agile or hybrid environments — these activities overlap, iterate, and run simultaneously.
| Dimension | PMBOK 6 Process Groups | PMBOK 8 Focus Areas |
|---|---|---|
| Names | Identical (same 5 names) | Identical (same 5 names) |
| Flow | Implied sequential | Explicitly concurrent / overlapping |
| Processes housed | 49 prescriptive processes | 40 non-prescriptive processes |
| Agile applicability | Awkward fit | Explicitly addressed |
| Tailoring guidance | Limited | Built-in — processes are context-dependent |
The PMP exam from July 9, 2026 will use the term "Focus Areas" — not Process Groups. If a question references "the Planning Focus Area," understand it means the same conceptual space as the old Planning Process Group, but with 40 non-prescriptive processes instead of 24 prescriptive ones. The concurrency framing also matters: don't assume activities are sequential unless the scenario explicitly signals a waterfall context.
PMP July 2026: The 5 Core Focus Areas Explained
Here's every Focus Area — what it does, what it houses, and what the exam expects you to know about it.
Initiating
Initiating is where formal project existence begins. The two core processes here are Develop Project Charter and Identify Stakeholders. The Charter authorizes the project and grants the PM authority to act. Stakeholder identification is deliberately co-located here because you need to know who your stakeholders are before any meaningful planning can happen. On the exam, Initiating questions test whether you understand what belongs in a Charter vs. a Project Management Plan — a common trap. Initiating is brief by design; resist the urge to over-plan before you've formally authorized the project.
Planning
Planning is the heavyweight of the five — it houses roughly half of all 40 processes. This is where you define scope, build the WBS, develop the schedule, establish the cost baseline, plan quality, plan communications, plan risk responses, and create the Project Management Plan that ties everything together. The PMP itself is the master output of this Focus Area. What I tell every candidate: Planning isn't bureaucracy — it's risk prevention. Every hour spent in rigorous planning prevents three hours of reactive firefighting in Execution. The exam heavily rewards candidates who understand that planning processes exist to protect value delivery, not to generate paperwork.
Executing
Executing is where the project delivers. The PM directs and manages project work, manages team performance, acquires and develops resources, manages stakeholder engagement, and conducts quality assurance activities. Here's what nobody tells you about Executing questions on the exam: they're almost never about doing the work — they're about managing the people doing the work. The bulk of ECO 2026's People domain (~42%) plays out right here in Executing scenarios. Leadership style, conflict resolution, team motivation, and stakeholder communication dominate this Focus Area's exam questions.
Monitoring & Controlling
Monitoring and Controlling runs parallel to every other Focus Area — it never stops while the project is active. This is where you track performance against baselines, process change requests through integrated change control, monitor risks, and report status to stakeholders. PMBOK 8 reinforces that M&C is not a reactive function — proactive monitoring catches variance before it becomes a crisis. In agile environments, sprint retrospectives and burndown tracking are M&C activities. The exam's trickiest M&C questions involve knowing when to escalate vs. when to handle variance within your authority.
Closing
Closing is the most skipped Focus Area in real-world practice and one of the most tested on the exam. The two core processes are Close Project or Phase and Update Lessons Learned Repository. PMBOK 8 is explicit that Closing is never optional — even on agile projects, even when the project was cancelled, even when the client "just wants to move on." The lessons learned process is specifically elevated in PMBOK 8 as a knowledge asset for the organization, not just a checkbox. Exam scenarios that involve premature closure, scope gaps at handover, or unresolved contracts almost always have a Closing-related correct answer.
A visual guide to pmbok 8 focus areas: replacing traditional process groups for the 2026 PMP Exam
PMP Exam 2026: Focus Areas in Agile and Hybrid Contexts
Here's where PMBOK 8's reframing pays its biggest dividend. In a traditional waterfall project, the five areas do tend to run in rough sequence. But in an agile sprint-based project, you might plan the sprint (Planning), execute it (Executing), monitor its progress daily (M&C), and capture retrospective improvements (also M&C) — all within two weeks. Then you loop back to Planning for the next sprint.
PMBOK 8 acknowledges this explicitly. Focus Areas are designed to be concurrent, iterative, and context-dependent. The question isn't "which phase are we in?" — it's "which activities are most relevant right now?"
For exam scenarios set in agile or hybrid contexts, don't assume sequential flow. A retrospective at the end of a sprint belongs to Monitoring & Controlling — not Closing. A sprint planning session is Planning — even if the project is 70% complete. The Focus Area label follows the activity type, not the project timeline position.
PMP Exam 2026: Mapping PMBOK 8 Focus Areas to PMBOK 6 Groups
| PMBOK 6 Process Group | PMBOK 8 Focus Area | Process Count Change | Key Difference |
|---|---|---|---|
| Initiating | Initiating | 2 → ~2 | Minimal change; stakeholder ID co-located |
| Planning | Planning | 24 → ~20 | Processes consolidated; less prescriptive |
| Executing | Executing | 10 → ~8 | Quality & comms content redistributed |
| Monitoring & Controlling | Monitoring & Controlling | 12 → ~7 | Significant consolidation; agile M&C explicit |
| Closing | Closing | 2 → ~2 | Lessons learned elevated in importance |
According to PMBOK 8's Focus Area framework, which Focus Area is the PM PRIMARILY operating in during the retrospective activity?
Why C is correct
In PMBOK 8, Monitoring and Controlling encompasses all activities related to tracking performance, identifying variances, and implementing corrective or preventive actions. A sprint retrospective is explicitly a controlling mechanism — it evaluates process effectiveness and drives improvement. The fact that it occurs at a sprint boundary does not make it a Closing activity. Closing in PMBOK 8 involves formal acceptance of deliverables, final stakeholder sign-off, contract closure, and lessons learned archiving — not mid-project retrospectives. This is a very common trap on the exam.
Why the others are wrong
A — Closing applies to formal project or phase closure with deliverable acceptance. A sprint boundary is not a formal close. B — Executing covers direct project work and team management, not retrospective review. D — While the workflow decision for sprint 4 has a planning element, the primary activity — retrospective analysis and process correction — is unambiguously M&C territory.
📋 ECO 2026: Process (~50%) · Monitoring & Controlling Focus Area
