Quality Assurance vs. Quality Control in PMP – Explained

Your team is running full regression testing before every release. Defects keep escaping anyway. Adding more testing won’t fix this – fixing the process will. That’s the difference between QA and QC, and it’s one of the most precisely tested distinctions on the PMP exam. 

(Direct Answer)

Quality assurance is process-oriented. It checks whether the team follows methods that help prevent defects and asks, “Are we doing things correctly?” Quality control is product-oriented. It checks deliverables against specifications and asks, “Are the results correct?” In process-based PMBOK references, QA is associated with the Manage Quality process and QC with Control Quality. PMI’s 2026 PMP exam outline covers quality under Process Domain Task 7, “Plan and optimize quality of products/deliverables.” 

QA looks at the process. QC looks at the product.

For PMP candidates, this is a useful distinction: process issues call for examining how work is done, while deliverable issues call for checking the result.

Definitions side-to-side

Feature	Quality Assurance (QA)	Quality Control (QC)
PMBOK Process	Manage Quality	Control Quality
Core Definition	Planned and systematic activities ensuring the project follows the right processes to prevent defects.	Operational techniques and activities used to inspect and verify deliverables conform to specifications.
Core Tools & Examples	• Process audits• Design reviews• Training & standards adoption• Definition of Done (DoD)• Root cause analysis (RCA)• Benchmarking	• Inspections & sampling• Testing (UAT, automated suites)• Control charts & run charts• Acceptance criteria validation

The QA and QC definitions used here follow ASQ’s distinction between process-focused quality assurance and inspection-focused quality control. 

Head-to-Head Comparison

DIMENSION	QUALITY ASSURANCE	QUALITY CONTROL (QC)
Orientation	Process-focused	Product-focused
Purpose	Prevent defects by improving how the team works	Detect defects by verifying what the team produces
Timing	Throughout the project, proactively	At deliverable checkpoints, reactive
Who Owns It	PM, team, quality function, org policy	PM, testers, inspectors, customer
PMBOK Process	Manage Quality	Control Quality
Output	Process improvements, audit findings	Verified deliverables, quality measurements
Example	Auditing whether code reviews happen before merge	Running automated tests against release acceptance criteria
Risk If Confused	Treating QA as inspection leads to high rework costs	Treating QC as auditing leaves deliverables unverified

The PMBOK Quality Management Framework

Project quality management is often explained through three connected activities: Plan Quality Management sets how quality will be defined and verified; Manage Quality (QA) evaluates and improves the processes used; and Control Quality (QC) checks deliverables against requirements. 

The PMI quality philosophy draws on classical quality thinking: Deming’s continual process improvement, Juran’s quality trilogy of planning, control, and improvement, and Crosby’s principle that prevention is less expensive than the cost of failure. All three schools ground PMI’s view that quality is planned, not inspected, into a deliverable after the fact.

A useful practice scenario: when the same type of defect recurs despite testing, investigate root causes in both the process and the test coverage. A process audit may help identify systemic gaps; add or refine QC checks when the issue is coverage or verification.

In predictive projects

QA and QC are both formalized: documented quality plans, gate-review audits, formal inspection phases, and test execution against baselined specifications. Quality metrics are tracked throughout execution and reported to the sponsor. 

In agile environments

In agile environments, QA is built into team practices such as working agreements, peer reviews, and retrospectives, while QC checks work through tests and acceptance criteria. Both are part of each iteration rather than activities left until the end.

In hybrid projects

Predictive quality processes apply to fixed-scope contractual deliverables while agile quality practices apply to iteratively delivered features. A quality management plan must account for both modes, with clearly defined QA and QC activities for each delivery stream.

Cost of quality: Why prevention matters

The cost-of-quality framework provides the economic case for prioritizing QA. Total quality cost has two sides: costs of conformance (investments to prevent and detect defects) and costs of non-conformance (what you pay when quality fails).

Cost of quality breakdown
Cost of Conformance (Money spent to prevent failure)	Cost of Non-Conformance (Money spent because of failure)
Prevention Costs (QA Activities)• Training & onboarding• Process design & optimization• Quality audits	Internal Failure Costs (Before Delivery)• Reworking defective components• Scrap and waste material• Re-testing fixed items
Appraisal Costs (QC Activities)• Inspections & product testing• Control charts & measurements• Destructive testing loss	External Failure Costs (After Delivery)• Product recalls & warranty claims• Regulatory penalties (e.g., FDA/Fintech)• Lost reputation & customer churn

The PMI Implication: Investing in prevention (QA) can reduce the risk of defects and related failure costs, while appraisal (QC) helps detect defects before delivery. The right balance depends on the project’s cost-of-quality data.

Project examples across industries

IT / fintech

Fintech platform build

QA – audit code review checklist compliance

QC – automated regression tests before release

When a defect escapes into production, QA asks, “What process gap allowed this?” and QC asks, “How did our tests miss it?” Both questions belong in the post-incident review – neither replaces the other.

Construction

Commercial tower

QA – audit welding procedure spec adherence

QC – non-destructive weld tests and cube tests

A failed weld test (QC) should trigger a process audit (QA) of the welding crew’s training records. The product failure leads back to a process gap – which is how most quality failures begin.

Healthcare/pharma

Medical device manufacturer

QA – Audit design controls and change-control procedures

QC – Test finished devices against specifications before release

Medical device manufacturer

A regulatory finding may indicate a gap in quality assurance, a failure in quality control, or both. In the United States, the FDA’s Quality Management System Regulation (QMSR) took effect on February 2, 2026, and incorporates ISO 13485:2016, the international standard for medical device quality management systems. 

Finance

Core banking modernization

QA – Audit the migration methodology against the approved plan

QC – Reconcile migrated data against source records during the parallel run

Both run in parallel during the parallel-run phase. QA ensures the migration methodology is sound; QC verifies that the data that moved is accurate.

Manufacturing

Automotive supplier

QA – Audit the SPC methodology used to set up control charts

QC – Monitor control charts and measure output against tolerances

The QA program ensures the QC checks are well-designed. Without process audits confirming the SPC methodology, control charts may be present but poorly calibrated.

Catching defects is QC’s job. Preventing them is QA’s mission. The difference matters most at 2 am when a critical defect hits production, and the post-mortem asks how it got there.

PMP exam guidance

PMI’s PMP exam covers quality across the process domain. Situational questions typically test two scenarios. First, chronic defects despite extensive testing – the PMI-aligned answer is a process audit (QA), not more inspection. Second, a deliverable is rejected due to a specification mismatch – the answer is control quality. The exam tests whether you understand the directionality: process problems need QA, and product defects need QC. 

Three mnemonics worth memorizing before the exam:

1. “QA audits; QC counts.” – Auditing is a process activity; measuring and inspecting is a product activity.

2. “QA prevents; QC inspects.” – Prevention belongs to the process; inspection belongs to the deliverable.

3. “Process problem → QA. Product defect → QC. Both need each other.”

For Agile-related exam questions, the Definition of Done describes the quality state an Increment must meet and serves as a commitment in Scrum, rather than a QA artifact. Acceptance testing checks whether a product meets stated criteria and can support quality control, although Scrum does not define it as a QC artifact.

Common mistakes PMP candidates make

• ☐ Equating QA with testing. Testing is a QC activity. QA includes audits, training, and process design — not inspection of outputs.
• ☐ Treating QC as the only quality investment needed. Without QA, QC catches the same defects repeatedly because the underlying process never improves.
• ☐ Assuming a dedicated QA team owns quality alone. PMI assigns quality responsibility across the project team, PM, and stakeholders. No single function owns it.
• ☐ Skipping cost-of-quality analysis. Without it, organizations chronically underinvest in prevention and overspend on failure costs.
• ☐ Believing agile teams don’t need QA. Definition of Done, peer reviews, and retrospectives are QA practices, and continuous integration runs the automated QC checks. Agile teams practice both constantly, even without calling them that. 
• ☐ Confusing audits with inspections. Audits assess processes; inspections assess products. These are different activities with different inputs and outputs.
• ☐ Treating quality as a phase-end gate only. Both QA and QC are ongoing throughout the project lifecycle, not checkpoints at the end.
• ☐ Assuming “more testing” solves chronic quality issues. It often doesn’t. Process improvement is the answer when the same defect type recurs.
• ☐ Ignoring lessons learned for quality. Every defect should refine both the QA process design and the QC test coverage for the next iteration.
• ☐ Confusing the quality management plan with quality metrics. The plan governs the approach; metrics measure whether the approach is working.

6 questions to determine whether an action is QA or QC

QUICK DIAGNOSTIC

• Is the action examining a process or a product?

Process → QA. Product → QC.

• Is it designed to prevent defects or detect them?

Prevent → QA. Detect → QC.

• Is it an audit or an inspection?

Audit → QA. Inspection → QC.

• Does the output improve how the team works or verify what they produced?

How → QA. What → QC.

• Which PMBOK process does it belong to?

Manage Quality → QA. Control Quality → QC.

• Is it triggered by a recurring defect pattern or a specific deliverable handoff?

Pattern → QA process audit. Handoff → QC inspection.

Related Courses & Certifications: Strengthen your project management and Agile quality skills with our Project Management Professional (PMP)® Certification Training, AI Powered Project Manager, Leading SAFe® Agilist (SA) Certification Training, and SAFe® Scrum Master (SSM) Certification Training