Project Quality Management is Knowledge Area 5 in PMBOK 6 (its processes are numbered 8.1 to 8.3 because they sit in chapter 8 of the guide). It has three processes: Plan Quality Management (decide the standards and how you will prove you met them), Manage Quality (make sure the way you work produces good results) and Control Quality (check the finished deliverables). The big idea is simple: prevention is cheaper than inspection. Build quality in, do not try to inspect it in at the end. The Cost of Quality, the seven basic quality tools and improvement models like PDCA and Six Sigma are the tools you use to do this.
This page is my exam-focused view of quality: the processes, the tools and the traps PMI likes to test. If you want a ready-to-use document for your own project, use my quality management plan template instead. This page is for understanding the concepts and passing the exam.
Quality is the most misunderstood knowledge area. In daily life "quality" means premium or excellent. In project management it has a precise meaning: the degree to which a set of inherent characteristics fulfils requirements. If you deliver exactly what was agreed, to the agreed standard, that is a quality project, even if the product is basic. If you deliver something fancy but different from what was agreed, that is not.
So your job is not to deliver the best possible product. It is to deliver the right product, as the requirements define it, every time, and to be able to prove it.
On this page you will find the three PMBOK processes with their inputs, tools and outputs, the Cost of Quality, the seven basic quality tools, quality vs grade, prevention vs inspection, improvement models, quality in agile and hybrid projects, and exam tips.
What is the difference between quality and grade?
Before the three processes, learn two distinctions. Both come up on the PMP exam and the APM PMQ.
Precision vs Accuracy: Another Tested Distinction
Accuracy means how close a result is to the target. Precision means how close the results are to each other, whether or not they hit the target. A process can be precise but not accurate (it gives the same wrong result every time), accurate but not precise (right on average but all over the place), or both, which is what you want. Example: a machine that always cuts parts 2mm too long is precise but not accurate, so you recalibrate it. A machine that varies a lot around the target is accurate on average but not precise, so you improve the process.
Project Quality Management: The 3 PMBOK Processes
Plan Quality Management is where you decide which quality requirements and standards apply, and how you will show that you met them. Its main output is the Quality Management Plan, part of the project management plan. It sets out the standards, the quality objectives, who does which quality activity, the tools you will use, how you will check the work and what happens when something does not conform.
Key activities in Plan Quality Management include:
- Benchmarking: Comparing planned quality practices or the project's characteristics with comparable projects or organisations to identify best practices and establish performance improvement targets.
- Cost-benefit analysis: Evaluating the trade-off between the cost of quality activities (prevention and appraisal) and the benefits (reduced rework, customer satisfaction, reduced warranty costs). The core argument for quality investment: prevention costs less than cure.
- Cost of Quality (CoQ) analysis: Identifying and estimating the costs of both conformance (doing it right) and non-conformance (fixing it when it is wrong). See the full CoQ framework below.
- Logical data models: Mapping data flows to identify quality requirements for information assets.
- Quality function deployment (QFD): A technique that translates customer wants and needs into project and product technical requirements.
The plan also sets the quality metrics: the measurable checks you will use. Examples: defects per 1,000 lines of code, first-pass yield (the percentage of items that pass inspection first time), on-time delivery rate or customer satisfaction score. Without metrics, quality becomes an opinion instead of a measurement.
- Project Charter
- Project Management Plan (Requirements, Risk, Stakeholder engagement)
- Project Documents (Assumptions log, Requirements docs, Risk register, Stakeholder register)
- Enterprise Environmental Factors
- Organisational Process Assets
- Expert judgement
- Data gathering (benchmarking, brainstorming, interviews)
- Data analysis (cost-benefit analysis, CoQ)
- Decision making (multi-criteria decision analysis)
- Data representation (flowcharts, logical data models, matrix diagrams)
- Test and inspection planning
- Meetings
- Quality Management Plan
- Quality Metrics
- Project Management Plan Updates
- Project Documents Updates
Manage Quality was called "Perform Quality Assurance" in older PMBOK editions. It is an executing process. Plan Quality Management asks "which standards apply and how will we meet them?" Manage Quality asks "are our processes working as planned, and how can we make them better?" The focus is on process quality: making sure the way the team works produces good outputs. Checking individual deliverables is Control Quality's job.
The main tool here is the quality audit: a structured, independent review that checks whether the team follows the processes in the quality plan, and whether those processes actually work. Audits can be internal or external, and they often end with recommendations for improvement.
Process analysis looks for ways to improve a process by removing waste, reducing variation and cutting steps that add no value. This links to Lean and Six Sigma. The result is often a change request to fix a process that keeps producing defects.
Manage Quality also produces the Quality Report: a summary of quality activities, audit findings, issues, non-conformances and recommended corrective actions. It feeds Control Quality and wider project decisions.
- Project Management Plan (Quality Management Plan)
- Project Documents (Lessons learned register, Quality control measurements, Quality metrics, Risk report)
- Organisational Process Assets
- Data gathering (checklists)
- Data analysis (alternatives analysis, document analysis, process analysis, root cause analysis)
- Decision making (multi-criteria decision analysis)
- Data representation (affinity diagrams, cause-and-effect, flowcharts, histograms, matrix diagrams, scatter diagrams)
- Audits
- Design for X (DfX)
- Problem solving
- Quality improvement methods (PDCA, Six Sigma)
- Quality Report
- Test and Evaluation Documents
- Change Requests
- Project Management Plan Updates
- Project Documents Updates
Control Quality is where you check the deliverables. You inspect, test and measure the actual outputs to confirm they meet the requirements in the quality plan, and you record the results. Manage Quality looks at processes. Control Quality looks at deliverables. This is the inspection side of quality management.
Control Quality uses the seven basic quality tools (see the next section) to analyse data, spot defect patterns and find root causes. It produces Quality Control Measurements, which go back into Manage Quality so the team can improve its processes.
Key concepts in Control Quality:
- Verified deliverables: The primary output: deliverables that have been checked against quality requirements and confirmed to meet them. Verified deliverables then flow into Validate Scope (Scope Management) for formal acceptance by the customer.
- Prevention vs inspection: Control Quality is an inspection activity. It detects defects after they are created. Manage Quality is a prevention activity. It works to eliminate the conditions that cause defects. Both are necessary, but investments in Manage Quality (prevention) typically reduce the burden on Control Quality (inspection).
- Tolerances vs control limits: Tolerances are the acceptable range specified by the customer or stakeholder (the specification limits). Control limits are statistically determined boundaries within which a process is considered in statistical control. A process can be within control limits yet outside tolerances (the process is stable but wrong) or within tolerances yet outside control limits (the process is meeting requirements but showing signs of instability).
- Project Management Plan (Quality Management Plan)
- Project Documents (Lessons learned register, Quality metrics, Test and evaluation documents)
- Approved Change Requests
- Deliverables
- Work Performance Data
- Enterprise Environmental Factors
- Organisational Process Assets
- Data gathering (checklists, check sheets, statistical sampling, questionnaires)
- Data analysis (performance reviews, root cause analysis)
- Inspection
- Testing / product evaluations
- Data representation (cause-and-effect, control charts, histograms, scatter diagrams)
- Meetings
- Quality Control Measurements
- Verified Deliverables
- Work Performance Information
- Change Requests
- Project Management Plan Updates
- Project Documents Updates
The 3 quality management processes at a glance
| Process | Process group | Key output |
|---|---|---|
| Plan Quality Management | Planning | Quality management plan and quality metrics |
| Manage Quality | Executing | Quality reports and test and evaluation documents |
| Control Quality | Monitoring and Controlling | Quality control measurements and verified deliverables |
Source: PMBOK Guide, 6th edition (PMI).
The Cost of Quality Framework
The Cost of Quality (CoQ) splits every quality-related cost into two groups. The cost of conformance is money you spend to prevent defects and check the work. The cost of non-conformance is money you spend because the work was not right. This framework is how you make the business case for quality, and it is a regular PMP exam topic.
- Quality training and education
- Process documentation and standardisation
- Quality planning and requirements definition
- Supplier qualification and evaluation
- Equipment maintenance and calibration
- Peer reviews and design reviews
- Process improvement initiatives
- Testing (unit, integration, system, acceptance)
- Inspections and audits
- Destructive testing and sampling
- Quality measurements and data collection
- Supplier audits
- Rework: fixing defects found internally
- Scrap: discarding defective work
- Retesting after rework
- Downtime caused by quality failures
- Root cause analysis for internal failures
- Schedule recovery costs caused by rework
- Warranty claims and product recalls
- Liability costs and legal fees
- Customer complaint handling
- Loss of future business (reputational damage)
- Emergency field fixes and patches
The Seven Basic Quality Tools
PMBOK lists seven basic quality tools, often called the "7 QC tools". They came from Japanese quality management. Each one helps with a different kind of quality problem, from collecting data to finding root causes to deciding what to fix first.
Continuous Improvement Models in Project Quality Management
Why is prevention better than inspection?
Prevention activities eliminate the root causes of defects before they can occur. They focus on process design and improvement rather than defect detection.
- Clear, testable requirements with agreed acceptance criteria
- Peer reviews and design reviews of work in progress
- Team training in quality standards and techniques
- Process standardisation and documentation
- Root cause analysis of past defect patterns
- Supplier qualification and pre-qualification
- Configuration management to prevent unauthorised changes
Cost profile: Lower cost per defect avoided. Prevention investment is front-loaded but reduces total quality cost by eliminating defects before they multiply through the delivery chain.
Inspection activities detect defects after work is complete. They provide a quality gate before deliverables are accepted or passed to the next stage.
- Testing (unit, integration, system, user acceptance)
- Formal inspections and reviews against specification
- Statistical sampling of deliverable populations
- Independent quality audits
- Control charts monitoring process output
- Acceptance criteria verification
- Third-party certification or compliance audits
Cost profile: Higher cost per defect found. Inspection does not eliminate defects. It finds them after they exist. The cost of finding a defect during inspection is always higher than the cost of preventing it in the first place.
How Quality Management Connects to Every Other Knowledge Area
Quality Management in Agile, Waterfall and Hybrid Environments
In predictive projects, quality management follows the full three-process PMBOK model with formal quality gates at stage boundaries:
- Quality requirements and metrics defined upfront in Plan Quality Management
- Quality assurance activities embedded throughout execution phases
- Formal testing phases (SIT, UAT) scheduled as distinct project stages
- Quality audits conducted by independent QA function or PMO
- Stage gate reviews include quality performance assessment
- Defect management through formal defect tracking systems
- Quality sign-off required before stage boundary approval
- Lessons learned on quality fed into OPAs for future projects
Strength: Clear quality governance and formal acceptance gates. Risk: Defects found late in testing phases are expensive to fix, the waterfall model can defer quality feedback until significant rework is already costly.
Agile approaches quality management fundamentally differently: quality is built in continuously rather than inspected at the end:
- Definition of Done (DoD): The team's agreed quality checklist that every user story must meet before being marked complete: testing, code review, documentation, acceptance criteria met. The DoD is Quality Management operationalised at sprint level.
- Test-Driven Development (TDD): Tests written before code is written, ensuring quality requirements are defined before implementation begins: prevention over inspection in its purest form.
- Continuous integration / continuous testing: Automated tests run on every code commit, providing immediate quality feedback and catching defects within hours of introduction.
- Sprint retrospectives: PDCA applied to the team's working processes every sprint: identifying quality process improvements and implementing them immediately.
- Customer/product owner involvement every sprint provides continuous quality feedback
- No separate "quality phase": quality is validated continuously
Strength: Defects found within the sprint are far cheaper to fix than defects found in a separate testing phase. Risk: Without clear Definition of Done, quality can vary between sprints and teams.
Quality Management in Hybrid Environments
In hybrid projects, the formal quality controls (standards, audit rights, stage gate reviews) stay at the programme level, while delivery teams use agile quality practices inside each sprint. The Definition of Done is the quality gate for each sprint, and the stage review is the quality gate for the programme. Sprint results such as defect counts and test pass rates roll up into the formal quality report.
Quality Management: 7 Exam Tips for PMP and APM PMQ
Worked exam example: which answer would PMI pick?
Here is the kind of question I give my PMP students. Your team keeps finding the same welding defect at inspection. Rework is eating the schedule. What should you do first? A) Add more inspectors. B) Ask the supplier for a discount. C) Do a root cause analysis and fix the process. D) Report the issue to the sponsor.
The answer is C. More inspectors (A) only finds more defects; it does not stop them. B and D do nothing about the cause. When you see a repeated defect, think "process problem, so Manage Quality, root cause, then a change request to fix the process".
Mistakes I see most often in mock exams:
- Mixing up Manage Quality (process) and Control Quality (deliverable).
- Thinking a basic, cheap product is a quality problem. It is a grade choice.
- Choosing "inspect more" when the question is about stopping defects.
- Forgetting that verified deliverables go to Validate Scope for customer acceptance.
Use This Knowledge Area in Your PMP or APM PMQ Exam
Quality processes, the Cost of Quality and the seven quality tools are tested in both the PMP and the APM PMQ. On the PMP, remember that the 2026 exam is built on the Exam Content Outline and PMBOK 8, not on these PMBOK 6 processes directly. The processes are still the easiest way to learn quality step by step, and the ideas behind them appear in many situational questions.