PMBOK 8 Focus Areas Explained: Life After Process Groups

Five overlapping translucent circles in navy, teal and gold forming a loop, representing the five PMBOK 8 Focus Areas

- T. Laketia Jones

If you learned project management with the five process groups, PMBOK 8 will feel familiar and new at the same time. The edition reimagines them as five Focus Areas: Initiating, Planning, Executing, Monitoring and Controlling, and Closing [S1]. The names are the same. The way you are asked to think about them is different.

What Changed From Process Groups to Focus Areas

The Standard for Project Management explains that the Focus Areas are groupings of processes, practices, or actions, and that they should not be confused with project phases [S2]. They are also not strictly sequential. Planning and monitoring, for example, can happen at the same time within a single phase [S2].

The Focus Areas are independent of industry and of development approach. Predictive, adaptive, and hybrid projects all honor these five areas in some way [S2]. Meanwhile, the PMBOK Guide maps the processes of each performance domain into the Focus Areas, so you can see, for instance, that Identify Stakeholders sits in Initiating while Monitor Risks sits in Monitoring and Controlling [S3].

The Five Focus Areas in Plain English

Initiating: Should we start, and why?

Initiating covers the actions that define a new project or phase, often including formal authorization [S2]. Its purpose is to align stakeholders on purpose, scope, and objectives. Initial scope is defined, early funding is committed, key stakeholders are identified, and roles are assigned, often captured in a project charter and stakeholder register [S2]. The key benefit is that projects are authorized only when they align with strategy and the business case [S2].

Planning: How will we get there?

Planning defines the course of action. PMBOK 8 describes planning as progressive elaboration, meaning it is ongoing and iterative rather than a one-time event [S2]. Predictive projects tend to front-load planning, while highly iterative projects often do brief roadmapping up front followed by frequent replanning [S2].

Executing: Doing the agreed work

Executing is where resources are coordinated, stakeholder engagement is managed, and the work gets done [S2]. The Standard points out that the plan can and should change whenever a change would improve the project's value, and that this Focus Area is often where the chosen development approach is most visible [S2].

See where you stand before you study. Take the free Skills Diagnostic to find out which exam tasks need the most attention.

Monitoring and Controlling: Are we on track?

This area tracks, measures, reviews, and regulates progress and performance [S2]. Monitoring compares actual and planned performance and reports it. Controlling analyzes variances and trends and recommends action. When variances appear, the team identifies corrective actions, which are then agreed with the right stakeholders [S2].

Closing: Finish well

Closing concludes the project or phase, and PMBOK 8 notes that it can also cover suspension or early closure, for example when canceling is the best way to protect the return on the investment [S2]. On the exam, closure tasks include obtaining stakeholder approval, validating readiness for transition, and capturing final lessons learned [S4].

Why "Not Phases" Matters on the Exam

Many candidates lose points by assuming the project is always moving neatly from one group to the next. PMBOK 8 is explicit that Focus Areas interact within each phase and overlap [S2]. Consider a scenario where a team is executing a release and discovers a new compliance requirement. You are executing, monitoring, and replanning at once. The best answer usually addresses the change through the right control process without stopping all work.

The exam reinforces this mindset. About 40% of items represent predictive approaches, and the remaining 60% are split between adaptive/agile and hybrid approaches, spread across all domains [S4]. That means you will see Focus Areas expressed through sprints, releases, and phase gates.

A Worked Example

Picture a hybrid project to open a new customer service center. The building fit-out follows a predictive plan, while the team configures the support software in two-week iterations.

  • Initiating: the sponsor approves a charter, and the team identifies stakeholders such as facilities, IT, the support team, and a union representative.
  • Planning: the fit-out gets a detailed baseline. The software work gets a high-level roadmap and a prioritized backlog.
  • Executing: contractors build out the space while the software team delivers working features every iteration.
  • Monitoring and Controlling: the project manager tracks fit-out progress against the baseline and reviews software progress at each iteration review. A late furniture delivery goes through change control.
  • Closing: the space is handed over to operations, the software is transitioned to the support team, and lessons learned are captured.

Notice that in the middle of the project, all five areas are active at once. Planning continues for the next iteration while execution and monitoring happen every day. That is exactly the overlap the Standard describes [S2].

How Focus Areas, Domains, and Principles Fit Together

  • Principles guide behavior and judgment. Our guide to the six PMBOK 8 principles covers them.
  • Performance domains group the processes by area of focus. See the seven performance domains.
  • Focus Areas describe when and why groups of actions happen across the life cycle.

When a scenario confuses you, try naming all three: which principle, which domain, and which Focus Area. The correct answer usually satisfies all three.

Study Tips

  1. Draw the overlap. Sketch a phase and shade where planning, executing, and monitoring happen at the same time.
  2. Learn the key benefit of each area. The Standard states one for each, and they make excellent flashcards [S2].
  3. Practice with mixed approaches. Work questions set in both predictive and agile contexts so the Focus Areas feel natural in both.
  4. Revisit the role of the PM. Our article on the role of a project manager connects these areas to day-to-day responsibilities.

Frequently Asked Questions

What are the five PMBOK 8 Focus Areas?

Initiating, Planning, Executing, Monitoring and Controlling, and Closing [S1][S2].

Are Focus Areas the same as the old process groups?

They keep the same names, but PMBOK 8 reimagines them as Focus Areas that overlap, are not phases, and apply to every development approach [S1][S2].

Can Focus Areas happen at the same time?

Yes. The Standard notes that they often overlap within a single phase; for example, planning and monitoring can happen simultaneously [S2].

Your Next Step

Want to see the Focus Areas in action across predictive, agile, and hybrid projects? The PMBOK 8 Exam Prep course teaches each one with visual slides and scenario quizzes, and it provides the 35 contact hours PMI requires.

Sources

  • [S1] PMI, A Guide to the Project Management Body of Knowledge (PMBOK Guide), 8th ed. (2025), Preface, pp. vii-ix
  • [S2] PMI, The Standard for Project Management, in A Guide to the Project Management Body of Knowledge (PMBOK Guide), 8th ed. (2025), Section 4, Project Management Focus Areas, pp. 69-73
  • [S3] PMI, A Guide to the Project Management Body of Knowledge (PMBOK Guide), 8th ed. (2025), Section 2, Table 2-1, Mapping Project Management Focus Areas to Performance Domains, p. 9
  • [S4] PMI, PMP Examination Content Outline (July 2026), pp. 5, 10 (approach mix; Process Task 10, Manage project closure)