Focus Areas: The PMBOK8 Activity Map

Below the Domain Level

The seven Performance Domains tell you what the PM is accountable for. Focus Areas tell you what work happens within each domain at each point in the project lifecycle. They connect a broad accountability, such as scope, to specific work such as planning scope management, eliciting and analyzing requirements, defining scope, and developing the WBS.

If you are familiar with PMBOK6, Focus Areas play a role similar to processes. They name project management activities, organize them under domains and process groups, and connect them to inputs, tools and techniques, and outputs. The next chapter covers ITTOs in detail. This chapter establishes the map.

The Five Process Groups

PMBOK8 uses the five Process Groups: Initiating, Planning, Executing, Monitoring and Controlling, and Closing. These are categories of project management work, not always calendar phases. A phase-gate project may use them at the start and end of each phase. An iterative project may cycle through them repeatedly in shorter increments.

The Complete Focus Area Map

The table below shows Focus Areas organized by Performance Domain and Process Group. This map follows the PMBOK8 reference naming convention used throughout this book. Empty cells do not mean the PM ignores that domain. They mean PMBOK8 does not name a formal Focus Area at that domain-group intersection.

PMBOK8 treats procurement as a cross-cutting practice rather than one of the seven performance domains. It does not appear as its own row in the Focus Area map because procurement activities span multiple domains simultaneously: contract authorization sits in Governance, vendor costs sit in Finance, and statement-of-work definition sits in Scope. In practice, the PM still needs to plan procurement, conduct procurements, and control procurements — those activities just integrate across domain boundaries rather than living in a single dedicated row.

How to Read This Map

The table is a navigation tool, not a reading assignment. You do not need to memorize every Focus Area. You need to know how to find the right one when a work situation requires it. Start with the domain, then identify the Process Group that matches what you are trying to do.

Situation 1: You are planning how to manage vendor relationships. The work is procurement-related and touches Governance and Finance. The planning work points you to procurement planning and the procurement content inside the project management plan.

Situation 2: You have completed a major deliverable and need sponsor acceptance. That is Scope work during Executing: Validate Scope.

Situation 3: Midway through execution, a team member's engagement drops and their output changes. That is Resources work during Executing: Manage Team.

Using the Map as a Planning Checklist

One practical use of the Focus Area map is as a planning completeness check. Before finalizing the project management plan, scan the Planning column. Do you have the planning artifacts or decisions needed for scope, schedule, finance, stakeholders, resources, and risk? If a cell points to work you have not done, decide whether to address it formally, handle it lightly, or document why it is not needed for this project.

This does not mean every Focus Area needs a heavy document. A small project may use a one-page communications table instead of a full communications management plan. What matters is that the PM made a deliberate tailoring decision — adjusting how formally each Focus Area is handled based on the project's specific context — instead of skipping the work by accident.

The Monitoring and Controlling Column

Notice that every domain has Monitoring and Controlling work. Governance monitors overall project work and manages changes. Scope, schedule, and costs are all controlled. Stakeholder engagement and communications are monitored. Resources are controlled and risks are monitored. The Monitoring and Controlling process group is the feedback loop that tells you whether execution is tracking to the plan and whether the plan still makes sense.

PMs who monitor schedule and cost but ignore stakeholders, communications, resources, or risk are running with a partial feedback loop. Those domains will still produce signals. The only question is whether the PM sees them early as data or late as surprises.

Focus Areas and the Reference Site

The complete Focus Area matrix, including ITTOs, is documented at hksmnow.com on the PMBOK definitions page linked in the course resources. Use it as a lookup tool when you need to locate a specific PMBOK8 activity or verify what inputs and outputs it requires. The next chapter shows how to use ITTOs diagnostically rather than as memorization material.

Focus Areas Across Delivery Approaches

Focus Areas still apply on agile and iterative projects, but they may happen in shorter cycles and with lighter documentation. Planning work may happen at the release or sprint level. Executing and Monitoring and Controlling work may happen inside each iteration. The map is still useful; the cadence changes.

Tailoring determines how formally each Focus Area is handled. A regulated project may produce a written artifact for every planning Focus Area. An iterative software team may address the same work through sprint ceremonies, backlogs, and team agreements. The question is not whether to do the work. The question is how to do it in proportion to the project.

What's Next

The next chapter covers ITTOs: Inputs, Tools and Techniques, and Outputs. Understanding ITTOs makes the map more useful as a reference and gives you a diagnostic language for identifying what is missing when a project output is weak or absent.

Reflect

• Look at the Planning column. On a project you know, which planning Focus Areas were formal, which were informal, and which were skipped?
• Which domains are usually monitored well in your organization, and which ones tend to surprise people later?
• Where do you draw the line between tailoring and under-managing?
• Stakeholder work appears across several Process Groups. What does that say about how PMBOK8 treats stakeholder engagement compared with schedule work?