Overview
The Process domain covers how the work gets planned, delivered, measured and closed. Its ten tasks run from choosing a predictive, adaptive or hybrid development approach and building an integrated plan, through scope, value-based delivery, resources, procurement, finance, quality and schedule, to evaluating status and closing the project or phase. Finance is a task in its own right, value-based delivery has its own task, and the outline explicitly calls out sustainability, cost of quality and artifact management.
PMBOK Guide 7th Edition reorganizes this material by outcomes rather than processes. The Development Approach and Life Cycle, Planning, Project Work, Delivery and Measurement performance domains describe what good looks like, and the Tailor based on context, Focus on value, Build quality into processes and deliverables, and Navigate complexity principles explain why one approach beats another. People skills from Domain 1 and the governance, change and risk controls in Domain 3 surround every Process decision.
How it's tested
Process questions mix scenario judgment with short calculations. Expect a variance or index to interpret, a schedule network fact, a contract type to choose, or an artifact to select for a given development approach. Many questions ask what to do NEXT once a status signal appears, and the best answer analyzes the cause before applying a correction.
-
Interpret the metric
The scenario gives EV, PV and AC values or a burndown trend and asks what it means or what to do. Compute the index, state whether the project is ahead or behind, then pick the analysis-first action.
-
Tailor to the approach
The scenario describes uncertainty, requirements stability and stakeholder availability, and asks which approach, estimate type or artifact fits. High uncertainty and frequent feedback favor adaptive; stable, regulated scope favors predictive.
-
Right owner, right artifact
Options differ only in which document or person handles the issue, for example product backlog versus WBS, or product owner versus sponsor. Identify the approach in use and the artifact that owns that information.
A predictive project reports EV of 400,000, PV of 500,000 and AC of 380,000. SPI is 0.8 and CPI is about 1.05, so the project is behind schedule but under budget. Options include crashing immediately, cutting scope, requesting more budget, or analyzing the schedule variance to find which critical-path activities are late. Analyze first, then choose compression with the cost headroom the CPI shows.
Tasks 10
Official tasks from the PMI outline, in outline order.
2.1 Develop an integrated project management plan and plan deliveryAssess the project, recommend a development approach and build and maintain an integrated plan.
- What it means
- The project manager assesses needs, complexity and magnitude, recommends a predictive, adaptive/agile or hybrid approach and an execution strategy, identifies critical information requirements such as sustainability, estimates effort and resources, and creates and maintains a plan that integrates all of it.
- What to understand
- Approach selection follows from requirements certainty, rate of change, delivery cadence, regulatory constraints and stakeholder availability; integration means checking consolidated plans for dependencies, gaps and continued business value. PMBOK 7 lens: Tailor based on context and Navigate complexity, with the Development Approach and Life Cycle and Planning performance domains.
- How it shows up
- A scenario describes evolving requirements, an engaged customer and a need for early feedback, or a fixed, regulated deliverable. The best answer recommends the approach that fits those facts, often hybrid when only part of the work is uncertain.
- Common confusion
- Hybrid is not a compromise to avoid choosing; it is chosen deliberately when components differ, such as predictive hardware and adaptive software in the same project.
2.2 Develop and manage project scopeDefine scope, obtain agreement on it and break it down.
- What it means
- The project manager defines what is and is not included, gets stakeholders to agree to it, and decomposes it into manageable pieces, using a WBS in predictive work or epics, features and user stories in adaptive work.
- What to understand
- The scope baseline is the approved scope statement, WBS and WBS dictionary; the 100% rule says the WBS covers all the work and nothing else, and work packages are the lowest level. In agile work scope is managed through a prioritized backlog with a definition of done. PMBOK 7 lens: Planning and Delivery performance domains, where scope clarity is a delivery outcome.
- How it shows up
- A stakeholder disputes whether a feature was included, or a team keeps finding unplanned work. The answer checks the scope baseline or backlog and acceptance criteria, then routes new work through change control or backlog refinement.
- Common confusion
- Validating scope (customer formally accepts completed deliverables) is not the same as controlling quality (the team checks deliverables meet requirements before the customer sees them).
2.3 Help ensure value-based deliveryIdentify and prioritize value, deliver incrementally and track benefits.
- What it means
- The project manager works with key stakeholders to identify what creates value, prioritizes work by value and feedback, looks for chances to deliver value incrementally, re-examines business value throughout, and makes sure benefits can be measured.
- What to understand
- Value can be tangible or intangible and is defined by the business case and benefits management plan; a minimum viable product (MVP) tests value with the least work, and MoSCoW or value-based ranking sets order. PMBOK 7 lens: Focus on value is the anchor principle, and the Delivery performance domain treats realized benefits, not completed tasks, as success.
- How it shows up
- Halfway through, a market shift makes a planned feature low value, or a sponsor wants everything delivered at once. The answer reprioritizes with stakeholders or proposes an incremental release that captures value earlier.
- Common confusion
- Output is not outcome: delivering every planned feature on time can still fail if the benefits in the business case are not realized.
2.4 Plan and manage resourcesPlan resources from requirements and optimize their availability.
- What it means
- The project manager defines team and physical resource needs from the requirements, then manages and optimizes those needs against actual availability throughout the project.
- What to understand
- Resource leveling changes start and finish dates to fit resource limits and can extend the critical path; resource smoothing adjusts only within available float, so the end date does not move. Resource calendars, histograms and a resource breakdown structure support the planning. PMBOK 7 lens: Planning and Project Work performance domains, plus Team for human resources.
- How it shows up
- A shared specialist is over-allocated across two projects. The best answer analyzes the impact and negotiates with the functional manager or levels the schedule, rather than asking the specialist to work overtime indefinitely.
- Common confusion
- Candidates think smoothing can fix any over-allocation; if the conflict sits on the critical path with no float, only leveling (which delays the finish) or added resources will resolve it.
2.5 Plan and manage procurementPlan procurement, select contract types, negotiate and manage suppliers.
- What it means
- The project manager plans what to buy and how, selects contract types, takes part in negotiations with a planned strategy, manages suppliers and contracts, evaluates vendor performance, and verifies the agreement's objectives are met.
- What to understand
- Fixed-price contracts put cost risk on the seller and suit well-defined scope; cost-reimbursable contracts (CPFF, CPIF, CPAF) put cost risk on the buyer and suit uncertain scope; time and materials suits small or staff-augmentation work. Make-or-buy analysis precedes the decision, and the contract is legally binding, so changes go through its terms. PMBOK 7 lens: Project Work performance domain, and Be a diligent, respectful, and caring steward for integrity in dealings.
- How it shows up
- A buyer cannot define scope precisely but needs a vendor to start, or a seller is late on a fixed-price deliverable. Choose cost-reimbursable or T&M for unclear scope, and use the contract's change and dispute terms for seller issues.
- Common confusion
- Under a fixed-price contract the buyer still bears schedule and quality risk; fixed price only caps the buyer's cost exposure for the defined scope.
2.6 Plan and manage financeAnalyze financial needs, allocate contingency, track spend and manage reserves.
- What it means
- The project manager analyzes financial needs, quantifies risk-based contingency, plans spend tracking and financial reporting, anticipates finance challenges, monitors variance through the governance process, and manages financial reserves.
- What to understand
- Contingency reserve covers identified risks (known-unknowns) and sits inside the cost baseline; management reserve covers unidentified risks (unknown-unknowns), sits outside the baseline but inside the budget, and needs management approval to use. Earned value metrics track performance: CV = EV - AC, SV = EV - PV, CPI = EV/AC, SPI = EV/PV, EAC = BAC/CPI when current performance continues. PMBOK 7 lens: Planning and Measurement performance domains; PMBOK 8 makes finance its own performance domain.
- How it shows up
- An identified risk occurs and the project manager must decide how to fund the response, or a CPI below 1 appears in a status report. Use contingency for the identified risk; investigate the cause of a poor CPI before requesting more funds.
- Common confusion
- Management reserve is not the project manager's to spend on identified risks, and it is not part of the cost baseline used for earned value.
2.7 Plan and optimize quality of products/deliverablesPlan quality, execute the quality plan, manage cost of quality and improve continuously.
- What it means
- The project manager gathers quality requirements, plans processes and tools, executes the quality management plan, helps ensure regulatory compliance, manages cost of quality and sustainability, runs ongoing reviews and drives continuous improvement.
- What to understand
- Cost of quality splits into cost of conformance (prevention and appraisal) and cost of nonconformance (internal and external failure); spending on prevention is usually cheaper than fixing defects found by customers. Quality assurance improves the process, quality control inspects the product. PMBOK 7 lens: Build quality into processes and deliverables, within the Delivery performance domain.
- How it shows up
- Defects are being found late by the customer, or the team plans to add a final inspection stage. The best answer moves quality earlier through prevention, such as reviews, test-first practices or clearer acceptance criteria.
- Common confusion
- Grade is not quality: a low-grade product with no defects can be high quality, while a high-grade product full of defects is low quality.
2.8 Plan and manage schedulePrepare, estimate, baseline and control a schedule suited to the development approach.
- What it means
- The project manager prepares a schedule that fits the chosen approach, coordinates with other projects and operations, estimates using milestones, dependencies or story points and historical data, baselines the schedule, executes the schedule management plan and analyzes variation.
- What to understand
- Critical path is the longest path with zero total float; crashing adds resources to critical activities and raises cost, while fast tracking overlaps activities and raises risk. Agile schedules use timeboxes, velocity and release planning; velocity is a team-specific planning measure, not a productivity score. PMBOK 7 lens: Planning performance domain, with Tailor based on context deciding the scheduling method.
- How it shows up
- A predictive project must finish two weeks earlier with no extra budget, or an agile team's velocity drops. Fast tracking fits the first when activities can overlap; investigating impediments fits the second before re-planning releases.
- Common confusion
- Crashing a non-critical activity does not shorten the project, and comparing velocity across teams is invalid because story points are relative within each team.
2.9 Evaluate project statusMeasure progress, tailor and manage artifacts, and communicate status.
- What it means
- The project manager develops metrics, assesses progress against them, identifies and tailors the needed artifacts, keeps artifacts current and accessible, communicates status, and checks whether artifact management itself is working.
- What to understand
- Good measures are specific, meaningful and include leading indicators (risk trends, cycle time) as well as lagging ones (cost to date). Predictive projects use earned value and variance analysis; adaptive teams use burndown and burnup charts, cumulative flow diagrams, cycle time and throughput. PMBOK 7 lens: Measurement performance domain, which warns against vanity metrics and measuring what is easy instead of what matters.
- How it shows up
- A dashboard looks green but stakeholders sense trouble, or a burnup shows scope growing faster than completion. The answer examines what the metrics are missing or the scope trend, then communicates a realistic forecast.
- Common confusion
- A burndown shows remaining work falling; a burnup shows completed work against a total scope line, so only the burnup makes scope growth visible.
2.10 Manage project closureObtain acceptance, validate transition readiness and close the project or phase.
- What it means
- The project manager gets stakeholder approval of completion, applies agreed closure criteria, confirms readiness to transition to operations or the next phase, and concludes final lessons learned, retrospectives, procurements, financials and resource releases.
- What to understand
- Closure applies to phases and to cancelled projects as well as successful ones; procurement closure confirms all deliverables are accepted and claims settled before contracts close. Transition is complete only when the receiving group can operate and support the result. PMBOK 7 lens: Delivery performance domain (benefits realized after handoff) and Project Work performance domain (closing out work and knowledge).
- How it shows up
- The sponsor cancels the project, or the customer has accepted the product but operations has not been trained. The answer still performs formal closure, or completes transition readiness before declaring the project closed.
- Common confusion
- Customer acceptance of deliverables is not the same as closing the project; administrative closure, lessons learned, release of resources and contract closure still remain.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Earned value core formulas
CV = EV - AC and SV = EV - PV show variance in currency; CPI = EV/AC and SPI = EV/PV show efficiency as ratios.
- Remember
- EV comes first in every formula; negative variance or an index below 1.0 is bad, positive or above 1.0 is good.
- Tested as
- Direct calculation and interpretation questions, and status scenarios that hand you the three numbers.
- Trap
- Swapping PV and AC, which turns a schedule question into a cost answer.
-
Forecasting: EAC, ETC, VAC, TCPI
EAC = BAC/CPI if current cost performance continues, or AC + (BAC - EV) if the variance was atypical; ETC = EAC - AC; VAC = BAC - EAC; TCPI = (BAC - EV)/(BAC - AC).
- Remember
- Pick the EAC formula from the scenario wording: 'expected to continue' means BAC/CPI, 'one-time' or 'will not recur' means AC + BAC - EV.
- Tested as
- Forecast questions ask what the project will cost at completion or how efficient remaining work must be.
- Trap
- Using BAC/CPI when the scenario explicitly says the overrun was a one-off event.
-
Contingency vs. management reserve
Contingency reserve funds responses to identified risks and is part of the cost baseline; management reserve covers unidentified risks and sits outside the baseline.
- Remember
- Cost baseline plus management reserve equals the project budget; using management reserve needs approval and changes the baseline.
- Tested as
- Funding decisions when a known risk or a surprise occurs, and budget composition questions.
- Trap
- Drawing on management reserve for a risk that was already in the risk register.
-
Contract types and risk
Firm fixed price (FFP), fixed price incentive fee (FPIF), fixed price with economic price adjustment (FP-EPA), cost plus fixed fee (CPFF), cost plus incentive fee (CPIF), cost plus award fee (CPAF) and time and materials (T&M).
- Remember
- FFP puts most cost risk on the seller; cost-reimbursable puts most on the buyer; T&M sits between and needs a not-to-exceed cap.
- Tested as
- Scenarios ask which contract fits given scope clarity, or who bears an overrun.
- Trap
- Choosing FFP when scope is still undefined, which invites change claims and padded bids.
-
Critical path and float
The critical path is the longest path through the network and determines the earliest finish; total float is how long an activity can slip without delaying the project.
- Remember
- Critical activities have zero total float in a normal network; there can be more than one critical path, which increases schedule risk.
- Tested as
- Network calculation questions and decisions about where to apply compression.
- Trap
- Shortening an activity that is not on the critical path and expecting the finish date to move.
-
Crashing vs. fast tracking
Crashing adds resources to critical-path activities to shorten them; fast tracking performs activities in parallel that were planned in sequence.
- Remember
- Crashing increases cost; fast tracking increases risk and possible rework; neither helps on non-critical activities.
- Tested as
- Schedule compression scenarios with a stated constraint on budget or risk tolerance.
- Trap
- Choosing crashing when the scenario says no additional budget is available.
-
Cost of quality
Cost of conformance is prevention (training, design reviews) and appraisal (testing, inspection); cost of nonconformance is internal failure (rework, scrap) and external failure (warranty, lost customers).
- Remember
- Investing in prevention lowers total cost; external failure is the most expensive category.
- Tested as
- Classification questions and scenarios about defects reaching the customer.
- Trap
- Classifying testing as prevention; testing is appraisal.
-
Velocity and story points
Story points are relative size estimates; velocity is the points a team completes per iteration, used to forecast how many iterations remaining work will take.
- Remember
- Velocity stabilizes after a few iterations and is only meaningful for the team that produced it.
- Tested as
- Release forecasting calculations and scenarios where management wants to compare teams.
- Trap
- Using velocity as a performance target, which leads teams to inflate estimates.
-
Minimum viable product (MVP)
The smallest release that lets the team test a value hypothesis with real users and learn whether to continue.
- Remember
- An MVP is for validated learning, not a cut-down final product; a minimum business increment (MBI) is the smallest piece that delivers business value.
- Tested as
- Value-based delivery scenarios that ask how to reduce risk on an uncertain product idea.
- Trap
- Treating MVP as permission to ship low quality.
-
Scope baseline vs. product backlog
The scope baseline is the approved scope statement, WBS and WBS dictionary, changed only via change control; the product backlog is an ordered, evolving list owned by the product owner.
- Remember
- In adaptive work, new requests go into the backlog and the product owner reorders it; in predictive work they go through a change request.
- Tested as
- Questions about handling a new request depend on which artifact governs scope.
- Trap
- Raising a formal change request for a new story in a Scrum project.
-
Burndown, burnup and cumulative flow
Burndown plots remaining work; burnup plots completed work against total scope; a cumulative flow diagram shows work in each state over time.
- Remember
- Widening bands on a cumulative flow diagram signal a bottleneck; a rising total scope line on a burnup signals scope growth.
- Tested as
- Status questions in adaptive projects ask what the chart reveals.
- Trap
- Reading a flat burndown as no work done when scope was added in the same period.
-
PMBOK 7 Development Approach and Life Cycle performance domain
The performance domain about choosing the development approach, delivery cadence and life cycle that fit the product and context.
- Remember
- Delivery cadence can be single, multiple or periodic; approach depends on the product, the project and the organization.
- Tested as
- Underpins approach-selection and hybrid-tailoring questions in task 2.1.
- Trap
- Assuming agile is always preferred; PMI expects the approach that fits the context.
-
PMBOK 7 Measurement performance domain
The performance domain about assessing performance and taking action, using metrics that support timely, accurate decisions.
- Remember
- Good metrics are tied to outcomes and include leading indicators; beware vanity metrics and the Hawthorne effect, where measuring changes behavior.
- Tested as
- Explains why the best status answer looks behind a green dashboard.
- Trap
- Treating any metric that improves as proof the project is healthy.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Contingency reserve vs. management reserve
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Contingency reserve | Time or money set aside for identified risks with planned responses. | Inside the cost baseline; the project manager can use it per the risk management plan. | Asking management for approval to use it, as if it were management reserve. |
| Management reserve | Funds held for unforeseen work within scope, the unknown-unknowns. | Outside the cost baseline but inside the total budget; management approval is needed and the baseline is then updated. | Including it in earned value calculations or using it for a risk already in the register. |
Fixed price vs. cost-reimbursable vs. time and materials
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Fixed price (FFP, FPIF, FP-EPA) | Seller delivers defined scope for an agreed price, possibly with incentives or economic price adjustment. | Seller carries most cost risk; requires well-defined scope. | Assuming the buyer has no risk; poor scope definition leads to claims and change orders. |
| Cost-reimbursable (CPFF, CPIF, CPAF) | Buyer pays the seller's allowable costs plus a fee that is fixed, incentive-based or awarded subjectively. | Buyer carries most cost risk; suits uncertain or evolving scope. | Confusing CPAF (subjective award decided by the buyer) with CPIF (formula sharing of over or under runs). |
| Time and materials (T&M) | Buyer pays agreed rates for labor and materials actually used. | Hybrid risk profile; quick to start for small or staff-augmentation work, usually with a not-to-exceed limit. | Using T&M for a large, long engagement without a cap, leaving the buyer open-ended cost exposure. |
Crashing vs. fast tracking vs. resource leveling vs. resource smoothing
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Crashing | Add resources to critical-path activities to shorten duration. | Shortens the schedule at added cost. | Applying it to activities with float. |
| Fast tracking | Overlap activities originally planned in sequence. | Shortens the schedule at added risk and possible rework; works only where dependencies are discretionary. | Choosing it for activities linked by a mandatory dependency. |
| Resource leveling | Adjust start and finish dates to resolve resource over-allocation. | Can change the critical path and extend the end date. | Expecting the finish date to stay fixed. |
| Resource smoothing | Adjust activities within their float to even out resource demand. | Does not change the critical path or end date, so it may not resolve every over-allocation. | Using it when the over-allocated activity has no float. |
ECO Process tasks vs. PMBOK 7 performance domains and principles (editorial mapping)
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Integrated plan and delivery approach; Schedule; Resources | Performance domains: Development Approach and Life Cycle, Planning. Principles: Tailor based on context, Navigate complexity. | Planning in PMBOK 7 is scaled to the approach: detailed up front for predictive, progressive and just-in-time for adaptive. | Expecting a full upfront plan and baseline in every scenario. |
| Value-based delivery; Scope; Quality; Closure | Performance domain: Delivery. Principles: Focus on value, Build quality into processes and deliverables. | Success is benefits realized and quality built in, not just outputs completed. | Judging success only by on-time, on-budget delivery. |
| Procurement; Finance; Evaluate project status | Performance domains: Project Work, Planning, Measurement. Principle: Be a diligent, respectful, and caring steward. | Stewardship covers financial integrity and fair supplier dealings; measurement drives decisions, not just reports. | Treating metrics and reports as the goal rather than inputs to action. |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Act on the metric without analysis
- What candidates pick
- Crash the schedule or request more budget as soon as SPI or CPI falls below 1.0.
- Why it looks right
- The number looks bad, and corrective action seems proactive.
- Why it's wrong
- PMI expects variance analysis to find the cause first; the fix depends on whether the delay sits on the critical path or the overrun is one-off.
Clue to watch for The question gives indices but no cause; look for 'analyze the variance' or 'determine the root cause'.
-
One approach for everything
- What candidates pick
- Use a fully predictive plan, or a fully agile one, for the whole project.
- Why it looks right
- Consistency feels simpler to manage and explain.
- Why it's wrong
- The ECO expects you to recommend an approach based on needs and complexity; mixed certainty across components calls for hybrid tailoring.
Clue to watch for The scenario mentions one stable, regulated component and one with evolving requirements.
-
Gold plating to delight the customer
- What candidates pick
- Let the team add an extra feature the customer did not request because there is slack.
- Why it looks right
- It seems to increase satisfaction at no visible cost.
- Why it's wrong
- Unrequested scope adds risk, cost and testing, bypasses change control, and may not deliver value the customer wants.
Clue to watch for The team proposes the extra on its own initiative without a request or prioritization by the product owner or sponsor.
-
Fixed price for uncertain scope
- What candidates pick
- Select a firm fixed price contract to protect the budget.
- Why it looks right
- It appears to cap the buyer's risk.
- Why it's wrong
- Sellers will pad bids or raise claims when scope is vague; cost-reimbursable or T&M fits uncertain work better.
Clue to watch for Phrases such as 'requirements are not yet defined' or 'research and development'.
-
Acceptance equals closure
- What candidates pick
- Mark the project complete once the customer signs off the final deliverable.
- Why it looks right
- Sign-off feels like the finish line.
- Why it's wrong
- Closure also needs transition readiness, procurement and financial closure, lessons learned and release of resources.
Clue to watch for The scenario mentions operations not yet trained, open vendor invoices or team members still assigned.
-
Comparing team velocities
- What candidates pick
- Use velocity to rank teams or push a slower team to match a faster one.
- Why it looks right
- It looks like objective performance management.
- Why it's wrong
- Story points are relative to each team, so velocity cannot be compared across teams and turning it into a target distorts estimates.
Clue to watch for A manager asks why Team A delivers 40 points and Team B only 25.
Answer framework
Use this sequence for Process questions about planning choices, performance signals or closing work.
- Identify the development approach in use and which artifact owns the information: the scope or cost baseline, the product backlog, the contract, or the management plan.
- If numbers are given, calculate the variance, index or forecast and state plainly what it means, such as behind schedule but under budget.
- Analyze the cause before correcting: check the critical path, the scope trend, defect sources, vendor performance or resource conflicts behind the signal.
- Choose the response that protects value and respects the constraint the scenario names, such as no extra budget, low risk tolerance or fixed contract terms.
- Update the relevant plan, baseline, backlog or forecast through the proper owner and communicate the change to the stakeholders who depend on it.
Practice question
Want more like this? The PMP (PMBOK 7) practice test has questions for every domain.
Checklist
0 of 14
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Begin with task 2.1 and the PMBOK 7 Development Approach and Life Cycle performance domain, because approach selection decides which artifacts and techniques apply in every later task. Then pair each remaining task with its predictive and adaptive form: WBS and backlog, Gantt and release plan, earned value and burnup.
Spend the most time on finance and schedule. Drill the earned value formulas until you can compute and interpret them in under a minute, including the two EAC variants and TCPI, and practice small critical path networks by hand. Learn contract types by who bears cost risk rather than by memorizing acronyms.
Commonly underestimated areas are value-based delivery, artifact management in task 2.9, and closure. The July 2026 outline treats value and finance as separate tasks and explicitly mentions cost of quality, sustainability and transition readiness, so expect scenarios on benefits tracking and handoff to operations, not only on schedules.
Afterwards, take timed mixed sets where roughly 60% of questions are adaptive or hybrid, mirroring the outline's stated split. For every calculation you miss, rewrite the formula and the clue word that selects it. Then move to Business Environment, which applies these baselines and reserves to change control and risk.
FAQ
How much of the PMP exam is the Process domain?
Process is 41% of scored items under the July 2026 outline, the largest domain. As a planning estimate that is about 74 of the 180 questions; PMI does not publish per-domain counts.
Do I need to memorize earned value formulas?
Yes. Finance is now a standalone task, and interpreting CPI, SPI and forecasts such as EAC is a core skill. Know which EAC formula applies when variance is typical versus atypical.
How is Process different under the July 2026 outline?
It fell from 50% with 17 tasks to 41% with 10 consolidated tasks. Value-based delivery, finance, and project status evaluation with artifact management are each explicit tasks, and sustainability appears in planning and quality enablers.
Are Process questions mostly predictive?
No. The outline states about 40% of all items are predictive and about 60% adaptive/agile or hybrid, across every domain. Expect backlog, velocity and burnup questions alongside critical path and earned value.
How does PMBOK 7 help with a process-heavy domain?
PMBOK 7 replaced process groups with outcome-focused performance domains such as Planning, Delivery and Measurement. Using them helps you choose the answer that fits the context rather than the one that follows a fixed process sequence.
What is the difference between validating scope and controlling quality?
Controlling quality is the team checking that deliverables meet requirements; validating scope is the customer or sponsor formally accepting them. Quality control normally happens first.
How long should I study Process?
As a planning estimate, about 50 to 70 hours of a 150-hour plan, with extra time for calculations if you are new to earned value or network diagrams.
Which domain should I study after Process?
Business Environment, because its change control, risk and governance tasks act on the baselines, backlogs and reserves defined here.
Other Project Management certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- Project Management Professional 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
Apply what this page covered, from tailoring the delivery approach to earned value forecasts, contract risk and closure, in timed scenario questions built on the July 2026 PMP outline.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the PMP (PMBOK 7) AI tutor Get any concept explained your way