Control Quality

Control Quality

Introduction: Why This Matters

Producing deliverables is not enough. They must also meet defined quality requirements. The Control Quality process verifies that deliverables conform to specifications, standards, and customer expectations. While Manage Quality focuses on process assurance, Control Quality focuses on deliverable inspection and validation.

On the PMP exam, this process is often tested through situational questions about quality control tools, inspections, and differences between QA (process-focused) and QC (deliverable-focused). In practice, quality control prevents defective outputs from reaching customers, reducing rework and protecting stakeholder trust (Project Management Institute, 2021).

Purpose and Objectives

Primary Purpose: To monitor and record quality results to ensure deliverables meet requirements.

Key Objectives:

• Inspect deliverables for compliance with quality standards.
• Identify defects and nonconformities.
• Recommend corrective actions or rework.
• Verify that quality processes are producing acceptable results.
• Produce verified deliverables as inputs to Validate Scope.

Overview

In Control Quality, the project team tests and inspects actual deliverables, compares results to quality standards, and either accepts, rejects, or requests rework. It turns raw work performance data into meaningful quality information and verified deliverables that move on to validation and acceptance.

• Measure: Collect data on product performance and defects against defined metrics.
• Analyze: Use quality tools and charts to understand patterns, causes, and trends.
• Act: Approve, reject, or send deliverables for rework through change control.
• Feed back: Update plans, processes, and lessons learned to prevent future defects.

Characteristics

• Deliverable-focused: Concentrates on product outputs rather than process design.
• Data-driven: Relies on measurements, sampling, and statistical analysis.
• Iterative: Inspections and testing occur repeatedly across the life cycle.
• Compliance-oriented: Ensures regulatory, contractual, and internal standards are met.

Inputs, Tools & Techniques, Outputs (ITTOs)

Inputs

• Project management plan (quality management plan).
• Quality metrics.
• Work performance data.
• Deliverables (from execution).
• Approved change requests.
• Organizational process assets (checklists, policies, lessons learned).

Tools & Techniques

• Inspection: Reviews, audits, walkthroughs, peer reviews, product testing.
• Data gathering: Checklists, check sheets, statistical sampling.
• Data analysis: Root cause analysis, cause-and-effect diagrams.
• Data representation: Control charts, histograms, scatter diagrams, Pareto charts.
• Testing and product evaluations: Functional testing, stress testing, system testing.
• Meetings: Quality review boards, defect review sessions.

Outputs

• Verified deliverables.
• Work performance information.
• Quality control measurements.
• Change requests.
• Updates to project management plan, project documents, and OPAs.

Key Quality Control Tools

• Cause-and-effect diagram (Ishikawa/Fishbone): Identifies root causes of defects.
• Control charts: Monitor process stability and detect trends or out-of-control points.
• Histograms: Show frequency distribution of defects.
• Pareto chart: Prioritize issues using the 80/20 principle.
• Scatter diagram: Show correlations between variables.
• Check sheets: Collect and track defect data.

Practical Example: Medical Device Manufacturing

Context: A company produces medical devices under strict regulatory standards.

Control Quality activities:

• Devices undergo functional and stress testing.
• Quality inspectors use check sheets to record defect counts.
• Pareto chart reveals that 80 percent of failures stem from a single assembly line issue.
• Root cause analysis identifies miscalibrated equipment.
• Corrective action is initiated, and verified deliverables are submitted for stakeholder acceptance.

Outcome: Defects are caught before products reach customers, ensuring compliance and safety.

Common Pitfalls

Confusing QA and QC

• Pitfall: Treating process audits as quality control.
• Prevention: Remember QA = process, QC = deliverables.

Late inspections only

• Pitfall: Discovering defects only at the end.
• Prevention: Perform inspections throughout execution.

Over-inspection

• Pitfall: Excessive checking slows progress.
• Prevention: Balance thoroughness with efficiency.

Ignoring defect data

• Pitfall: Collecting defect metrics without analysis.
• Prevention: Use statistical and root cause tools to drive improvements.

Quick Recap Table

Key Takeaways

• Control Quality verifies that deliverables meet standards and requirements.
• Outputs include verified deliverables, quality control measurements, work performance information, and change requests.
• Tools include inspections, Pareto charts, control charts, check sheets, and root cause analysis.
• On the PMP exam, QA versus QC is a common distinction and a frequent trap.
• In practice, strong quality control ensures customer satisfaction, compliance, and reduced rework.

Next Step

With Control Quality complete, the next process is Control Resources, which ensures that project resources are being used as planned and that adjustments are made when necessary.

Bibliography

Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute.