II.7 — Plan and Optimize Quality of Products/Deliverables

II.7 · Last updated: 24/08/2026

Where this task sits

II.7 — Plan and Optimize Quality of Products/Deliverables is the seventh task in the Process domain of the 2026 ECO. The domain carries 41% of the exam.

It has seven enablers:

• Gather quality requirements for project deliverables
• Plan quality processes and tools
• Execute a quality management plan
• Help ensure regulatory compliance
• Manage cost of quality (CoQ) and sustainability
• Conduct ongoing quality reviews
• Implement continuous improvement

The verb "optimize" in the task title is worth noting: the ECO treats quality not as a threshold you set and leave, but as something you tune.

🔴 The number stayed — but the knowledge area disappeared

Good news first: II.7 stayed put. Quality was II.7 in 2021 and it is II.7 in 2026 — the only task in Domain II whose number did not change.

The bad news is structural rather than numeric. PMBOK® 8 gathers technical ways of working into seven performance domains: Governance, Scope, Schedule, Finance, Stakeholders, Resources, and Risk. Quality is not among the seven.

In the eighth edition quality is distributed across two places: it is one of the six project management principles (Embed Quality Into Processes and Deliverables), and its processes are seated inside other domains — Manage Quality Assurance sits in Governance, while measuring deliverable quality appears in the definition of Monitor and Control Scope.

The consequence: you cannot study quality from a single chapter. Remember too that the neighboring numbers in this domain (II.5, II.6, II.8, II.10) moved to other topics; for the general shape of the trap, see what changed in the 2026 PMP exam.

Quality assurance versus quality control

The most frequent distinction on this task, and the book separates the two cleanly.

The Guide starts with a caveat: quality management is sometimes called quality assurance, although quality management has a broader meaning in non-project work. In contrast, project management differentiates quality assurance and quality control as two distinct efforts (PMBOK® 8, Guide p.23):

• Quality assurance is about using project processes effectively. It involves following and meeting standards to assure stakeholders that the project's final results will meet their needs, expectations, and requirements. Related concepts: regulations, compliance, and audits.
• Quality control is about creating project deliverables that meet defined specifications and thresholds. It involves defining the attributes of the value generated by a project and ensuring deliverables achieve those attributes. Related concepts: product design and testing.

Short version: assurance looks at the process, control looks at the output.

The Manage Quality Assurance process is the process of ensuring project processes are performed in a manner consistent with stakeholder expectations; it involves translating the project management plan into executable activities that incorporate the organization's standards, regulations, and policies. Its key benefit is that it increases the probability of meeting project objectives and identifies ineffective processes and causes of poor project performance. The process is performed throughout the project (PMBOK® 8, Guide p.23).

The nine dimensions of quality

The ECO says "gather quality requirements." The book says what to gather, under nine headings that apply to both deliverables and processes (PMBOK® 8, Standard p.43–44):

• Performance — do the deliverables or processes function as intended by the project team and other stakeholders?
• Conformity — are they aligned with specifications and fit for use?
• Reliability — do they maintain the consistency necessary to meet or exceed desired outcomes?
• Resilience — can they cope with unforeseen failures and recover quickly?
• Satisfaction — do they elicit valuable feedback from customers and/or end users, including usability and user experience?
• Uniformity — do they demonstrate parity across similar outputs or workflows?
• Efficiency — are they optimized?
• Sustainability — do they contribute positively to economic, social, and environmental outcomes?
• Compliance — do they comply with regulatory requirements, relevant industry standards, and organizational standards?

The last two map one-to-one onto two separate ECO enablers: sustainability and regulatory compliance. For the compliance side in detail, see III.2 — Plan and Manage Project Compliance.

Quality as a principle: where the threshold goes

The Embed Quality Into Processes and Deliverables principle asks for a consistent focus on achieving target quality thresholds. Project quality entails satisfying relevant stakeholders' expectations and fulfilling project and product requirements; it focuses on meeting acceptance criteria for deliverables and on ensuring project processes are appropriate and as effective as possible (PMBOK® 8, Standard p.43).

Where the thresholds sit is written down too: quality thresholds typically address scope specifications, but they can also apply to schedule and cost, especially for projects where the value proposition is highly sensitive to those factors (PMBOK® 8, Standard p.43). The measures named include conformance to acceptance criteria, the definition of done (DoD), fitness for use, and overall efficiency.

Cost of quality (CoQ)

This is the only financial concept the ECO names outright.

The cost of quality includes all costs incurred over the life of the product by three things: investment in preventing nonconformance to requirements, appraisal of the product or service for conformance to requirements, and failure to meet requirements (PMBOK® 8, Guide p.158).

That trio sets up the exam logic: prevention and appraisal costs are spent deliberately; failure cost arrives when they fall short. The book draws the connection as well — subsequent efforts to correct deficiencies should result in a reduced cost of quality and an increase in sponsor or customer acceptance of the project's product (PMBOK® 8, Guide p.148).

CoQ is also listed as a data analysis tool of the Estimate Costs process (PMBOK® 8, Guide p.63) — quality decisions tie straight into the financial side, see II.6 — Plan and Manage Finance.

"Shift left": moving quality earlier

The book's most practical quality advice sits on the schedule side.

Embedding quality into the schedule includes ensuring scheduling practices and artifacts are reviewed for completeness and correctness; integrating product quality reviews as scheduled milestones; and practicing a "shift-left" approach, where quality practices are prioritized as early in the project life cycle as possible (PMBOK® 8, Standard p.46).

The same passage states the payoff: when potential quality issues can be anticipated and mitigated, the risk of defects and noncompliance is reduced (PMBOK® 8, Standard p.46).

That is exactly what the ECO's "conduct ongoing quality reviews" enabler asks for: review is not a gate at the end but work carried out throughout.

Audits and continuous improvement

The last two enablers look at the side of quality that reaches past the project.

Quality audits may be scheduled or random and may be conducted by internal or external auditors; they can confirm the implementation of approved change requests, including updates, corrective actions, defect repairs, and preventive actions (PMBOK® 8, Guide p.148).

The ECO's final enabler points directly at another task: implement continuous improvement. The book makes the link: foundational to embedding target quality thresholds is continuous improvement and waste elimination; adopting a continuous improvement mindset optimizes processes, boosts efficiency, and enhances maturity growth for the whole organization (PMBOK® 8, Standard p.43).

That is why the quality task works hand in hand with a task in the Business Environment domain — see III.6 — Continuous Improvement.

About the citations

The page numbers above refer to the PMBOK® Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked as "ECO."

⚠️ PMBOK® 8 contains two separate books in one volume, and their page numbering is independent:

• The Standard for Project Management — cited as Standard p.X
• A Guide to the Project Management Body of Knowledge — cited as Guide p.X

This page cites both books; which number belongs to which book is stated in every citation. The numbers are the books' printed page numbers.

This page explains the book; it does not replace it.