Overview
Process is 41% of the PMP exam, the largest domain, covering the technical delivery of projects across predictive, agile and hybrid approaches. It has ten tasks. Developing the integrated plan and delivery covers assessing project needs and recommending the development approach (predictive, agile or hybrid), then creating and maintaining an integrated plan. Managing scope covers defining and decomposing scope. Value-based delivery covers prioritizing and delivering value incrementally. The remaining tasks plan and manage resources, procurement, finance, quality, and schedule, evaluate project status with the right metrics and artifacts, and manage project closure.
Under the 2026 ECO, Process explicitly connects execution to business value, and selecting the delivery approach, predictive, adaptive/agile or hybrid, is a first-class task. Because about 60% of the exam is agile or hybrid, the exam rewards tailoring the process to the project, delivering value iteratively where appropriate, and applying the right planning, scheduling, quality and closure practices for the chosen approach.
How it's tested
PMP questions in this domain describe a delivery situation and ask how to plan, execute or control it. PMP questions are situational scenarios asking what a project manager should do, so read the scenario for the dynamic and choose the proactive, value-focused, best-practice response rather than a reactive or rigid one.
-
Choose the approach
A project's characteristics are described, and you recommend predictive, agile or hybrid delivery.
-
Deliver value
A delivery need is described, and you choose to prioritize and deliver value incrementally.
-
Plan and control delivery
A scope, schedule, quality or closure need is described, and you choose the right practice for the approach.
A project has unclear, evolving requirements and a customer who wants to see working results early and give feedback. A fully predictive plan locks scope upfront, which fits poorly here. An adaptive or agile approach delivers in increments, prioritizing the highest-value work and incorporating feedback each iteration, which suits evolving requirements and early value, so recommending an agile or hybrid approach is the tailoring decision the 2026 ECO expects.
Domains 10
Official domains from the PMI outline, in outline order.
2.1 Develop an integrated project management plan and plan deliveryAssess needs, recommend the development approach, and create the integrated plan.
- What it means
- This covers assessing project needs, complexity and magnitude, recommending a development approach (predictive, adaptive/agile or hybrid), determining critical information requirements including sustainability, recommending an execution strategy, creating and maintaining an integrated plan, estimating effort and resources, and assessing plans for dependencies, gaps and continued business value.
- What to understand
- Planning starts with choosing how to deliver: predictive for well-defined work, agile for evolving requirements, or hybrid combining both. The integrated plan ties all aspects together and is kept current. Tailoring the approach to the project's needs and complexity, rather than defaulting to one method, is a central 2026 ECO emphasis.
- How it shows up
- A project's characteristics are described, and you must recommend the development approach or the integrated planning action.
- Common confusion
- Defaulting to a predictive approach rather than tailoring predictive, agile or hybrid to the project's needs.
2.2 Develop and manage project scopeDefine, agree and decompose scope.
- What it means
- This covers defining scope, obtaining stakeholder agreement on it, and breaking scope down into manageable components, such as a work breakdown structure in predictive work or a backlog in agile.
- What to understand
- Scope defines what the project will and will not deliver. In predictive projects it is defined upfront and decomposed into a work breakdown structure; in agile it evolves as a prioritized backlog. Obtaining stakeholder agreement on scope and decomposing it appropriately for the approach prevents scope confusion and uncontrolled change.
- How it shows up
- A scope situation is described, and you must choose how to define, agree or decompose it for the approach.
- Common confusion
- Applying a fixed upfront scope where an evolving backlog suits the agile approach, or vice versa.
2.3 Help ensure value-based deliveryPrioritize and deliver value incrementally.
- What it means
- This covers identifying value components with stakeholders, prioritizing work by value and feedback, assessing opportunities to deliver value incrementally, examining business value throughout, verifying a measurement system tracks benefits, and evaluating delivery options to demonstrate value.
- What to understand
- The 2026 ECO reframes success around delivering value, not just meeting scope, schedule and budget. The project manager prioritizes the highest-value work, delivers it incrementally where possible so benefits are realized sooner, and continually measures and demonstrates value. This value focus is a defining theme of the updated exam.
- How it shows up
- A delivery or prioritization situation is described, and you must choose the value-maximizing, incremental approach.
- Common confusion
- Focusing only on scope, schedule and budget rather than prioritizing and delivering business value.
2.4 Plan and manage resourcesDefine, plan and optimize resources.
- What it means
- This covers defining and planning resources, both people and physical, based on requirements, and managing and optimizing resource needs and availability throughout the project.
- What to understand
- Resources must be planned to match the work and then actively managed as needs and availability change. The project manager secures the right resources, optimizes their use, and resolves shortages or conflicts. Good resource management keeps delivery on track without over- or under-allocating.
- How it shows up
- A resource need or conflict is described, and you must choose how to plan or optimize resources.
- Common confusion
- Planning resources once rather than continually optimizing to changing needs and availability.
2.5 Plan and manage procurementProcurement planning, contracts, vendors and negotiation.
- What it means
- This covers planning procurement, executing a procurement management plan, selecting contract types, evaluating vendor performance, verifying agreement objectives are met, participating in and strategizing negotiations, managing suppliers and contracts, and developing a delivery solution.
- What to understand
- Procurement obtains goods and services from outside the project. The project manager plans what to procure, selects appropriate contract types for the risk and work, negotiates and manages agreements, and evaluates vendor performance against the contract. Matching the contract type to the situation and managing vendors well controls cost and risk.
- How it shows up
- A procurement or vendor situation is described, and you must choose the contract type, negotiation or management action.
- Common confusion
- Choosing a contract type that misallocates risk for the situation, or not managing vendor performance against the agreement.
2.6 Plan and manage financeFinancial needs, reserves, tracking and reporting.
- What it means
- This covers analyzing project financial needs, quantifying risk and contingency allocations, planning spend tracking across the life cycle, planning financial reporting, anticipating future finance challenges, monitoring financial variations with the governance process, and managing financial reserves.
- What to understand
- Financial management plans the budget, sets contingency and management reserves for risk, tracks spending against the plan, and reports and responds to variances. Reserves cover identified and unforeseen risks. Monitoring financial performance, often with earned value concepts, and working with governance on variances keeps the project financially on track.
- How it shows up
- A budget or financial variance situation is described, and you must choose the financial planning, reserve or monitoring action.
- Common confusion
- Confusing contingency reserves (for identified risks) with management reserves (for unforeseen risks), or ignoring variance monitoring.
2.7 Plan and optimize quality of products and deliverablesQuality requirements, processes, compliance and improvement.
- What it means
- This covers gathering quality requirements for deliverables, planning quality processes and tools, executing a quality management plan, helping ensure regulatory compliance, managing the cost of quality and sustainability, conducting ongoing quality reviews, and implementing continuous improvement.
- What to understand
- Quality means meeting the requirements and fitness for purpose of the deliverables. The project manager plans how quality will be built in and verified, manages the cost of quality (prevention and appraisal versus failure costs), reviews quality continually, and improves processes. Building quality in, rather than inspecting it in at the end, is the preferred approach.
- How it shows up
- A quality situation is described, and you must choose the quality planning, assurance, control or improvement action.
- Common confusion
- Relying on end inspection rather than building quality in, or confusing quality assurance with quality control.
2.8 Plan and manage scheduleSchedule preparation, estimation, baselining and control.
- What it means
- This covers preparing a schedule based on the development approach, coordinating with other projects and operations, estimating tasks (milestones, dependencies, story points), using benchmarks and historical data, creating and baselining the schedule, executing the schedule management plan, and analyzing schedule variation.
- What to understand
- Scheduling sequences and times the work, using techniques suited to the approach: critical path and a baseline in predictive projects, iterations and story points in agile. The project manager estimates, builds and baselines the schedule, then tracks and analyzes variation to keep delivery on time. The method is tailored to the development approach.
- How it shows up
- A scheduling or delay situation is described, and you must choose the estimation, scheduling or variance-analysis action.
- Common confusion
- Applying predictive critical-path scheduling where iterative, story-point based scheduling fits the agile approach.
2.9 Evaluate project statusMetrics, artifacts, progress assessment and reporting.
- What it means
- This covers developing project metrics, analysis and reconciliation, identifying and tailoring needed artifacts, ensuring artifacts are created, reviewed, updated, documented and accessible, assessing current progress, measuring and updating metrics, communicating status, and continually assessing the effectiveness of artifact management.
- What to understand
- Evaluating status means measuring progress against the plan with appropriate metrics, keeping project artifacts current and accessible, and communicating status to stakeholders. The right metrics depend on the approach, such as earned value in predictive work or velocity and burndown in agile. Accurate status enables timely corrective action.
- How it shows up
- A status or metrics situation is described, and you must choose the right metric, artifact or reporting action.
- Common confusion
- Using the wrong metrics for the approach, such as earned value where agile velocity and burndown fit better.
2.10 Manage project closureApproval, closure criteria, transition and final activities.
- What it means
- This covers obtaining stakeholder approval of project completion, determining criteria to successfully close the project or phase, validating readiness for transition (such as to operations or the next phase), and concluding closure activities including final lessons learned, retrospectives, procurement, financials and resources.
- What to understand
- Closure formally ends the project or phase: confirming deliverables are accepted against closure criteria, transitioning the product to operations or the next phase, releasing resources, closing contracts and financials, and capturing lessons learned. Proper closure ensures value is handed over and knowledge is retained, and it is often overlooked.
- How it shows up
- A closure or transition situation is described, and you must choose the correct closure activity.
- Common confusion
- Skipping formal closure activities such as lessons learned, transition validation and contract closure.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Development approach
Predictive, adaptive/agile or hybrid.
- Remember
- Tailor it to the project.
- Tested as
- Planning questions.
- Trap
- Defaulting to predictive.
-
Integrated plan
Ties all project aspects together.
- Remember
- Kept current throughout.
- Tested as
- Planning questions.
- Trap
- Treating plans as static.
-
Value-based delivery
Prioritizing and delivering value incrementally.
- Remember
- A defining 2026 ECO theme.
- Tested as
- Delivery questions.
- Trap
- Focusing only on scope, schedule, budget.
-
Scope decomposition
WBS in predictive, backlog in agile.
- Remember
- Match to the approach.
- Tested as
- Scope questions.
- Trap
- Using the wrong decomposition.
-
Contingency vs. management reserves
For identified versus unforeseen risks.
- Remember
- Different purposes.
- Tested as
- Finance questions.
- Trap
- Confusing the two reserves.
-
Cost of quality
Prevention and appraisal versus failure costs.
- Remember
- Build quality in, not inspect it in.
- Tested as
- Quality questions.
- Trap
- Relying on end inspection.
-
Quality assurance vs. control
Process focus versus deliverable focus.
- Remember
- Assurance improves process; control checks output.
- Tested as
- Quality questions.
- Trap
- Confusing the two.
-
Schedule by approach
Critical path versus iterations and story points.
- Remember
- Match to the development approach.
- Tested as
- Schedule questions.
- Trap
- Using predictive scheduling for agile.
-
Status metrics by approach
Earned value versus velocity and burndown.
- Remember
- Choose metrics for the approach.
- Tested as
- Status questions.
- Trap
- Using the wrong metrics.
-
Project closure
Approval, transition, lessons learned, contract closure.
- Remember
- Formally close every project or phase.
- Tested as
- Closure questions.
- Trap
- Skipping closure activities.
-
Tailoring
Adapting process to the project.
- Remember
- Central to the 2026 ECO.
- Tested as
- Process questions.
- Trap
- Applying one method to all projects.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Predictive vs. agile vs. hybrid
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Predictive | Plan scope upfront | Well-defined, stable work | Using for evolving requirements |
| Adaptive/agile | Deliver in increments | Evolving requirements, early value | Using for fixed, stable scope |
| Hybrid | Combine both | Mixed needs | Forcing one approach throughout |
Contingency vs. management reserves
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Contingency reserve | For identified risks | Part of the cost baseline | Confusing with management reserve |
| Management reserve | For unforeseen risks | Outside the cost baseline | Confusing with contingency |
Quality assurance vs. quality control
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Quality assurance | Improves the process | Prevention-focused | Confusing with control |
| Quality control | Inspects the deliverable | Detection-focused | Confusing with assurance |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Predictive for evolving scope
- What candidates pick
- Plan full scope upfront for a project with unclear, evolving requirements.
- Why it looks right
- Upfront planning feels thorough.
- Why it's wrong
- Evolving requirements suit an adaptive or hybrid approach that delivers incrementally and incorporates feedback.
Clue to watch for Requirements are unclear and the customer wants early feedback.
-
Scope over value
- What candidates pick
- Deliver exactly the planned scope even if it no longer maximizes value.
- Why it looks right
- Meeting scope seems like success.
- Why it's wrong
- The 2026 ECO reframes success around value; the project manager prioritizes and delivers the highest-value work.
Clue to watch for Delivering value matters more than completing all original scope.
-
Inspect quality in
- What candidates pick
- Plan to find and fix defects by inspecting deliverables at the end.
- Why it looks right
- Inspection catches defects.
- Why it's wrong
- Quality should be built in through prevention and process, which costs less than failure found late.
Clue to watch for The goal is to achieve quality efficiently, not just detect defects.
-
Wrong reserve
- What candidates pick
- Use management reserve to cover an identified, analyzed risk.
- Why it looks right
- Both are reserves.
- Why it's wrong
- Contingency reserve covers identified risks within the baseline; management reserve covers unforeseen risks outside it.
Clue to watch for The risk was identified and analyzed versus truly unforeseen.
-
Skip closure
- What candidates pick
- Move the team to the next project without formally closing the current one.
- Why it looks right
- The work is done.
- Why it's wrong
- Formal closure validates acceptance, transitions the product, closes contracts and captures lessons learned.
Clue to watch for The project's deliverables are complete but closure steps remain.
Answer framework
For any Process-domain scenario, use these steps to find the answer the PMP expects.
- Read the project's characteristics and constraints carefully, and first choose the development approach that fits: predictive for stable work, adaptive or agile for evolving requirements, or hybrid combining both.
- Create and maintain an integrated plan, and define and decompose scope appropriately for the approach.
- Prioritize and deliver business value incrementally where possible, measuring benefits throughout.
- Plan and manage resources, procurement, finance, quality and schedule using techniques suited to the chosen approach.
- Evaluate status with the right metrics and artifacts, and formally close the project or phase with acceptance, transition and lessons learned. Where two options seem to fit, choose the one that most precisely matches the scenario and the chosen delivery approach.
Practice question
Want more like this? The PMP practice test has questions for every domain.
Checklist
0 of 10
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Give this domain the most study time, since at 41% it is the largest, and anchor it on the 2026 ECO's two big themes: tailoring the development approach and delivering value. First, master choosing and tailoring predictive, agile and hybrid delivery, because selecting the approach is now a first-class task and about 60% of the exam is agile or hybrid.
Then learn value-based delivery, prioritizing and delivering the highest-value work incrementally, which reframes success beyond scope, schedule and budget. Work through the delivery tasks, scope, resources, procurement, finance, quality and schedule, learning the key distinctions (contingency versus management reserves, quality assurance versus control, predictive versus agile scheduling and metrics) and how each adapts to the approach. Finally, learn proper project closure, which is often overlooked.
Because the exam is situational, drill scenario questions and ask which practice best fits the described project and approach. Because the PMP tests judgment in scenarios rather than recall, drill many situational practice questions and examine why the best-practice answer wins, applying the mindset across predictive, agile and hybrid contexts, and review missed questions by domain. Afterwards, move to Domain 3, Business Environment.
FAQ
How much of the PMP exam is the Process domain?
Process is 41% of the exam under the 2026 Examination Content Outline, the single largest domain, covering the technical delivery of projects.
How do I choose between predictive, agile and hybrid?
Match the approach to the project: predictive for well-defined, stable work; adaptive or agile for evolving requirements and early, incremental value; and hybrid to combine both. Selecting the approach is a first-class task in the 2026 ECO.
What does value-based delivery mean?
Prioritizing and delivering the highest-value work, often incrementally, and continually measuring business value, rather than defining success only by scope, schedule and budget. It is a defining theme of the 2026 exam.
What is the difference between contingency and management reserves?
Contingency reserves cover identified, analyzed risks and are part of the cost baseline. Management reserves cover unforeseen risks and sit outside the baseline, requiring management approval to use.
What is the difference between quality assurance and quality control?
Quality assurance focuses on improving the processes that produce deliverables (prevention). Quality control inspects the deliverables themselves to find defects (detection). The exam prefers building quality in over inspecting it in.
Does the schedule approach change with agile?
Yes. Predictive projects use techniques like critical path and a baseline, while agile uses iterations, story points, velocity and burndown. The scheduling and status metrics are tailored to the development approach.
How does the Process domain connect to the rest of the exam?
Process delivers the work that the led, engaged team of the People domain performs, within the governance, risk and change of the Business Environment domain, so the three are tightly linked.
Other Project Management certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- Project Management Professional (PMBOK 7) Same subject: Domain 2: Process (41%)
- PRINCE2 7 Practitioner Study guide
- PMI Risk Management Professional Study guide
- PMI Scheduling Professional Study guide
- CompTIA Project+ Study guide
- PRINCE2 7 Foundation Study guide
- Portfolio Management Professional Study guide
- Program Management Professional Study guide
- Certified Associate in Project Management Study guide
- Agile Project Management Study guide
- PMI Agile Certified Practitioner Study guide
- Disciplined Agile Scrum Master Study guide
Test your Domain 2 knowledge
You have covered delivery approach, scope, value, resources, procurement, finance, quality, schedule and closure. Test whether you can choose the right delivery practice under exam conditions.