Quality management is the set of activities you perform to ensure that the project's deliverables meet the needs and expectations of the stakeholders. It matters for the PMP exam because projects often fail not because they were late or over budget, but because the end product was unusable or had too many defects. Learning this concept helps you as a project manager to build customer satisfaction into the project from the start, rather than fixing problems after the work is done.
Jump to a section
A simple way to picture Quality Management and Improvement
A bustling kitchen on a Friday evening, with the host preparing a multi-course dinner for twelve guests. The host has a recipe book (the plan) and a timeline for when each dish should be ready.
The host does not just cook and hope for the best. They taste the soup as it simmers to check the seasoning (quality control, inspecting the product). When the sauce is too thin, they add a cornstarch slurry to fix it on the spot (corrective action). They also check that the oven temperature is accurate before roasting the chicken, ensuring the process itself is sound (quality assurance, checking the process). To decide what to cook, the host earlier asked guests about dietary restrictions, like gluten-free or nut allergies (understanding stakeholder requirements for quality). If a guest cannot eat dairy, the host chooses a different dessert recipe (managing quality by adjusting the plan upfront). After the meal, the host notes that the starter took too long to plate, so for the next party they will prep the ingredients earlier (continuous improvement). All of this – tasting, adjusting the recipe, checking the equipment, and gathering feedback – is quality management. It ensures every guest enjoys a safe, delicious experience, not just a meal that happens to be served on time.
Quality management in a project context is about making sure that what you build is good enough for the people who will use it. It is not about making something perfect or fancy; it is about making something that works correctly and meets the agreed-upon requirements. In IT projects, this often means software that does not crash, a website that loads quickly, or a data centre that stays cool.
The three main processes in project quality management are: plan quality management, manage quality, and control quality. First, you plan. This means determining what quality standards are relevant to your project and how you will satisfy them. You write down which metrics you will use, such as response time for a website or defect density for code, and you decide which tools you will use to check them, such as peer reviews or testing software. This planning happens early, but you update it as the project goes on.
Second, you manage quality. This is an ongoing activity during the project execution. Here, you turn the quality plan into real actions. You audit the project activities to make sure they follow the plan. You also perform process analysis to identify improvements. A tool often used here is a 'quality audit' – an independent review to confirm that the project is following the organisation's quality policies. Another tool is a 'process analysis', where you examine a specific step in your workflow and find ways to make it more efficient or less error-prone.
Third, you control quality. This happens during the project work and also at the end of a phase. Control quality is about monitoring specific project results to determine if they comply with the relevant quality standards. You inspect the actual output – the software build, the server configuration, the user manual – and compare it to the requirements. If you find a defect, you document it and try to fix it. The key difference is: manage quality focuses on the process, while control quality focuses on the product.
There are several important terms and concepts you must know for the PMP exam. 'Cost of quality' means the total money spent on quality-related activities. This includes two categories: the cost of conformance (money spent to prevent problems and to test for them) and the cost of non-conformance (money spent because of failures, such as rework, lost customers, or warranty claims). A basic principle is that prevention is cheaper than inspection, and inspection is cheaper than fixing something after it has been delivered.
Precision and accuracy are two related but different concepts. Precision means your measurements are consistent and repeatable; if you weigh the same item ten times and get 1.0 kg each time, your scale is precise. Accuracy means your measurement is close to the true value; if the item truly weighs 1.1 kg and your scale shows 1.1 kg, that is accurate. It is possible to be precise but not accurate (consistently wrong) or accurate but not precise (sometimes right by luck). You need both.
There are several tools and techniques you will see on the exam. One group is called the 'seven basic quality tools': cause-and-effect diagrams (fishbone diagrams to find root causes of problems), flowcharts (to understand a process), check sheets (data collection forms), Pareto diagrams (bar charts showing which problems occur most often), histograms (frequency distributions), control charts (to see if a process is stable over time), and scatter diagrams (to look for relationships between two variables). Another group is 'benchmarking', which means comparing your project's practices or products to those of other projects or organisations to generate improvement ideas.
Continuous improvement is a core idea. It is often embodied in the 'Plan-Do-Check-Act' (PDCA) cycle. Plan: define the problem and propose a solution. Do: implement the solution on a small scale. Check: measure the results. Act: if it worked, standardise it; if not, start the cycle again. This cycle is repeated throughout the project to drive incremental gains.
Finally, remember that quality is not an afterthought; it is planned from the start. The project manager is responsible for balancing quality with cost, schedule, and scope. Cutting corners on quality to save money or time almost always leads to more expensive rework later. The PMP exam will test your understanding that the project manager must manage quality proactively, involve the team, and make decisions based on data, not hunches.
Define Quality Objectives
Identify which quality standards and requirements are relevant to the project. This includes discussing with stakeholders what 'good enough' looks like (e.g., response time, defect rate). Document these in the quality management plan.
Plan Quality Activities
Decide which tools and techniques you will use to achieve those objectives. Choose metrics (like number of defects per module), select testing methods (automated tests, peer reviews), and schedule quality audits. This plan is a component of the project management plan.
Perform Quality Assurance (Manage Quality)
During execution, conduct process audits to ensure the team is following the quality plan. Analyse the processes themselves, not just the outputs. Use tools like process analysis and quality audits to identify improvements. This step focuses on the method of work.
Perform Quality Control (Control Quality)
Inspect the actual deliverables (e.g., a software build, a document) to see if they meet the specified quality standards. Use tools like control charts, Pareto diagrams, and inspection checklists. Record defects, take corrective actions, and verify fixes.
Review and Improve
Continuously analyse the data from quality control and audits. Use the Plan-Do-Check-Act cycle to implement process improvements. For example, if a high number of defects come from unclear requirements, improve the requirements gathering process for future projects.
Consider an IT project to build a mobile banking application for a large retail bank. The project manager, Priya, is responsible for ensuring the app is reliable and secure before it is released to customers.
During the planning phase, Priya works with her team to define quality standards. They decide that the app must load the account balance screen in under two seconds. They also decide that there must be zero security vulnerabilities in the code. They write these into the project's quality management plan. They choose to use automated testing tools, peer code reviews, and a dedicated security audit as their primary quality activities.
During the execution phase, the team manages quality. Every Friday, a quality audit is conducted by a senior developer who is not on the project. This person checks that the team is actually following the coding standards they agreed on. They notice that developers are skipping some unit tests because they are behind schedule. Priya uses this finding to discuss with the team and adjust the timeline, rather than allowing them to skip testing. This is managing quality – ensuring the process is followed.
Simultaneously, the team is doing control quality work. Every time a new feature is completed, the code is run through an automated test suite. The results are recorded in a control chart that shows the number of defects per module. Priya reviews this chart weekly. If she sees that one particular module has a spike in defects (say, more than 5 per 1000 lines of code), she asks the team to investigate and fix that module before building more features on top of it. They also perform user acceptance testing (UAT) with a small group of bank employees, collecting feedback on the app's usability.
Later, a security audit discovers that a sensitive customer data field is being logged in plain text. This is a major quality failure. The team immediately stops work on new features and fixes the logging issue (corrective action). They also update their coding guidelines to prevent the same mistake in the future (preventive action). This is an example of the cost of non-conformance – the time spend fixing the defect is far higher than if they had written the code correctly the first time.
After the app launches, the team conducts a retrospective. They analyse the data: what caused the most defects? They find that complex features with unclear requirements had the highest defect rates. They decide that for the next project, they will invest more time in writing clear, detailed requirements (process improvement). This is the 'Plan-Do-Check-Act' cycle in action.
Priya's day-to-day activities include:
Reviewing quality metrics from the testing team every morning.
Participating in walkthroughs of new feature designs to catch issues early.
Leading a weekly meeting focused on process improvement ideas from the team.
Checking the control chart for test results and deciding on corrective actions.
Updating the quality management plan when new risks are identified.
The result of Priya's diligence is a mobile app that passes its security audit, loads quickly, and receives positive customer feedback. The project is considered a success not just because it was on time and on budget, but because it delivered a product the bank's customers actually trusted and enjoyed using.
The PMP exam tests your understanding of quality management in three distinct areas: planning, managing, and controlling. Expect around 10-15 questions on this topic across the exam. The exam is heavy on terminology and the distinction between related concepts.
You will see questions that ask you to identify which process you are in (plan quality management, manage quality, or control quality). The key is to identify the trigger. If the question describes a team doing an audit of the process, it is 'manage quality' (or 'perform quality assurance' in older PMBOK terms). If the question describes inspecting a product or measuring a result, it is 'control quality'. If the question is about selecting metrics or writing a plan, it is 'plan quality management'. A common trap is confusing 'manage quality' with 'control quality'. Remember: manage quality is about the process; control quality is about the product.
Another major theme is the cost of quality. The exam loves to ask which type of cost is the most expensive. The order is: prevention (lowest cost), appraisal (inspection, moderate cost), internal failure (found before delivery), and external failure (found by the customer, highest cost). If a question asks 'where should the project manager invest to reduce the overall cost of quality?', the answer is nearly always prevention (e.g., training, better design, proper tools).
Expect a question that gives you a scenario with a control chart. They will ask what it means when a data point is outside the upper or lower control limit. The correct answer is that the process is 'out of control' and requires investigation and corrective action. Another common trap is misreading a 'rule of seven' (seven consecutive points on one side of the mean) as a problem even if none are out of limits. That indicates a non-random pattern and the process is out of control.
You must know the seven basic quality tools and what each is used for. The exam rarely asks you to name all seven, but it will describe a scenario and ask which tool to use. For example, if a scenario describes a list of defects and you want to focus on the most common ones, use a Pareto diagram. If you want to understand the cause of a specific problem, use a cause-and-effect diagram.
Key definitions to memorise:
Quality: the degree to which a set of inherent characteristics fulfils requirements.
Grade: a category assigned to products having the same functional use but different technical characteristics. A low-grade product can still be high quality if it meets its specifications. A high-grade product can be low quality if it is full of defects. This is a classic exam trap.
Precision vs. accuracy: as defined above.
Continuous improvement: the ongoing effort to improve products, services, or processes. Often linked to PDCA.
Benchmarking: comparing practices or products to industry leaders.
Question types you will see:
Scenario-based: 'You are the PM of a software project. During a sprint review, the customer says the interface is too slow. The team measures the response time and finds it exceeds the limit. Which process are they in?'
Definition-based: 'What is the difference between quality and grade?'
Tool-based: 'A PM wants to identify the root cause of a recurring defect. Which tool should they use?'
Cost of quality: 'The project team decides to invest in automated testing. This is an example of which cost of quality category?'
Control chart interpretation: 'On a control chart, seven consecutive data points fall above the mean but within the control limits. What does this indicate?' The answer: the process is out of control due to the rule of seven.
Traps to watch for:
Choosing 'quality assurance' (an older term) when the answer should be 'manage quality'. The current PMBOK (7th edition) uses 'manage quality'. The exam is aligned with this. However, many questions still use 'quality assurance' interchangeably. If you see 'quality assurance', it is equivalent to 'manage quality' in the exam context.
Confusing 'control quality' with 'manage quality' because both involve testing. Remember: control quality inspects the product; manage quality audits the process.
Assuming that 'high quality' means 'expensive'. A low-cost product can be high quality if it meets its requirements.
Thinking that quality is the sole responsibility of a separate QA team. The PMBOK states that quality is everyone's responsibility, but the project manager is ultimately accountable.
Quality management is composed of three processes: plan quality management, manage quality (process-focused), and control quality (product-focused).
The cost of quality includes the cost of conformance (prevention and appraisal) and the cost of non-conformance (internal and external failures).
Preventing defects is always cheaper than finding and fixing them after the product is built.
A process is considered 'out of control' if a data point falls outside the control limits, OR if seven consecutive data points fall on the same side of the mean (the rule of seven).
Quality is defined as the degree to which a set of inherent characteristics fulfils requirements; grade is a different concept and low grade does not mean low quality.
Continuous improvement is driven by the Plan-Do-Check-Act (PDCA) cycle and is a principle of quality management.
The seven basic quality tools include cause-and-effect diagrams, flowcharts, check sheets, Pareto diagrams, histograms, control charts, and scatter diagrams.
Benchmarking involves comparing your project's practices or products to those of other projects to identify improvement opportunities.
These come up on the exam all the time. Here's how to tell them apart.
Quality
The degree to which requirements are fulfilled.
A low-quality product has many defects or fails to meet requirements.
A product can be low quality even if it is high grade (e.g., a luxury phone that crashes).
Grade
A category assigned to products with different technical features.
A low-grade product has basic features (e.g., economy class).
A product can be high quality while being low grade (e.g., a reliable basic phone).
Manage Quality (Quality Assurance)
Focused on the process: are we following the right procedures?
Uses tools like process audits and process analysis.
Performed throughout the project execution.
Control Quality
Focused on the product: does the deliverable meet specifications?
Uses tools like inspection, control charts, and Pareto diagrams.
Performed at the end of phases and on specific work products.
Prevention Cost
Money spent to avoid defects from occurring in the first place.
Examples: training, proper tools, clear requirements, design reviews.
Considered the most cost-effective type of investment.
Appraisal Cost
Money spent to inspect and detect defects after they have been made.
Examples: testing, inspections, product audits.
More expensive than prevention but still cheaper than failure costs.
Internal Failure Cost
Costs incurred when a defect is found before the product reaches the customer.
Examples: rework, scrap, retesting, defect tracking.
Less damaging to reputation than external failures.
External Failure Cost
Costs incurred when a defect is found after the product reaches the customer.
Examples: warranty claims, customer complaints, product recalls, lost business.
The most expensive category; can harm brand reputation.
Precision
Consistency and repeatability of measurements.
Example: a scale that always reads 1.0 kg for a 1.0 kg weight is precise.
Precision alone does not guarantee correctness.
Accuracy
Closeness of a measurement to the true or target value.
Example: a scale that reads 1.1 kg for a 1.1 kg weight is accurate.
An accurate measurement may not be consistent every time.
Plan-Do-Check-Act (PDCA)
A four-step cycle for continuous improvement.
Plan: define a problem and propose a solution.
Do: implement the solution; Check: measure results; Act: standardise or restart.
Six Sigma (DMAIC)
A five-phase methodology for process improvement (Define, Measure, Analyse, Improve, Control).
Used to reduce variation and defects in processes.
More data-driven and structured than PDCA; often used in manufacturing.
Mistake
Quality management is only about testing the final product at the end of the project.
Correct
Quality management includes planning, process audits, and continuous improvement throughout the project, not just final inspection.
Many beginners come from a background where 'quality' means 'checking the final output'. In project management, the emphasis is on prevention and process improvement, which happen before and during the work.
Mistake
A low-budget project cannot have high quality because quality costs extra money.
Correct
Quality is about meeting requirements, not about adding expensive features. A simple, cheap product can be of high quality if it functions correctly and satisfies the customer's needs.
People often confuse quality with grade or luxury. The exam defines quality as conformance to requirements, not as 'fanciness'.
Mistake
If a project is behind schedule, the project manager should reduce quality activities to catch up on time.
Correct
Reducing quality activities (like testing or reviews) usually leads to more defects, rework, and delays later, making the schedule worse. The correct response is to analyse the root cause of the delay and find a more efficient process.
Pressure to deliver often tempts managers to skip quality steps. The PMP exam teaches that this is a false economy and a recipe for failure.
Mistake
The project manager is personally responsible for performing all quality checks.
Correct
The project manager is responsible for ensuring the quality activities happen, but the actual testing, inspections, and audits are performed by the project team or a dedicated quality function.
New project managers sometimes think they must do everything themselves. In reality, the PM is a facilitator and decision-maker, not a hands-on tester.
Mistake
Quality and grade are the same thing, just different words.
Correct
Quality is conformance to requirements (does it work as intended?). Grade is a category for products with different technical features (e.g., first class vs. economy seats). A low-grade product can be high quality.
The exam specifically tests this distinction because in everyday language the words are often used interchangeably. The PMBOK defines them separately.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Quality assurance (now called 'manage quality' in the PMBOK) focuses on the process: it audits the activities to ensure they are being done correctly. Quality control (called 'control quality') focuses on the product: it inspects the output to find defects. Think of it as: QA checks the recipe, QC tastes the soup.
You should know the names of the seven tools and, more importantly, what each one is used for. The exam will present scenarios and ask which tool to use. For example, a cause-and-effect diagram is for root cause analysis, and a Pareto chart is for prioritising problems.
Cost of quality is the total cost of all activities related to quality, including money spent on training and testing (conformance) and money lost due to rework and customer complaints (non-conformance). The key principle is that prevention is cheaper than failure.
Yes. Grade is a category for different levels of technical features (like economy vs. first class). Quality is about whether the product meets its specifications. A low-grade product (economy seat) can be high quality if it works correctly (seat is not broken, no defects).
The rule of seven states that if seven consecutive data points all fall on the same side of the mean (central line), the process is considered 'out of control' even if none of the points are outside the control limits. It indicates a non-random pattern that should be investigated.
Yes, the project manager is ultimately accountable for ensuring that quality management activities are planned and executed. However, the entire team is responsible for performing quality work. The PM does not personally test everything; they ensure the system is in place.
You've finished Quality Management and Improvement. Continue through the PMP study guide to build a complete picture of the exam.
Done with this chapter?