2.4 The Ten Knowledge Areas

What the Knowledge Areas Do

The ten knowledge areas organize the 49 processes by subject matter — the expertise a project manager applies. Where process groups slice work by when (initiate, plan, execute, monitor, close), knowledge areas slice it by what (scope, cost, risk, and so on). Crossing the 5 groups with the 10 areas gives the classic process grid. Although the CAPM is structured around the four ECO domains, this vocabulary appears throughout the exam.

The Ten Knowledge Areas at a Glance

Integration Management — The Unifier

Integration Management ties all other areas together and is the only knowledge area with at least one process in all five process groups. Its seven processes:

• Develop Project Charter (Initiating)
• Develop Project Management Plan (Planning)
• Direct and Manage Project Work and Manage Project Knowledge (Executing)
• Monitor and Control Project Work and Perform Integrated Change Control (Monitoring & Controlling)
• Close Project or Phase (Closing)

Exam tip: If a question asks which knowledge area touches every process group, the answer is Integration Management. It is the project manager's coordination role made explicit.

The Triple Constraint (Iron Triangle)

Three knowledge areas form the classic Triple Constraint:

1. Scope — what the project delivers
2. Schedule — when it delivers
3. Cost — what it costs

They are interdependent; change one and at least one other must move:

• More scope → more cost and/or longer schedule
• Shorter schedule → more cost or less scope
• Smaller budget → less scope or longer schedule

Modern practice expands this to include Quality, Risk, and Resources, sometimes drawn as a star or as competing constraints. On the exam, the classic Triple Constraint is Scope, Schedule, Cost.

Mapping Areas to Process Groups

Each area distributes its processes across groups, which is why one subject is managed from planning through control:

High-Yield Terminology

Scope — Product scope = features/functions of the result; project scope = the work to deliver it; the WBS is the hierarchical decomposition of deliverables; the scope baseline = approved scope statement + WBS + WBS dictionary.

Schedule — the critical path is the longest sequence of dependent activities, setting the minimum project duration; float (slack) is how long an activity can slip without delaying the project; a milestone has zero duration.

Cost — a budget = cost baseline + management reserves; Earned Value Management (EVM) measures performance against plan.

Risk — a risk is an uncertain event with a positive or negative effect; a threat is negative risk; an opportunity is positive risk.

Trap: Create WBS is a Scope process and Identify Risks is a Risk process — neither belongs to Integration, even though both feed the integrated plan.

Quality, Communications, and Stakeholder Vocabulary

Three more areas supply frequently tested terms. Quality distinguishes quality (conformance to requirements — fitness for use) from grade (a category of features); a low-grade product can still be high quality if it meets its requirements. It also separates quality assurance (Manage Quality — auditing the processes, in Executing) from quality control (Control Quality — inspecting the deliverables, in Monitoring & Controlling).

Communications management notes that the number of potential communication channels grows with team size by the formula n(n−1)/2, where n is the number of stakeholders — a classic plug-in calculation (10 people → 45 channels). Stakeholder management, the 10th area added in the PMBOK Guide 5th edition, uses the power/interest grid to classify stakeholders into manage closely, keep satisfied, keep informed, or monitor.

Procurement and Resource Essentials

Procurement management covers acquiring goods or services from outside the organization. Know the main contract types and who carries cost risk:

Resource management spans both people (acquire, develop, and manage the team) and physical resources (materials, equipment, facilities). It is the only knowledge area besides Integration with multiple processes in Executing, reflecting that leading the team is hands-on, day-to-day work during execution.

How the Areas Tie Back to the ECO

The CAPM Exam Content Outline (ECO) is organized into four domains — Fundamentals (36%), Predictive Methodologies (17%), Agile Frameworks (20%), and Business Analysis (27%) — not by knowledge area. But the knowledge-area vocabulary is the connective tissue: the predictive domain leans on the scope/schedule/cost grid and the WBS, the agile domain reframes scope and schedule into backlogs and iterations, and business analysis maps to requirements work that feeds Scope Management.

Learning the ten areas gives you the precise language the question writers use across all four domains, which is why this section is high-yield even though no exam domain is named "knowledge areas."