Project Quality Management (PMBOK Knowledge Area 8) is the collection of three processes that incorporate the organisation's quality policy into the project and ensure the project and its deliverables meet stakeholder expectations. It covers Plan Quality Management (identifying quality requirements and standards, and defining how quality will be achieved and verified), Manage Quality (translating the quality plan into executable activities and continuously improving processes), and Control Quality (monitoring and recording results of quality activities to assess performance and recommend changes). Quality management is fundamentally about prevention over inspection — it is far cheaper to build quality in than to find and fix defects after the fact. The Cost of Quality framework, the seven basic quality tools, and continuous improvement models such as PDCA and Six Sigma are the analytical backbone of this knowledge area.
Quality is the most philosophically rich of all the project management knowledge areas — and the most frequently misunderstood. The word "quality" in everyday language implies something excellent or premium. In project management, quality has a precise technical meaning: the degree to which a set of inherent characteristics fulfils requirements. A project that delivers exactly what was specified, to the agreed standard, is a quality project — even if that specification is for a basic product. A project that delivers something excellent but different from what was agreed is not.
This distinction matters enormously for how project managers think about quality. The job is not to deliver the best possible product — it is to deliver the right product, as defined by the requirements, consistently and verifiably. Quality management provides the processes, tools and philosophy to achieve that reliably across the project lifecycle.
This guide covers all three PMBOK processes in depth, the complete Cost of Quality framework, all seven basic quality tools, the distinction between quality and grade, prevention vs inspection, continuous improvement models, how quality management operates in Agile and hybrid environments, and how it connects to every other PMBOK knowledge area.
Foundational Concepts
Quality vs Grade — A Critical Distinction
Before examining the three processes, two foundational distinctions must be understood — both are examined on the PMP and APM PMQ.
⭐ Quality
Quality is the degree to which a set of inherent characteristics fulfils requirements. A deliverable is high quality if it meets its specified requirements consistently and reliably. Quality is about conformance to specification — does it do what it was supposed to do, to the standard it was supposed to do it to? Low quality is always a problem. A product that fails its requirements is not fit for purpose, regardless of how basic or advanced those requirements are. Poor quality has direct cost consequences: rework, defect correction, warranty claims, customer dissatisfaction.
🏷️ Grade
Grade is a category assigned to products or services having the same functional use but different technical characteristics. A budget hotel and a five-star hotel both have a grade — low grade and high grade respectively. Low grade is not necessarily a problem — if the customer requires and has agreed to a low-grade product, delivering a low-grade product that meets all specified requirements is a quality outcome. The PMP exam frequently tests the distinction: low quality is always a problem; low grade is only a problem if the customer required high grade. A high-grade product that does not meet requirements is low quality — and that is always a problem.
💡
Prevention over inspection — the central principle of modern quality management. Prevention means building quality into the process from the start — designing processes that reduce defect probability, training team members, writing clear requirements, conducting peer reviews. Inspection means checking output after work is done and removing defects. Prevention is almost always cheaper than inspection: finding and fixing a defect during requirements costs a fraction of finding it during testing, which costs a fraction of finding it in production. The Cost of Quality framework quantifies this relationship precisely.
Precision vs Accuracy — Another Tested Distinction
Accuracy is how closely a measurement or output conforms to the correct or target value — it is about hitting the right target. Precision is how consistently results cluster together regardless of whether they are close to the target — it is about repeatability. A process can be precise but inaccurate (consistently producing the wrong result), accurate but imprecise (occasionally hitting the target but inconsistently), or both precise and accurate (the goal). Quality control measurements must distinguish between these: a process that consistently produces parts 2mm too large is precise but inaccurate and needs recalibration; a process that randomly varies ±5mm around the target is accurate on average but not precise and needs process improvement.
The Three Processes
Project Quality Management — The 3 PMBOK Processes
8.1
Plan Quality Management
Planning Process Group · Identifies quality requirements and standards; defines how quality will be achieved and verified
+
Plan Quality Management is the process of identifying quality requirements and standards for the project and its deliverables, and documenting how the project will demonstrate compliance with quality requirements. Its primary output is the Quality Management Plan — a component of the Project Management Plan that defines the quality standards applicable to the project, the quality objectives, the roles and responsibilities for quality activities, the quality tools and techniques to be used, the approach to quality control and quality assurance, and the non-conformance procedures.
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 Quality Management Plan also defines the quality metrics — the specific, measurable indicators that will be used to verify quality. Examples: defect density (defects per 1,000 lines of code), first-pass yield (percentage of items passing inspection on first attempt), on-time delivery rate, customer satisfaction score. Without defined metrics, quality becomes a subjective judgment rather than an objective measurement.
Inputs
Project Charter
Project Management Plan (Requirements, Risk, Stakeholder engagement)
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
Outputs
Quality Management Plan
Quality Metrics
Project Management Plan Updates
Project Documents Updates
8.2
Manage Quality
Executing Process Group · Translates the Quality Management Plan into executable quality activities; focuses on process quality
+
Manage Quality (previously called "Perform Quality Assurance" in earlier PMBOK editions) is the executing process that translates the Quality Management Plan into action. Where Plan Quality Management asks "what quality standards apply and how will we meet them?", Manage Quality asks "are our processes actually working as planned, and how do we continuously improve them?" The focus is on process quality — ensuring the project's work processes are producing outputs that meet quality requirements — rather than on inspecting individual deliverables (which is Control Quality's job).
Manage Quality uses quality audits as its primary investigative tool — structured, independent reviews of quality management activities to assess whether the project's quality processes are appropriate and effective. A quality audit may be internal or external, and it evaluates whether the processes defined in the Quality Management Plan are being followed, whether they are achieving the intended quality objectives, and whether improvements should be recommended.
Process analysis is another key technique — identifying opportunities to improve processes by eliminating waste, reducing variation, and removing non-value-adding steps. This connects directly to Lean principles and Six Sigma methodology. The output of process analysis is often a change request to improve a process that is producing defects or operating inefficiently.
Manage Quality also produces the Quality Report — a consolidated view of quality management activities, quality audit findings, issues encountered, non-conformances identified, and recommended corrective actions — which feeds into Control Quality and broader project decision-making.
Monitoring & Controlling Process Group · Monitors and records results of quality activities; identifies defects and drives corrections
+
Control Quality is the process of monitoring and recording the results of executing quality management activities to assess performance and recommend necessary changes. While Manage Quality is concerned with processes, Control Quality is concerned with deliverables — inspecting, testing and measuring specific outputs to confirm they meet the quality requirements defined in the Quality Management Plan. This is the inspection-side of quality management.
Control Quality uses the seven basic quality tools (detailed in the next section) to analyse quality data, identify defect patterns, and determine root causes of non-conformances. It produces Quality Control Measurements — documented results of Control Quality activities — which feed back into Manage Quality as inputs for process improvement analysis.
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).
Inputs
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
Tools & Techniques
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
Outputs
Quality Control Measurements
Verified Deliverables
Work Performance Information
Change Requests
Project Management Plan Updates
Project Documents Updates
Cost of Quality
The Cost of Quality Framework
The Cost of Quality (CoQ) framework categorises all quality-related costs into two buckets: the cost of conformance (money spent to prevent defects and ensure quality) and the cost of non-conformance (money spent because quality was not achieved). Understanding this framework is essential for making the business case for quality investment — and for the PMP exam, where it is regularly tested.
Cost of Quality — Complete Framework
✅ Cost of Conformance (Good Money)
Prevention Costs — to avoid failures
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
Appraisal Costs — to assess quality
Testing (unit, integration, system, acceptance)
Inspections and audits
Destructive testing and sampling
Quality measurements and data collection
Supplier audits
❌ Cost of Non-Conformance (Bad Money)
Internal Failure Costs — found before delivery
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
External Failure Costs — found after delivery
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 fundamental principle: External failure costs are typically 10–100× more expensive than prevention costs. A defect that costs £50 to prevent in design costs £500 to fix in testing and £5,000+ to fix in production — and has incalculable reputational cost if it reaches a customer. Every pound spent on prevention and appraisal reduces a disproportionately larger amount of non-conformance cost. This is the business case for investing in quality upfront rather than inspecting quality in at the end.
The Seven Quality Tools
The Seven Basic Quality Tools
PMBOK identifies seven basic quality tools — sometimes called the "7 QC tools" from their origins in Japanese quality management. Each addresses a specific type of quality problem analysis. Together they provide a complete toolkit for identifying, analysing and resolving quality issues.
🐟Cause-and-Effect Diagram (Fishbone / Ishikawa)
A structured brainstorming tool that maps potential causes of a quality problem (the effect) in a visual fishbone structure. Causes are typically organised into categories — in manufacturing: Machine, Method, Material, Measurement, Man, Environment (the 6Ms). In software/services: People, Process, Technology, Environment, Management. The diagram forces systematic exploration of all potential root causes rather than jumping to the most obvious one.
Root cause analysis of defects and process failures
📊Control Chart (Run Chart)
A time-series chart that plots process measurement data against statistically calculated Upper Control Limit (UCL) and Lower Control Limit (LCL) — typically set at ±3 standard deviations from the mean. Data points within control limits indicate a stable, predictable process. Data points outside control limits, or non-random patterns within limits (7 consecutive points on one side of the mean = "Rule of 7"), indicate assignable causes that must be investigated. The control chart distinguishes between common cause variation (inherent, random) and special cause variation (assignable, correctable).
Monitoring process stability over time; identifying when intervention is needed
📈Flowchart (Process Map)
A visual representation of a process showing the sequence of steps, decision points, inputs and outputs. Flowcharts make process logic visible — enabling the team to identify where defects are most likely to be introduced, where process steps are redundant or missing, and where quality control checkpoints should be positioned. In quality management, flowcharts are used both for process design (Plan Quality Management) and process analysis (Manage Quality — identifying waste and improvement opportunities).
Process design, waste identification, quality checkpoint placement
📋Histogram
A bar chart that shows the frequency distribution of a dataset — how often values fall within defined intervals. In quality management, histograms reveal whether a process output is centred on the target, how much variation exists, whether the distribution is normal, and whether output is skewed toward the upper or lower specification limits. A histogram can reveal that a process is producing output that is statistically within specification on average but with a distribution that will regularly breach the upper limit.
Analysing the distribution and variation of process outputs
📉Pareto Chart (80/20 Rule)
A bar chart that ranks defect types or causes by frequency (or cost) in descending order, with a cumulative percentage line overlaid. Based on Vilfredo Pareto's observation that roughly 80% of effects come from 20% of causes. In quality management, the Pareto chart tells the quality team: which defect types account for the majority of failures, and therefore where to focus corrective action for maximum impact. Fixing the top three defect categories on a Pareto chart will typically address more than half of all defects.
Prioritising which defect categories to address first for maximum impact
🔵Scatter Diagram (Correlation Chart)
A two-dimensional chart that plots pairs of data values to reveal whether a relationship (correlation) exists between two variables. In quality management, scatter diagrams test hypotheses like "does higher ambient temperature correlate with more defects?" or "does longer test duration correlate with fewer escaped defects?" A positive correlation (data points trending upward from left to right) suggests a relationship that may indicate a cause-and-effect connection — though correlation is not causation and further analysis is needed to confirm.
Testing hypotheses about relationships between process variables and quality outcomes
✅Checklist (Check Sheet)
A structured data collection tool used to systematically gather and organise data. In quality management, checklists serve two purposes: as a verification checklist (ensuring all required steps have been completed before a deliverable is approved) and as a check sheet (a tally sheet that records how often each defect type occurs during a defined observation period). Check sheets feed directly into Pareto analysis — the frequency tallies become the data for the Pareto chart's defect ranking.
Verifying completion of required steps; collecting defect frequency data
Continuous Improvement
Continuous Improvement Models in Project Quality Management
Quality Improvement Frameworks — Referenced in PMBOK
PDCA — Plan-Do-Check-Act (Deming Cycle)
The foundational continuous improvement loop. Plan: identify the problem and design the improvement. Do: implement the solution on a small scale. Check: measure whether the improvement achieved the desired result. Act: standardise the successful change and scale it. In project quality management, PDCA operates at the process level — each cycle improves a specific process. PMBOK's Manage Quality process is essentially an application of PDCA to project quality management processes.
Six Sigma — DMAIC and DMADV
Six Sigma targets a process defect rate below 3.4 defects per million opportunities (6σ quality level). DMAIC (Define, Measure, Analyse, Improve, Control) is used to improve existing processes. DMADV (Define, Measure, Analyse, Design, Verify) is used to design new processes. Both are heavily data-driven and use statistical analysis to identify and eliminate root causes of variation. Relevant in quality-critical industries (manufacturing, healthcare, finance) where near-zero defect rates are achievable and required.
Lean — Eliminate Waste
Lean focuses on maximising customer value by eliminating the eight types of waste (TIMWOODS: Transport, Inventory, Motion, Waiting, Overproduction, Over-processing, Defects, Skills underutilisation). In project quality management, Lean thinking challenges PMs to question whether every quality activity adds value or whether it is bureaucratic overhead. Value stream mapping (a Lean tool) visualises the flow of work and identifies waste — including quality waste such as excessive inspection that should be replaced by better process design.
Total Quality Management (TQM)
TQM is an organisation-wide philosophy that makes quality the responsibility of every person, at every level, in every function — not just the quality department. W. Edwards Deming and Joseph Juran are the primary architects of TQM. Key TQM principles: customer focus, continuous improvement, employee involvement, fact-based decision making, and process approach. TQM is less a specific methodology than a cultural orientation toward quality that underpins all modern quality management frameworks, including PMBOK's approach.
Prevention vs Inspection
Prevention vs Inspection — The Right Balance
🛡️ Prevention (Manage Quality focus)
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 (Control Quality focus)
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.
Interrelation to Other Knowledge Areas
How Quality Management Connects to Every Other Knowledge Area
🔗KA01 — Integration Management
The Quality Management Plan is a subsidiary component of the Project Management Plan, governed by Integration Management. All quality-related change requests must pass through integrated change control. When Control Quality identifies a systemic defect requiring a process change, the corrective action is implemented via a change request reviewed by the project board. The direct and manage project work process generates the deliverables that Control Quality then inspects. Non-conformances identified in quality audits (Manage Quality) may trigger exceptions at stage boundary reviews.
📐KA02 — Scope Management
Quality and scope are definitionally intertwined. Requirements documents define what the deliverable must do; quality standards define how well it must do it. The acceptance criteria within the scope definition become the verification criteria for Control Quality. Verified deliverables (the output of Control Quality) flow into Validate Scope for formal customer acceptance. A scope change that adds new features must be accompanied by updated quality requirements — the new features need quality specifications just as the original scope did. Scope creep without quality planning creates deliverables with undefined quality standards.
📅KA03 — Schedule Management
Schedule pressure is the primary driver of quality shortcuts. When the critical path is compressed, testing and review activities are the first to be shortened or skipped — because their cost is visible and their value is perceived as optional. Quality activities must be explicitly scheduled as activities in the project network with realistic durations — not appended as afterthoughts. Rework resulting from poor quality (defects found late) causes more schedule disruption than the time "saved" by skipping quality activities. Fast-tracking (overlapping sequential activities) increases rework risk — a specific quality risk to be managed.
💰KA04 — Cost Management
The Cost of Quality framework directly bridges these two knowledge areas. Prevention and appraisal costs are estimated and budgeted in Estimate Costs as legitimate project cost elements. Non-conformance costs (rework, scrap, warranty) represent unplanned cost that damages CPI. The business case for quality investment is a cost management argument: preventing defects costs less than finding and fixing them. Quality-related change requests (rework, corrective action) require cost impact assessment before approval. A project with poor quality management often has a CPI below 1.0 — not because of poor scheduling but because of unplanned rework spending.
👥KA06 — Resource Management
Quality management requires skilled resources with the right expertise. Team training (a prevention cost) is both a Resource Management and Quality Management activity. Resource skill gaps directly cause quality defects — an undertrained developer introduces bugs; an inexperienced procurement officer accepts non-conforming supplier deliverables. Quality audits (Manage Quality) assess whether resources are following defined quality processes. Where they are not, training needs identified in the audit feed back into Resource Management's team development activities.
⚠️KA08 — Risk Management
Quality failures are risk events. Quality risks — the risk that a deliverable will fail to meet specification — belong in the Risk Register alongside schedule and cost risks. Risk responses to quality risks include prevention activities (avoid the defect), quality gates (reduce the impact by catching defects early), and contingency reserves for rework (accept with a cost buffer). The relationship flows both ways: poor risk management (unidentified or unmitigated risks materialising) typically causes quality impacts as teams scramble to recover, cutting corners on quality to restore schedule.
📣KA07 — Communications Management
Quality reports, audit findings and non-conformance notices are formal communications that must be managed under the Communications Management Plan. Stakeholders have different quality reporting needs — a technical team needs defect density data by component; a steering group needs a red/amber/green quality health summary with trend direction; a customer needs acceptance test results and sign-off documentation. Quality metrics must be communicated clearly to be actionable. Ambiguous quality reporting — where it is unclear whether a metric represents a pass or fail — is itself a quality failure in the communication process.
🛒KA09 — Procurement Management
Supplier and contractor quality is an extension of project quality management. Procurement contracts must include quality requirements, acceptance criteria and audit rights — otherwise the PM has no formal mechanism to enforce quality standards on external suppliers. Supplier qualification (a prevention cost) reduces the probability of non-conforming deliverables. Incoming inspection of supplier deliverables is an appraisal cost. When a supplier delivers non-conforming work, the consequences — rework, replacement, delay — flow directly into the project's cost and schedule performance. Quality management must explicitly extend to the supply chain, not just internal delivery teams.
Agile and Hybrid Approaches
Quality Management in Agile, Waterfall and Hybrid Environments
🏛️ Quality Management in Waterfall
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.
🔄 Quality Management in Agile
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
Hybrid environments maintain formal quality governance (quality standards, audit rights, stage gate quality reviews) at the programme level, while delivery teams apply Agile quality practices within sprints. The Definition of Done serves as the sprint-level quality gate; the stage boundary review serves as the programme-level quality gate. Quality metrics are reported in sprint reviews (velocity-normalised defect rates, test pass rates) and aggregated into the formal quality report for stage boundary governance.
Exam Tips
Quality Management — 7 Exam Tips for PMP and APM PMQ
1
Quality vs grade: low grade is acceptable; low quality never is. The PMP exam frequently presents scenarios where a product is described as basic or inexpensive and asks whether this is a quality problem. If the product meets its specified requirements, it is not a quality problem regardless of grade. A budget product that fails its requirements is low quality — always a problem.
2
Prevention is preferred over inspection — always. Any exam question that asks the best approach to quality will favour prevention activities (process improvement, training, clear requirements) over inspection activities (testing after the fact). Prevention eliminates defects; inspection only finds them. The cost rationale supports this: prevention is always cheaper per defect avoided than inspection per defect found.
3
Know the difference between Manage Quality and Control Quality. Manage Quality = process-focused, executing process group, quality assurance, proactive improvement. Control Quality = deliverable-focused, monitoring and controlling, inspection and testing, reactive detection. Manage Quality asks "are our processes working?"; Control Quality asks "does this deliverable meet requirements?" The exam tests this distinction frequently.
4
Control chart Rule of 7 — know it cold. Seven or more consecutive data points on one side of the mean (even if all within control limits) signals an out-of-control process requiring investigation. This is called "Rule of 7" and is a specific PMP exam topic. A process can be statistically in control (within UCL/LCL) but still show this pattern — the pattern itself is the signal, not just the control limit breach.
5
Verified deliverables flow into Validate Scope — not the reverse. Control Quality (Quality Management) produces verified deliverables — deliverables confirmed to meet quality standards. These then go to Validate Scope (Scope Management) for formal customer acceptance. The sequence is: quality inspection → verified deliverable → customer acceptance → accepted deliverable. Many candidates confuse which process produces which output.
6
Know the CoQ categories for exam scenarios. Prevention costs (training, process design), appraisal costs (testing, inspection), internal failure costs (rework, scrap) and external failure costs (warranty, recalls). When a question asks about quality costs, categorise each item correctly. Prevention and appraisal = conformance costs. Internal and external failure = non-conformance costs.
7
Precision and accuracy are different. Accurate = close to the target value. Precise = consistent results (low variation), regardless of whether they are near the target. You can be precise without being accurate (consistently wrong), accurate without being precise (right on average but variable), or both. The exam distinguishes between a process needing recalibration (precise but inaccurate) vs process improvement (imprecise).
Use This Knowledge Area in Your PMP or APM PMQ Exam
Quality management processes, the Cost of Quality framework and the seven quality tools are examined in both the PMP and APM PMQ. The APM PMQ tests quality within its broader PM competency framework, including scope, requirements and configuration management.
The three PMBOK processes in Project Quality Management (Knowledge Area 8) are: (1) Plan Quality Management (Planning Process Group) — identifying quality requirements and standards applicable to the project, defining quality metrics, and documenting how quality will be achieved and verified. Its primary output is the Quality Management Plan. (2) Manage Quality (Executing Process Group) — translating the Quality Management Plan into executable quality activities, conducting quality audits, and continuously improving processes. Its primary outputs are the Quality Report and Test and Evaluation Documents. (3) Control Quality (Monitoring and Controlling Process Group) — inspecting, testing and measuring deliverables against quality requirements, recording results, and generating Verified Deliverables and Quality Control Measurements. The key distinction: Manage Quality focuses on process quality (proactive); Control Quality focuses on deliverable quality (reactive).
Quality is the degree to which a set of inherent characteristics fulfils requirements — a product is high quality if it consistently meets its specified requirements, regardless of how basic or advanced those requirements are. Grade is a category assigned to products with the same functional use but different technical characteristics — a budget product has low grade; a premium product has high grade. Low quality is always a problem — a product that fails to meet its requirements is not fit for purpose regardless of its intended grade level. Low grade is not inherently a problem — a low-grade product that consistently meets its specified requirements for a basic use case is a quality product. The classic example: a basic hotel room that is clean, functional and consistently matches its description is high quality at low grade. An expensive hotel room that consistently fails to deliver the experience its price implies is low quality at high grade.
The Cost of Quality (CoQ) framework categorises all quality-related project costs into two groups. Conformance costs are money spent to deliver quality: prevention costs (training, process design, quality planning, peer reviews) and appraisal costs (testing, inspection, audits, quality measurements). Non-conformance costs are money spent because quality was not achieved: internal failure costs (rework, scrap, retesting) found before delivery, and external failure costs (warranty claims, recalls, liability, customer complaints) found after delivery. The fundamental principle of CoQ is that conformance costs — particularly prevention costs — are significantly cheaper per defect avoided than non-conformance costs per defect fixed. A defect that costs £50 to prevent during design may cost £500 to fix in testing and £5,000+ to fix after delivery. This provides the financial justification for investing in quality activities upfront.
The seven basic quality tools (7 QC tools) are: (1) Cause-and-Effect Diagram (Fishbone/Ishikawa) — maps potential causes of a quality problem in categories to identify root causes; (2) Control Chart — plots process measurements over time against statistical control limits to distinguish common cause from special cause variation; (3) Flowchart — visualises a process to identify defect introduction points and improvement opportunities; (4) Histogram — shows the frequency distribution of process outputs to reveal variation patterns and specification compliance; (5) Pareto Chart — ranks defect types by frequency using the 80/20 principle to prioritise improvement efforts; (6) Scatter Diagram — plots two variables to test for correlation between a potential cause and a quality outcome; (7) Checklist/Check Sheet — a structured data collection tool used for systematic verification of completed steps or recording of defect frequencies. Together these tools cover the complete quality analysis cycle from data collection to root cause identification to improvement prioritisation.
In waterfall, quality management follows the three-process PMBOK model with formal quality gates at stage boundaries — quality requirements are defined upfront, quality assurance activities run throughout execution, and separate testing phases inspect deliverables at defined checkpoints. In Agile, quality is built in continuously rather than inspected at the end. The Definition of Done (DoD) serves as the sprint-level quality checklist — every user story must meet defined quality criteria before it is marked complete. Test-Driven Development (TDD) ensures tests are written before code, making quality requirements explicit from the start. Continuous integration with automated testing provides immediate quality feedback within hours of code being written, dramatically reducing the cost of defect discovery. Sprint retrospectives apply the PDCA continuous improvement cycle every sprint. The fundamental difference: waterfall separates quality into a distinct phase; Agile makes quality everyone's continuous responsibility throughout delivery.
The Rule of 7 (also called the run rule) is a control chart analysis rule that states: if seven or more consecutive data points appear on the same side of the mean (centre line), the process is considered out of statistical control and requires investigation — even if all data points remain within the Upper and Lower Control Limits. This is because the probability of seven consecutive points randomly falling on the same side of the mean by chance is less than 1% (0.5⁷ ≈ 0.78%), indicating that a non-random (assignable) cause is affecting the process. A process can pass the control limit test (no points outside UCL or LCL) yet still be identified as out of control by the Rule of 7. On the PMP exam, the Rule of 7 is a frequently tested concept — any question showing a control chart with seven consecutive points above or below the mean requires investigation and corrective action, regardless of whether those points are within control limits.