PMBOK 8 Focus Areas Explained: What Happened to Process Groups

PMBOK 8 brings back the 5 Process Group names as Focus Areas, alongside 7 Performance Domains and 40 processes. See what changed, the full process list, and what it means for the PMP exam.

Project Management Blogs Oct 13, 2026 0 10 Add to Reading List

PMBOK 8 Focus Areas Explained: What Happened to Process Groups

Quick Answer: PMBOK 8's five Focus Areas carry the same names as the five classic Process Groups: Initiating, Planning, Executing, Monitoring and Controlling, and Closing. Sources differ on whether to call this a rename or a reintroduction, but the practical point is the same: the lifecycle vocabulary is unchanged. What changed is the framing. PMBOK 8 presents Focus Areas as approach-agnostic activity areas that apply across predictive, agile, and hybrid delivery, and pairs them with a second structure of 7 Performance Domains containing 40 processes. If you already know the 5 Process Groups, you already know the 5 Focus Areas. The new learning is the 40-process list and how it replaced the 10 Knowledge Areas.

Three Editions, Three Different Structures

Most confusion about PMBOK 8 comes from treating it as an update to PMBOK 7. It is closer to a blend of PMBOK 6 and PMBOK 7. This table shows how the three editions organize the same body of knowledge.

	PMBOK 6	PMBOK 7	PMBOK 8
Core structure	5 Process Groups x 10 Knowledge Areas	12 Principles and 8 Performance Domains	6 Principles, 5 Focus Areas, and 7 Performance Domains
Number of processes	49	None defined	40
Lifecycle groupings	Process Groups	Not used	Focus Areas (same five names as the Process Groups)
Delivery approach	Mostly predictive framing	Approach-agnostic, outcome-focused	Explicitly predictive, agile, and hybrid
Best described as	A process rulebook	A principles-based framework	A process structure with principles-era framing

PMBOK 7 removed Process Groups entirely, which left many practitioners without the lifecycle vocabulary they used every day. PMBOK 8 restores that vocabulary in the form of Focus Areas and adds a trimmed process list so there is something concrete to learn again.

What Changed: Process Groups Return as Focus Areas

The five names are unchanged: Initiating, Planning, Executing, Monitoring and Controlling, and Closing. The sources we reviewed describe the Focus Areas as flexible categories rather than strict phases, bringing back a familiar flow without a rigid sequence. Brainbok reports that the 8th Edition Standard (Section 4.5) describes the Process Groups as renamed Focus Areas, while PM Study Circle calls it a reintroduction. Neither changes what you need to learn.

That distinction matters most for agile and hybrid work. An agile team initiates a release, plans each iteration, executes in short cycles, monitors every day, and closes a release without closing the product. Under the old label, you had to mentally translate. Under the new one, the language already fits.

The Five Focus Areas, Mapped to the Old Process Groups

PMBOK 8 Focus Area	Old Process Group	What it covers	How it looks in an agile team
Initiating	Initiating	Authorizing a project or phase and defining initial scope and stakeholders	Product vision, chartering a release, identifying who the customers are
Planning	Planning	Establishing scope, schedule, cost, quality, and risk baselines	Release planning, backlog refinement, sprint planning
Executing	Executing	Performing the work defined in the management plans	The sprint itself: building, testing, and integrating increments
Monitoring and Controlling	Monitoring and Controlling	Tracking, reviewing, and regulating progress and performance	Daily stand-ups, burndown charts, sprint reviews, change decisions
Closing	Closing	Finalizing all activities to formally close a project, phase, or contract	Release wrap-up, handover, retrospective, archiving lessons learned

Nothing in this table is new content to learn. These are the same five activity areas you would have studied under PMBOK 6, under a new label. The right-hand column is our illustration of how each one appears in agile delivery, not PMI's wording.

The 7 Performance Domains and Their 40 Processes

This is the genuinely new structure to learn. PMBOK 8 organizes its 40 processes under 7 Performance Domains. We cross-checked the list below against five independent sources (Brainbok, ProjInsights, mudassiriqbal.net, ProjectManagement.com.br, and MyPrepPilot). All five give the same 40 process names and the same domain counts of 9, 7, 6, 6, 5, 4, and 3. They are still secondary sources, so confirm exact names against your copy of the PMBOK 8 Guide before quoting them in your own materials.

Performance Domain	Count	Processes
Governance	9	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; Close Project or Phase
Stakeholders	7	Identify Stakeholders; Plan Stakeholder Engagement; Plan Communications Management; Manage Stakeholder Engagement; Manage Communications; Monitor Stakeholder Engagement; Monitor Communications
Scope	6	Plan Scope Management; Elicit and Analyze Requirements; Define Scope; Develop Scope Structure; Monitor and Control Scope; Validate Scope
Risk	6	Plan Risk Management; Identify Risks; Perform Risk Analysis; Plan Risk Responses; Implement Risk Responses; Monitor Risks
Resources	5	Plan Resource Management; Estimate Resources; Acquire Resources; Lead the Team; Monitor and Control Resourcing
Finance	4	Plan Financial Management; Estimate Costs; Develop Budget; Monitor and Control Finances
Schedule	3	Plan Schedule Management; Develop Schedule; Monitor and Control Schedule

Two things stand out. First, Governance is the largest domain and absorbs processes that used to sit in their own Knowledge Areas, including quality assurance, sourcing, and project-wide integration. Second, Schedule shrinks to three processes. Activity sequencing, duration estimating, and the other fine-grained scheduling steps from PMBOK 6 are no longer separate processes.

What Several Processes Were Called Before

One source (ProjectManagement.com.br) lists the closest PMBOK 6 name for many of the renamed processes. This is useful if you studied the older edition. Treat the pairings as a single-source crosswalk.

PMBOK 8 process	Closest PMBOK 6 name
Initiate Project or Phase	Develop Project Charter
Plan Sourcing Strategy	Plan Procurement Management
Manage Project Execution	Direct and Manage Project Work
Manage Quality Assurance	Manage Quality
Assess and Implement Changes	Perform Integrated Change Control
Elicit and Analyze Requirements	Collect Requirements
Develop Scope Structure	Create WBS
Plan Financial Management	Plan Cost Management
Develop Budget	Determine Budget
Monitor and Control Finances	Control Costs
Lead the Team	Develop Team and Manage Team
Perform Risk Analysis	Perform Qualitative and Quantitative Risk Analysis

The Grid: Where Each Process Sits Across Focus Areas

Focus Areas and Performance Domains answer different questions. A Focus Area answers when in the lifecycle the work happens. A Performance Domain answers what management discipline is involved. Every process sits at the intersection of one of each. "Develop Schedule" is a Planning process inside the Schedule domain. "Monitor Risks" is a Monitoring and Controlling process inside the Risk domain.

Several of the sources we checked also assign each process to a Focus Area, and they agree on every process except one: Identify Stakeholders is placed under Initiating by most and under Planning by one. The counts below use the majority placement. If you count Identify Stakeholders under Planning, Initiating drops to 1 and Planning rises to 20.

Focus Area	Processes	Examples
Initiating	2	Initiate Project or Phase; Identify Stakeholders
Planning	19	Define Scope; Develop Schedule; Develop Budget; Plan Risk Responses
Executing	8	Manage Project Execution; Acquire Resources; Lead the Team; Implement Risk Responses
Monitoring and Controlling	10	Monitor and Control Scope; Assess and Implement Changes; Monitor Risks
Closing	1	Close Project or Phase

The shape is informative on its own: roughly half of PMBOK 8's processes are Planning processes, which matches how much of the exam deals with planning decisions.

Where Did the 10 Knowledge Areas Go?

If you studied PMBOK 6, the quickest way to learn PMBOK 8 is to map what you already know. Again, this mapping is our inference from process names, not an official PMI crosswalk.

PMBOK 6 Knowledge Area	Most likely PMBOK 8 home
Integration	Governance (Integrate and Align Project Plans; Assess and Implement Changes; Close Project or Phase)
Scope	Scope
Schedule	Schedule
Cost	Finance
Quality	Governance (Manage Quality Assurance)
Resource	Resources
Communications	Stakeholders (Plan, Manage, and Monitor Communications)
Risk	Risk
Procurement	Governance (Plan Sourcing Strategy)
Stakeholder	Stakeholders

Three Knowledge Areas, Integration, Quality, and Procurement, effectively dissolved into Governance. If your PMBOK 6 notes treat procurement as a major standalone topic, expect it to be lighter in PMBOK 8.

A Worked Walkthrough: One Release Through Both Lenses

Suppose a team is building a customer portal in two-week iterations. Here is how the same work reads through the Focus Area lens and the Performance Domain lens. This is our illustration, not a PMI example.

What the team does	Focus Area (when)	Performance Domain (what)	Likely process
Agrees the release goal and who the users are	Initiating	Stakeholders	Identify Stakeholders
Breaks the goal into backlog items and agrees what is in scope	Planning	Scope	Define Scope
Sequences iterations into a release plan	Planning	Schedule	Develop Schedule
Builds and tests the first increment	Executing	Governance	Manage Project Execution
Reviews burndown and decides whether to adjust the plan	Monitoring and Controlling	Governance	Monitor and Control Project Performance
Handles a late change request from a customer	Monitoring and Controlling	Governance	Assess and Implement Changes
Hands over the release and runs a retrospective	Closing	Governance	Close Project or Phase

The same activity can be described by asking two different questions, which is why PMBOK 8 needs both structures. It also shows why Governance is the largest domain: it holds the processes that run across the whole effort.

How the Content Lines Up With the Three Exam Domains

Because the exam uses People, Process, and Business Environment, it helps to know where PMBOK 8 material feeds each one. Again, this is our study-aid mapping, not an official crosswalk.

PMP exam domain (weight)	PMBOK 8 material that feeds it most
People (33%)	Resources (Lead the Team, Acquire Resources) and Stakeholders (engagement and communications)
Process (41%)	Scope, Schedule, Finance, and Risk, plus the execution and monitoring processes in Governance
Business Environment (26%)	Governance (compliance, change, and benefits-related decisions) and the financial planning processes in Finance

If your preparation time is limited, this tells you where PMBOK 8 reading pays off most: the Planning and Monitoring processes in Scope, Schedule, Finance, and Risk, because they feed the largest exam domain.

Why the Reframing Matters (Our Reading)

We have not found a PMI statement explaining the choice of the term "Focus Area," so treat this section as interpretation. The pattern is consistent with PMBOK 7's move away from a rigid, sequential, predictive-looking structure: "Process Group" reads like a phase you complete, while "Focus Area" reads like something you attend to throughout the work.

The practical effect is that PMBOK 8 can describe lifecycle thinking that has always existed in project management without implying it applies only to predictive projects. An agile team still initiates, plans, executes, monitors, and closes, just not in one pass.

What This Means for the 2026 PMP Exam

PMBOK 8 is reference material, not the exam blueprint. The PMP exam is built directly from PMI's Examination Content Outline (ECO), organized around three domains: People, Process, and Business Environment, weighted 33%, 41%, and 26% as of the July 2026 update. Focus Areas and Performance Domains do not appear as exam domains, and PMI does not test them by that label.

What carries over is the underlying knowledge. Scheduling, risk, stakeholder engagement, and the rest of PMBOK 8's content map onto ECO tasks even though the labels differ. Candidates studying from PMBOK 8 are learning the same material the exam tests, structured for reference instead of exam weighting.

How to use PMBOK 8 while preparing

Read it for concepts and process purpose, not for label memorization. Ask what each process produces and why.
Study from the ECO task list first, then use PMBOK 8 to deepen any task you find weak.
Learn the Planning processes thoroughly. They are about half the book and the closest match to scenario questions about baselines, estimates, and risk.
Practice translating a scenario into a plain question: what is the team trying to achieve right now, and which practice fits? That skill is tested far more than vocabulary.

Common Misunderstandings

"PMBOK 8 replaced agile with process groups." No. The Focus Areas are presented as flexible categories that can apply to predictive, agile, and hybrid delivery.
"I need to memorize which process goes in which Focus Area." No. The exam does not test that mapping.
"PMBOK 8 is just PMBOK 6 again." No. It has 40 processes instead of 49 and drops the 10-Knowledge-Area grid in favor of 7 Performance Domains.
"PMBOK 7 is now obsolete for studying." Not entirely. PMBOK 8 keeps the Performance Domain concept, so PMBOK 7 background still helps, though the domain count and contents changed.

FAQ

Are Process Groups gone in PMBOK 8?

The classic structure is not used as such, but the five Focus Areas carry the same names: Initiating, Planning, Executing, Monitoring and Controlling, and Closing. Sources differ on whether to call it a rename or a reintroduction.

Do I need to memorize Focus Areas for the PMP exam?

No. The exam follows PMI's Examination Content Outline, organized by People, Process, and Business Environment, not PMBOK 8's Focus Area labels, though the underlying concepts overlap.

What is the difference between a Focus Area and a Performance Domain?

A Focus Area answers when in the project lifecycle work happens. A Performance Domain answers what management discipline is involved. PMBOK 8 uses both as a two-dimensional grid.

How many processes does PMBOK 8 have, and did that number change?

40 processes, down from 49 in PMBOK 6, distributed across 7 Performance Domains.

What happened to the 10 Knowledge Areas from PMBOK 6?

They no longer organize the book. Their content was regrouped into 7 Performance Domains. Several, such as Integration, Quality, and Procurement, show up as individual processes inside the Governance domain.

Is PMBOK 8 a return to PMBOK 6?

Partly. It brings back lifecycle structure and a defined set of processes, which PMBOK 7 had dropped, but with fewer processes and explicit support for predictive, agile, and hybrid delivery.

Will the PMP exam ask me which Focus Area a process belongs to?

Unlikely. The exam tests whether you can apply the right practice in a scenario, not whether you can file a process under a label. Learn what each process does and when to use it.

Where can I get the official PMBOK 8 Guide?

Through PMI directly. Membership includes free digital access; non-members can purchase it through PMI's publication store.