HKSM

Key Points

• Part of the project management plan that guides how quality is planned, managed, and measured.
• Specifies quality objectives, standards, metrics, thresholds, and acceptance criteria.
• Defines quality assurance (process-focused) and quality control (product-focused) activities.
• Clarifies roles, responsibilities, reviews, audits, testing, and reporting methods.
• Integrates with scope, schedule, cost, risk, procurement, and configuration/change control.
• Tailored to the delivery approach (predictive, iterative, or hybrid) and regulatory context.

Purpose

• Align the team and stakeholders on what quality means for the project and how it will be achieved.
• Prevent defects through clear standards, methods, and continuous improvement practices.
• Ensure consistent quality measurement, transparency, and timely escalation of issues.
• Provide criteria for acceptance of deliverables and for supplier quality expectations.

Typical Sections

• Quality objectives and applicable standards.
• Roles and responsibilities for quality.
• Quality assurance approach (audits, process reviews, compliance checks).
• Quality control approach (inspections, testing, verification and validation).
• Quality metrics, thresholds, and data collection methods.
• Acceptance criteria and acceptance process.
• Nonconformance and defect management procedures.
• Supplier and procurement quality requirements.
• Tools, checklists, templates, and reporting cadence.
• Interfaces with other plans (scope, risk, change/configuration, schedule, cost).
• Continuous improvement and lessons learned approach.
• Quality budget, schedule, and resource needs.

How to Create

• Engage stakeholders to define quality objectives, acceptance criteria, and regulatory needs.
• Identify applicable organizational, industry, and regulatory standards to comply with.
• Select quality metrics and set measurable thresholds and tolerances.
• Plan quality assurance activities (process definitions, audits, reviews) to prevent defects.
• Plan quality control activities (inspections, tests, checklists) to detect and correct defects.
• Define roles, responsibilities, escalation paths, and reporting formats.
• Integrate quality tasks and milestones into schedule, cost, and risk responses.
• Specify supplier quality criteria and how vendor deliverables will be verified.
• Establish change control for quality standards, metrics, and acceptance criteria.
• Review with the team and key stakeholders; approve and baseline as part of the project plan.

How to Use

• Guide day-to-day QA/QC activities, audits, reviews, and testing throughout the life cycle.
• Monitor metrics and thresholds; record results using agreed data collection methods.
• Log, analyze, and resolve nonconformances; implement corrective and preventive actions.
• Report quality performance to stakeholders and escalate deviations promptly.
• Update related plans and the risk register when quality issues or trends emerge.
• Capture lessons learned and improve processes iteratively.

Maintenance Cadence

• Review at phase gates or iteration boundaries to confirm continued fit-for-purpose.
• Update after significant scope, regulatory, supplier, or technology changes.
• Adjust when recurring defects, audit findings, or trend shifts are detected.
• In iterative/agile delivery, inspect and adapt the plan each sprint or release.
• Rebaseline the plan through change control when standards or acceptance criteria change.

Example

Project X - Quality Management Plan (Excerpt)

• Objectives: Deliver features that meet usability and safety standards; defect escape rate below 1% per release.
• Standards: Organization QA Policy v3.2; ISO 9001 clauses 8.5 and 9.1; applicable regulatory guideline ABC-123.
• Metrics: Defect density ≤ 0.6 per KLOC; test coverage ≥ 85%; audit findings closed within 10 business days.
• QA Activities: Process audits monthly; design reviews at each milestone; compliance checklist per deliverable.
• QC Activities: Inspection of critical outputs; verification against acceptance criteria; sampling per ANSI/ASQ Z1.4.
• Acceptance: All critical tests passed; no open high-severity defects; stakeholder sign-off per acceptance workflow.
• Roles: Quality lead owns audits and reporting; team leads own corrective actions; PM manages escalation.
• Reporting: Weekly dashboard; threshold breaches trigger immediate escalation to the sponsor.

PMP Example Question

During planning, the team defines how it will prevent and detect defects and sets thresholds for key metrics. Which document should capture these decisions?

1. Scope management plan.
2. Quality management plan.
3. Requirements traceability matrix.
4. Issue log.

Correct Answer: B — Quality management plan.

Explanation: The quality management plan defines quality objectives, standards, metrics, and the assurance and control activities used to achieve them. The other documents do not govern overall quality planning.