← ECO 2026 tasks

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

II.7 · Last updated: 11/10/2026

Quality as something you keep adjusting

II.7 — Plan and Optimize Quality of Products/Deliverables is the seventh task in the Process domain of the 2026 ECO, the domain that carries 41% of the exam. Seven enablers sit under it:

The verb "optimize" in the title signals an attitude. The ECO does not see quality as a fixed threshold that is set once at the start and then defended; it sees quality as something that is watched and improved for as long as the project runs.

The number stayed, but quality has no domain of its own

Candidates working from older material get some good news here, because the number II.7 has not moved. Quality was II.7 in 2021 and it is still II.7 in 2026, which makes it one of the few tasks in the Process domain that kept its number.

The real change is in the structure of PMBOK itself. PMBOK® 8 gathers its technical areas of work into seven performance domains (Governance, Scope, Schedule, Finance, Stakeholders, Resources, and Risk), and quality is not one of the seven. In the eighth edition quality is spread across two places. One is the principle Embed Quality Into Processes and Deliverables, which is one of the six project management principles. The other is a set of quality-related processes placed inside other domains, with Manage Quality Assurance sitting in Governance (PMBOK® 8, Guide p.9) and the measurement of deliverable quality folded into the Monitor and Control Scope process.

So quality cannot be studied from a single chapter. It also helps to remember that II.5, II.6, II.8, and II.10 in the Process domain now point to different topics than they did in 2021. The overall picture is in what changed in the 2026 PMP exam.

Assurance watches the process, control watches the output

The distinction the exam asks about most on this task is the one between quality assurance and quality control, and the book draws a clear line between them (PMBOK® 8, Guide p.23). It starts by pointing out a source of confusion. Quality management is sometimes called "quality assurance", although outside project work quality management has a much broader meaning. Project management, for its part, treats quality assurance and quality control as two distinct efforts.

Quality assurance is about using project processes effectively. It means following and meeting standards so that stakeholders can be assured the project's results will meet their needs, expectations, and requirements, and its related concepts are regulations, compliance, and audits. Quality control is about creating deliverables that meet defined specifications and thresholds, which is why product design and testing belong on that side. Put briefly, assurance looks at how the work is done and control looks at what the work produces.

The Manage Quality Assurance process makes sure that project processes are performed in a way that is consistent with stakeholder expectations. The book credits it with raising the probability of meeting project objectives and with identifying ineffective processes and the causes of poor project performance (PMBOK® 8, Guide p.23).

Nine dimensions of quality

The ECO asks you to gather quality requirements, and the book frames what to gather as nine questions that apply to deliverables and processes alike (PMBOK® 8, Standard pp.43-44):

The last two dimensions line up exactly with two separate ECO enablers, sustainability and regulatory compliance. The compliance side is covered in more depth in III.2 — Plan and Manage Project Compliance.

Where the thresholds go

The Embed Quality Into Processes and Deliverables principle asks for a steady focus on target quality thresholds. According to the book, the quality of a deliverable and of the processes that produce it is measured by conformance to acceptance criteria, the definition of done (DoD), fitness for use, and overall efficiency (PMBOK® 8, Standard p.43).

The book also says what the thresholds apply to. They typically address scope specifications, but they can also apply to schedule and cost, especially in projects whose value proposition is sensitive to those factors (PMBOK® 8, Standard p.43). When most of a project's value depends on delivering on time, a delay can turn into a quality problem.

Cost of quality

Cost of quality (CoQ) is the only financial concept the ECO names outright in this task. The book defines it as all the costs incurred over the life of the product from three sources, namely 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).

The logic inside that trio comes up often on the exam. Prevention and appraisal costs are spent deliberately and in advance, while the cost of failure appears later, when those two fell short. The book also gives the relationship a direction, since later efforts to correct deficiencies are expected to reduce the cost of quality and increase the sponsor's or customer's acceptance of the product (PMBOK® 8, Guide p.148).

Cost of quality is also one of the data analysis tools of the Estimate Costs process (PMBOK® 8, Guide p.63), so decisions about quality feed directly into the financial side. The Standard makes the link explicit, saying that embedding quality into finance helps control costs by preventing rework and reducing waste (PMBOK® 8, Standard p.46). The financial side in detail is on the page for II.6 — Plan and Manage Finance.

Moving quality earlier

The book's most practical advice on quality sits on the schedule side (PMBOK® 8, Standard p.46). Embedding quality into the schedule means reviewing scheduling practices and artifacts for completeness and correctness, putting product quality reviews on the calendar as scheduled milestones, and practicing a "shift-left" approach, in which quality practices are brought as early in the life cycle as possible. The same page states the result. When quality is built into every aspect of the project, potential problems can be anticipated and mitigated, and the risk of defects and noncompliance goes down.

That is exactly what the ECO's enabler on ongoing quality reviews asks for. A quality review is meant to be repeated throughout the project, and a single gate passed at the end does not satisfy it.

Audits and continuous improvement

The last two enablers look at the part of quality that reaches beyond the project. Quality audits may be scheduled or random and may be carried out by internal or external auditors, and they can confirm that approved change requests (including updates, corrective actions, defect repairs, and preventive actions) have actually been implemented (PMBOK® 8, Guide p.148).

The ECO's final enabler, implementing continuous improvement, points straight at another task. The book makes the connection itself. Continuous improvement and waste elimination are foundational to embedding target quality thresholds, and adopting a continuous improvement mindset optimizes processes, boosts efficiency, and supports the maturity growth of the whole organization (PMBOK® 8, Standard p.43). For that reason the quality task works closely with a task in the Business Environment domain, III.6 — Continuous Improvement.

About the citations

Every page number above refers to the PMBOK® Guide, Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked "ECO" separately.

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

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 describes the book; it does not replace it.

iyzico ile Öde, Visa, MasterCard