3.5 Quality Management

CAPM Certified Associate in Project Management Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & CAPM Exam Overview

1.1 About the CAPM Exam 1.2 PMBOK 7th Edition Overview 1.3 Exam Content Outline (ECO) 1.4 CAPM vs. PMP: Understanding the Differences

2 Chapter 2: Project Life Cycles and Processes (Domain 1, Tasks 1-2)

2.1 Projects, Programs, and Portfolios 2.2 Project Life Cycle Phases 2.3 The Five Process Groups 2.4 The Ten Knowledge Areas

3 Chapter 3: Project Management Planning (Domain 1, Task 2)

3.1 The Project Management Plan 3.2 Scope Management and the WBS 3.3 Schedule Management 3.4 Cost Management and Earned Value 3.5 Quality Management

4 Chapter 4: Project Roles, Responsibilities, and Ethics (Domain 1, Tasks 3-4)

4.1 Project Roles and Responsibilities 4.2 Leadership and Emotional Intelligence 4.3 Risk Management Fundamentals 4.4 PMI Code of Ethics and Professional Conduct 4.5 Problem-Solving Tools and Techniques

5 Chapter 5: Resource, Communication, and Stakeholder Management (Domain 1, Tasks 2-3)

5.1 Resource Management 5.2 Communications Management 5.3 Stakeholder Management 5.4 Procurement Management 5.5 Issues, Risks, Assumptions, and Constraints

6 Chapter 6: Predictive, Plan-Based Methodologies (Domain 2)

6.1 When to Use a Predictive Approach 6.2 WBS, Work Packages, and Activity Definition 6.3 Predictive Project Controls and Artifacts 6.4 Critical Path and Schedule Calculations

7 Chapter 7: Agile Frameworks and Methodologies (Domain 3, Tasks 1-3)

7.1 When to Use an Adaptive (Agile) Approach 7.2 The Scrum Framework 7.3 Kanban, XP, and SAFe 7.4 Agile Planning, Estimation, and Metrics 7.5 Agile Project Controls and Artifacts

8 Chapter 8: Business Analysis Roles and Stakeholder Communication (Domain 4, Tasks 1-2)

8.1 Business Analysis Roles and Responsibilities 8.2 Stakeholder Communication in Business Analysis 8.3 Business Case and Needs Assessment

9 Chapter 9: Requirements Gathering and Product Roadmaps (Domain 4, Tasks 3-4)

9.1 Requirements Gathering Approaches 9.2 Requirements Traceability Matrix 9.3 Product Roadmaps

10 Chapter 10: BA Methodologies and Requirements Validation (Domain 4, Tasks 5-6)

10.1 Business Analysis in Predictive and Agile Approaches 10.2 Acceptance Criteria and Requirements Validation 10.3 Business Analysis Tools and Techniques Summary

3.5 Quality Management

Key Takeaways Explain This Topic AI

Quality is the degree to which inherent characteristics fulfill requirements — conformance and fitness for use, not luxury

Quality (must be high) is distinct from grade (lower grade can be acceptable)

Prevention is cheaper than inspection; Cost of Quality splits into conformance and nonconformance

The seven basic quality tools include cause-and-effect, control chart, flowchart, histogram, Pareto chart, scatter diagram, and check sheet

Manage Quality (assurance, process focus, executing) differs from Control Quality (inspection, deliverable focus, monitoring)

Last updated: June 2026

What Quality Means on the Exam

On the CAPM, quality is the degree to which inherent characteristics fulfill requirements — conformance to requirements and fitness for use . It is not about gold-plating or building the most expensive option; a cheap pen that writes reliably is high quality. Four definitions are routinely tested:

Concept Definition
Quality Inherent characteristics meet requirements
Grade Category for items of same use but differing technical features
Precision Repeated measurements cluster tightly together
Accuracy A measurement is close to the true value

Key distinction: Low quality is always a problem; low grade may be acceptable. A bug-free app with few features is high quality, low grade — fine. A buggy app, regardless of features, is low quality — not fine. Likewise, a scale can be precise (consistent) yet inaccurate (consistently wrong).

The Three Quality Processes

Process Process group Focus
Plan Quality Management Planning Define standards, metrics, and the quality management plan
Manage Quality Executing Audit and improve processes (quality assurance)
Control Quality Monitoring & Controlling Inspect deliverables against standards (quality control)

Manage Quality (QA) Control Quality (QC)
Focus on processes Focus on deliverables
Proactive — prevents defects Reactive — detects defects
Process audits, design-for-X Inspection, testing, measurement
"Are we using the right process?" "Does the output meet spec?"

Control Quality produces verified deliverables , which then feed Validate Scope for formal customer acceptance.

Cost of Quality

The Cost of Quality (CoQ) is the total cost of conformance plus nonconformance across the product's life.

Category Type Examples
Prevention Conformance Training, documented processes, design reviews
Appraisal Conformance Testing, inspections, audits
Internal failure Nonconformance Rework and scrap found before delivery
External failure Nonconformance Warranty, recalls, liability, lost reputation after delivery

Exam principle: Prevention over inspection. A dollar spent preventing a defect is far cheaper than the failure cost of fixing it after it reaches a customer. External failure costs are the most expensive of all.

The Seven Basic Quality Tools

Tool Purpose
Cause-and-effect (Ishikawa/fishbone) Trace root causes of a problem
Control chart Track whether a process is stable over time
Flowchart Map process steps and decisions
Histogram Show a frequency distribution
Pareto chart Rank the vital few causes (80/20 rule)
Scatter diagram Reveal correlation between two variables
Check sheet (tally) Collect counts in a structured form
Statistical and Improvement Concepts

PDCA (Plan-Do-Check-Act): Deming's cycle for iterative improvement.

Kaizen: continuous, incremental improvement.

Six Sigma: data-driven defect reduction targeting 3.4 defects per million opportunities.

Normal distribution: about 68.3% of data falls within ±1σ, 95.5% within ±2σ, and 99.7% within ±3σ.

Control limits are set by the process (typically ±3σ); specification limits are set by the customer . The rule of seven flags a process as out of control when seven consecutive points fall on one side of the mean, even if all are within the control limits — a non-random pattern signals an assignable cause.

Quality Gurus and Foundational Ideas

The CAPM exam occasionally attributes quality ideas to their originators. W. Edwards Deming championed continuous improvement and the PDCA cycle and argued most defects come from the system, not the worker. Joseph Juran defined quality as fitness for use and developed the quality trilogy of planning, control, and improvement. Philip Crosby promoted zero defects and the idea that quality is free because prevention costs less than the failures it avoids. Genichi Taguchi introduced the loss function, showing that any deviation from target — not just exceeding a tolerance — imposes a cost.

Recognizing these names and their core message is enough for the exam.

Common Cause vs. Special Cause Variation

A central control-chart concept is the difference between common cause (also called random or normal) variation, which is inherent to a stable process, and special cause (also called assignable) variation, which comes from a specific, correctable source. Points inside the control limits with no pattern reflect common cause variation and should be left alone — adjusting a stable process is called tampering and usually makes things worse. Points outside the control limits, or a non-random pattern such as the rule of seven, indicate special cause variation that warrants investigation.

This is exactly why control limits (process voice) and specification limits (customer voice) are separate: a process can be perfectly stable yet still fail to meet customer specs, which is a capability problem, not a stability problem.

Audits, Inspection, and Quality Metrics

Manage Quality relies on quality audits — structured, independent reviews confirming the project follows its own processes and identifying good practices and gaps. Control Quality relies on inspection (examining, measuring, testing) to determine whether a deliverable conforms. Both draw on quality metrics defined during planning, such as defect density, on-time performance, or test coverage, with allowable tolerances . A practical exam rule: if the question is about improving how work is done, the answer lives in Manage Quality; if it is about checking whether the output is right, the answer lives in Control Quality.

Quick Quality Decision Guide

Defect found before delivery is an internal failure ; after delivery it is an external failure — and external is always costlier.

Tightly clustered but off-target readings are precise, not accurate .

A stable point inside control limits is common cause — do not react.

Process sets control limits ; customer sets specification limits — never confuse the two.