Quality Management
PMP PMP · Process
What quality means on the PMP exam
Quality, in PMI's definition, is the degree to which a set of inherent characteristics fulfills requirements. In plain language: a deliverable has quality when it does what it was supposed to do, to the standard that was agreed. The July 2026 ECO gives the Process domain one task here: plan and optimize quality of products and deliverables. The exam tests quality as a management discipline — planning for it, building it in, checking it, and improving it — and it consistently rewards prevention over inspection. Finding a defect after the work is done is expensive; preventing it from happening in the first place is cheap. That single idea explains most of the exam's quality questions.
Two distinctions run through the whole topic. The first is between quality and grade. Quality is fitness for purpose: does the deliverable meet its requirements? Grade is a category of features: a basic hotel room and a luxury suite are different grades, but both can be high quality if they deliver what they promise. Low grade is a design choice; low quality is a failure. The exam tests this with scenarios where a low-grade deliverable is perfectly acceptable — a simple internal tool does not need the features of a flagship product — and the correct answer recognizes that quality and grade are different things. The second distinction is between precision and accuracy. Precision is consistency: repeated measurements give the same result. Accuracy is closeness to the true value: the measurements are right. A process can be precise but inaccurate (consistently wrong), and the exam expects you to know that accuracy matters more.
Plan quality, manage quality, control quality
Quality management has three parts, and the exam tests the boundaries between them. Plan quality management identifies the quality requirements and standards for the project and its deliverables, and documents how the project will demonstrate compliance — in the quality management plan. Manage quality (quality assurance) is about the processes: it audits whether the project is following the right processes and standards, and it is where process improvement happens. Control quality is about the deliverables: it inspects and tests the actual outputs to verify that they meet the requirements. The exam's shorthand is: manage quality checks the process, control quality checks the product.
A question might describe a project manager reviewing whether the team is following the agreed testing procedure — that is manage quality. A question describing the team running tests on a finished component is control quality. A question describing the project manager defining acceptance criteria during planning is plan quality management. The three processes form a loop: plan what quality means, build the work using good processes, check the outputs, and feed what you learn back into the processes.
Cost of quality: prevention is cheaper than failure
The cost of quality (COQ) is the total cost of all efforts to achieve quality, and it has four categories. Prevention costs are spent to stop defects happening: training, process design, quality planning, and proper equipment. Appraisal costs are spent to check for defects: inspection, testing, and audits. Internal failure costs arise when defects are found before delivery: rework, scrap, and retesting. External failure costs arise when defects reach the customer: warranty claims, returns, lost business, and reputational damage. The exam's key insight is that prevention and appraisal (the cost of conformance) are almost always cheaper than failure (the cost of nonconformance) — and that external failure is the most expensive category of all, because it includes damage to the organization's reputation that no amount of rework can undo.
This is why the exam rewards answers that invest in prevention. A question might offer a choice between hiring an extra tester (appraisal), training the team in the new technology (prevention), and fixing defects after the customer reports them (external failure). Training — prevention — is usually the best answer, because it stops defects at the source. A question might also ask which cost of quality category a warranty claim falls into: external failure. Or what rework costs are: internal failure. These are straightforward recall questions, and they are easy marks if you know the four categories.
Quality tools the exam tests
The exam expects familiarity with the seven basic quality tools, sometimes called the seven tools of quality. The cause-and-effect (fishbone or Ishikawa) diagram organizes possible causes of a problem into categories to find the root cause. The flowchart maps a process step by step to find where defects enter. The check sheet collects data in a structured way. The Pareto chart ranks causes by frequency, based on the Pareto principle that roughly 80% of problems come from 20% of causes — fix the vital few first. The histogram shows the distribution of data. The control chart plots process performance over time against control limits, to distinguish normal variation from a process that is out of control. The scatter diagram shows whether two variables are related. The exam tests these mainly by scenario: a question describing a team trying to find which defect type causes most failures is asking for a Pareto chart; a question about finding the root cause of a problem is asking for a fishbone diagram; a question about whether a process is stable is asking for a control chart.
Two more ideas complete the picture. Statistical sampling tests a subset of outputs rather than every one, when full inspection is impractical. Design of experiments varies factors systematically to find which ones affect quality. And the exam tests the difference between attribute sampling (pass/fail — the deliverable either meets the standard or it does not) and variable sampling (measured on a scale — how close to the standard is it). Attribute sampling is simpler; variable sampling gives more information.
Continuous improvement and modern quality thinking
Quality management on the PMP exam is not just about inspection; it is about continuous improvement. The plan-do-check-act (PDCA) cycle — plan a change, try it, check the results, and act on what you learn — is the basic improvement loop, and it appears in agile retrospectives as well as in formal quality programs. Kaizen is the philosophy of small, continuous improvements made by everyone, rather than occasional large changes imposed from above. Six Sigma is a structured method for reducing defects, aiming for no more than 3.4 defects per million opportunities. Total Quality Management (TQM) is the organization-wide commitment to quality in everything. The exam does not test these in depth, but it does expect you to recognize them and to know that continuous improvement is a PMI value: the correct answer in a quality scenario is often the one that improves the process, not the one that inspects harder.
In agile projects, quality is built in rather than inspected in. Practices such as test-driven development (writing the test before the code), continuous integration (merging and testing code frequently), pair programming, and the definition of done (the agreed standard a piece of work must meet before it counts as complete) all serve the same purpose: defects are caught within hours, not weeks. The exam rewards this approach: an option that builds quality into the process usually beats an option that adds more inspection at the end.
Exam mindset for quality
For quality questions, the decision tree is simple. Prevention beats inspection, and inspection beats failure. Manage quality is about the process; control quality is about the product. When a question asks for a tool, match the tool to the task: Pareto for ranking causes, fishbone for root cause, control chart for stability. And when a question offers a choice between improving the process and inspecting the output harder, choose the process improvement — that is where quality is actually created.
Exam traps to watch for
- Confusing manage quality (auditing the process) with control quality (inspecting the deliverable). The exam tests this boundary constantly.
- Choosing inspection over prevention. Finding defects is more expensive than preventing them — the prevention option is usually the right answer.
- Confusing quality with grade. A low-grade deliverable can be high quality; grade is a design choice, quality is fitness for purpose.
- Treating a control chart question as a Pareto question. Control charts show whether a process is stable over time; Pareto charts rank causes by frequency.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.A project team keeps finding the same type of defect in testing. The project manager wants to identify the root cause of the defect. Which quality tool should be used?
Explanation: A cause-and-effect (fishbone or Ishikawa) diagram is the tool for root-cause analysis: it organizes possible causes of a problem into categories (people, process, materials, environment, and so on) so the team can work through them systematically and find the underlying cause. Option C is wrong because a Pareto chart ranks defect types by frequency — useful for deciding which defect to fix first, but it does not find the cause of a specific defect. Option A is wrong because a control chart shows whether a process is stable over time, not why a defect occurs. Option D is wrong because a scatter diagram shows whether two variables are related, which is a different question from root cause.
Exam objective: PMP ECO Task: Plan and optimize quality of products/deliverables (Process)
Q2.A project manager is deciding between two quality investments: training the team in the new testing framework, or hiring an additional inspector to check finished work. Which is the BETTER investment, and why?
Explanation: Training is a prevention cost: it stops defects from being created in the first place. Inspection is an appraisal cost: it finds defects after they exist, and each defect found still has to be fixed (an internal failure cost). The cost-of-quality principle is that prevention is cheaper than appraisal and far cheaper than failure, so the prevention investment is the better one. Option B is wrong because inspection, while useful, is a more expensive way to achieve quality than prevention. Option D is wrong because the time spent on training is repaid many times over by the defects it prevents. Option C is wrong because quality investment does reduce overall cost — the cost of preventing a defect is a fraction of the cost of fixing it after delivery.
Exam objective: PMP ECO Task: Plan and optimize quality of products/deliverables (Process)
Q3.A customer reports a serious defect in a delivered product, and the organization must issue a recall and pay warranty claims. Which cost-of-quality category do the recall and warranty costs fall into?
Explanation: External failure costs arise when defects reach the customer: warranty claims, recalls, returns, and the reputational damage that follows. They are the most expensive cost-of-quality category. Option C is wrong because prevention costs (training, process design) are spent before defects happen. Option A is wrong because appraisal costs (inspection, testing) are spent checking for defects. Option D is wrong because internal failure costs (rework, scrap) arise when defects are found before delivery — here the defect reached the customer, so the failure is external.
Exam objective: PMP ECO Task: Plan and optimize quality of products/deliverables (Process)
Q4.A project manager audits the team's development process and finds that the team is not following the agreed code-review procedure. Which quality process is the project manager performing?
Explanation: Manage quality (quality assurance) is about the process: auditing whether the project is following the right processes and standards. Checking whether the team follows the agreed code-review procedure is a process audit, so it is manage quality. Option B is wrong because control quality inspects deliverables (the product), not processes — testing the code itself would be control quality. Option A is wrong because plan quality management happens during planning, when quality requirements and standards are defined. Option C is wrong because validate scope is the formal acceptance of completed deliverables by the customer, not a process audit.
Exam objective: PMP ECO Task: Plan and optimize quality of products/deliverables (Process)
Q5.A team has identified 20 different types of defects in a product. They want to focus their improvement effort on the defect types that cause the most problems. Which tool should they use?
Explanation: A Pareto chart ranks causes by frequency, based on the principle that roughly 80% of problems come from 20% of causes. It shows the team which defect types to fix first for the greatest impact. Option C is wrong because a flowchart maps process steps; it does not rank defect types. Option A is wrong because a control chart shows process stability over time, not the ranking of causes. Option B is wrong because a histogram shows the distribution of a single variable (such as defect size), not a ranked comparison of defect types.
Exam objective: PMP ECO Task: Plan and optimize quality of products/deliverables (Process)
Q6.A project is delivering a simple internal reporting tool. The tool has few features, but every feature works exactly as specified and the tool is reliable. How should the project manager describe the tool's quality and grade?
Explanation: Quality is fitness for purpose — does the deliverable meet its requirements? This tool does, so it is high quality. Grade is the category of features — this is a simple tool with few features, so it is low grade. Low grade is a legitimate design choice (the organization did not need a complex tool); low quality would be a failure. Option B confuses the two: few features mean low grade, not low quality. Option A is wrong because the tool is not high grade — it is deliberately simple. Option D is wrong on both counts: a simple tool can absolutely be high quality.
Exam objective: PMP ECO Task: Plan and optimize quality of products/deliverables (Process)
Q7.An agile team wants to reduce the number of defects reaching the sprint review. Which practice is MOST aligned with PMI's quality approach?
Explanation: Test-driven development (writing the test before the code) and continuous integration (merging and testing code frequently) build quality into the process: defects are caught within hours, when they are cheapest to fix. This is the agile expression of PMI's prevention-over-inspection principle. Option C is wrong because a separate testing phase at the end of the sprint is a return to waterfall thinking — it delays defect discovery and creates a testing bottleneck. Option A is wrong because reducing scope to reduce defects treats the symptom, not the cause, and it reduces the value delivered. Option D is wrong because the product owner is not the team's tester; quality is the whole team's responsibility, and pushing testing onto the product owner delays feedback.
Exam objective: PMP ECO Task: Plan and optimize quality of products/deliverables (Process)
Q8.A control chart shows that a manufacturing process has produced seven consecutive measurements on the same side of the center line, all within the control limits. What does this indicate?
Explanation: Seven consecutive points on the same side of the center line is a recognized rule-of-seven pattern: it suggests the process is drifting (a systematic shift) even though no single measurement has crossed a control limit. The correct response is to investigate the cause before the drift produces defects. Option D is wrong because the pattern is a warning sign, not a sign of stability — a stable process varies randomly on both sides of the center line. Option A is wrong because the control limits are not the problem; widening them would hide the drift. Option B is wrong because the output is still within limits — stopping the process is an overreaction to a warning sign that calls for investigation, not shutdown.
Exam objective: PMP ECO Task: Plan and optimize quality of products/deliverables (Process)