HKSM

Quantitative results from inspections, tests, and reviews that show how products or processes perform against stated quality criteria. These measurements are analyzed to confirm conformance, reveal trends, and drive corrective or preventive actions.

Key Points

• Quality control measurements are objective, time-stamped data gathered from inspections, tests, and reviews.
• They are compared against quality metrics, acceptance criteria, and specification or control limits to judge conformance.
• Analysis focuses on variation, trends, and stability using tools like run charts, control charts, histograms, and Pareto analysis.
• They inform both product acceptance decisions and continuous improvement actions for the process.
• Data collection must follow a defined sampling plan and calibrated measurement system to ensure reliability.
• Traceability to requirements and test cases is essential for meaningful interpretation and decision-making.

Purpose of Analysis

To determine whether deliverables meet specified quality criteria, identify patterns in defects or variation, and understand process performance. The results guide corrective and preventive actions, process improvements, and acceptance decisions.

Consistent analysis turns raw measurements into actionable insights, helping the team prevent recurrence of issues and predict future performance.

Method Steps

• Define what to measure and the measurement method based on quality metrics and acceptance criteria.
• Collect data using test plans, inspection checklists, and a documented sampling plan.
• Validate data integrity by checking calibration, completeness, and measurement system variation.
• Analyze data using appropriate statistical or visual tools (e.g., control charts, Pareto, trend lines).
• Compare results to specification limits and, where applicable, control limits and historical baselines.
• Identify root causes for nonconformities or instability and recommend actions.
• Report findings, update logs and registers, and submit change requests if thresholds are breached.
• Monitor follow-up actions and reassess measurements to confirm effectiveness.

Inputs Needed

• Quality metrics, acceptance criteria, and specification limits.
• Test plans, inspection checklists, and sampling strategy.
• Process control limits or historical baselines for comparison.
• Measurement tools and calibration records.
• Previous quality control measurements and trend data.
• Requirements, deliverable descriptions, and traceability references.

Outputs Produced

• Quality control reports and dashboards summarizing results and trends.
• Updated defect and nonconformance records with severity and status.
• Statistical summaries and visuals (e.g., control charts, Pareto charts, capability indices).
• Recommended corrective or preventive actions and process improvement ideas.
• Change requests when deviations require formal updates or rework.
• Updates to risk register, lessons learned, and quality management documents.

Interpretation Tips

• Distinguish common-cause variation from special-cause variation before acting.
• Do not overreact to a single data point; confirm patterns with run rules or trends.
• Validate sample size and sampling method to avoid misleading conclusions.
• Confirm measurement system accuracy and repeatability to reduce noise.
• Use both specification limits (customer requirements) and control limits (process behavior) appropriately.
• Translate findings into impact on requirements, schedule, cost, and customer value.

Example

A team inspects 200 units and records six defects. The defect rate is 3%, with most issues tied to a single cause identified via Pareto analysis. A control chart shows the process is stable but centered near the upper specification limit. The team adjusts the process setpoint, updates the checklist, and the next sample drops to a 1% defect rate with the mean moving toward the center of the spec range.

Pitfalls

• Relying only on pass/fail counts without examining variation and trends.
• Confusing control limits with specification limits, leading to incorrect actions.
• Making decisions from too little data or non-representative samples.
• Ignoring measurement system issues such as uncalibrated tools or operator bias.
• Selective reporting of results that hides defects or outliers.
• Adjusting the process unnecessarily (tampering) when the process is in control.

PMP Example Question

During Control Quality, the team compiles defect counts, rework hours, and tolerance readings. How should the project manager use these quality control measurements?

1. Approve deliverables immediately if most results are within specification limits.
2. Feed the data into Manage Quality to analyze trends, identify root causes, and recommend process improvements.
3. Update the project budget baseline to include the cost of rework discovered.
4. Archive the data for lessons learned at project closeout only.

Correct Answer: B — Feed the data into Manage Quality to analyze trends, identify root causes, and recommend process improvements.

Explanation: Quality control measurements are analyzed to evaluate conformance and drive improvement actions. They inform both acceptance decisions and upstream process improvements.