Process

Process is where the exam tests how a project is actually run, and at 41 percent it is the largest of the three domains, ahead of People (33) and Business Environment (26), per the 2026 PMP Exam Content Outline. Almost every task here turns on one decision you make first, the delivery approach, because the PMP validates leading projects in any way of working: predictive, hybrid, or agile, and the exam runs roughly 40 percent predictive work against 60 percent adaptive-and-hybrid work. Predictive (plan-driven, sometimes called waterfall) fixes scope up front and delivers near the end; adaptive (agile, iterative) keeps scope open and delivers in increments; hybrid blends the two by component, and you choose from the project's own traits, not from habit. That choice reshapes everything downstream, yet beneath the differences runs one loop, commit to a baseline or plan, measure the real work against it, then steer, so the recurring trap is reaching for predictive machinery (a full work breakdown structure, a frozen schedule baseline, earned value, a fixed-price contract) on an adaptive scenario, or doing the reverse.

Read the ten subtopics as a single pass through that delivery loop, in four movements, and reach for each stop when its decision comes due. First you frame the work: Integrated Planning and Delivery picks the approach and reconciles every subsidiary plan into one, Developing and Managing Scope agrees what is and is not being built, and Value-Based Delivery pins down the benefits the plan exists to produce and orders work so they arrive early. Then you secure the inputs: Planning and Managing Resources lines up the people and materials, Planning and Managing Procurement decides what to buy and on which contract type, and Planning and Managing Project Finance sets the budget, reserves, and funding timing. Next you set the bar and pace: Planning and Optimizing Deliverable Quality defines what good means and builds it in rather than inspecting it in, while Planning and Managing the Schedule turns estimates into a dated plan or a forecast. Finally you measure and close: Evaluating Project Status compares real progress against the baseline, and Managing Project Closure finishes the work against explicit exit criteria and hands over a running capability.

When two options are each mechanically valid, the exam rewards the one that fits the chosen approach and is grounded in the plan and the data, not the one that is fastest or most forceful. Tailor rather than template: there is no process you always apply, so a full WBS, earned value, or a fixed-price contract is right only when the project's approach calls for it. Steer from the baseline and the evidence: assess and plan before acting, measure variance before escalating, and route change through the agreed process instead of around it. And prefer the proactive move, confirm availability before you commit the plan, agree acceptance criteria before you build, and define what closed means before you start closing.