The PMP Process Domain: What 41% of the Exam Covers

What the PMP Process domain covers after the July 2026 update

Process is 41% of the PMP under PMI's 2026 Exam Content Outline (ECO, revised August 11, 2026, as checked on October 27, 2026). PMI's new-exam page lists the previous weight as 50%, so the domain shrank by 9 points but is still the largest of the three. It has ten tasks, and the ECO says every exam includes questions on all tasks in a domain.

Process questions are not a test of memorized process names. They describe a project at some point in its life and ask for the planning or control step that fits, often in agile or hybrid settings, because the ECO spreads approaches across all domains. Full PMP prep on Passy is not on sale yet, and its page shows the share of the planned PMP question bank given to Process, the largest of the three.

The ten PMP Process tasks and the decision each one tests

Task names are paraphrased and the example situations are invented.

Four tasks have their own deep dives: earned value for finance and status, critical path and compression for the schedule, contract types for procurement, and agile and hybrid questions for the approach choice in task 1. The sections below cover scope, value, quality and closure.

Scope on the PMP: WBS vs product backlog

The ECO's scope task comes down to three moves: define the scope, get stakeholders to agree to it, and break it into manageable pieces. How you break it down depends on the approach.

• Work breakdown structure (WBS). The U.S. Government Accountability Office describes a WBS as a breakdown of the end product into smaller elements suitable for management control, arranged in a parent-child hierarchy whose lowest level is the work package. It is set up early and becomes more detailed as more is known. GAO calls a product-oriented WBS a best practice.
• Product backlog. The 2020 Scrum Guide describes the Product Backlog as an emergent, ordered list of what is needed to improve the product, with the Product Owner accountable for ordering it. Refinement breaks items into smaller, more precise ones.

On a hybrid project both can exist: a WBS for the fixed, contracted part and a backlog for features that will evolve.

Value-based delivery with an incremental release example

Task 3 is about delivering what stakeholders value, early and in pieces where that is possible, and being able to show that the benefits arrived. An invented example shows how those pieces fit.

A city permit office is moving applications online. Most calls to its counter are people asking where their application stands. The team ships an online status lookup first, because it removes the largest share of calls with the least work. Online payment follows in the second release and document upload in the third. Before the first release, the team agrees with the office manager how benefit will be measured: weekly status calls to the counter. If calls do not fall after release one, that is evidence to rethink release two, not just a number for the closing report.

The decision a question tests here is ordering by value and evidence, rather than by which feature is easiest, most requested by one person or first in the original plan.

Quality on the PMP: cost of quality and continuous improvement

Task 7 runs from gathering quality requirements to improving how the work is done, and it pairs cost of quality with sustainability and regulatory compliance. ASQ, the American Society for Quality, splits the cost of quality into four categories and calls the two failure categories together the cost of poor quality:

The exam logic follows from the table. If customers keep finding defects, money is leaking through external failure, and spending more on prevention and appraisal is usually the better trade. Continuous improvement means feeding what reviews and retrospectives reveal back into the way the team works, not waiting for the end of the project.

The four categories are easy to mix up under time pressure, which makes them good material for short recall. Make your own cards, or use the Process flashcards planned for full PMP prep once it launches.

Closing a PMP project or phase: what must be finished first

Task 10 asks when a project or phase can be called finished: stakeholders accept the result, the agreed closing criteria are met, the receiving team is ready to take over, and loose ends such as contracts, budgets, people and final lessons are wrapped up.

Invented scenario: a website redesign has launched and the customer has signed acceptance, but one supplier contract is still open over a disputed final invoice, and the final lessons-learned session hasn't happened. The sponsor asks to release the team this week. A strong answer finishes the loose ends first: resolve the invoice and formally close the contract, capture lessons learned and archive the records, then release the team and close. Releasing people while a contract is still open leaves the project unfinished on paper and in practice.

When you can name the task behind each row of the table above, move from reading to answering. At launch, the PMP page says full prep will let you practice the Process domain on its own, then mix it with the other two. For mixed practice across all three domains, start with the free PMP practice questions, and use the PMP study plan to give Process its 41% share of your time.