Quality Management Plan: [Project name]

Project quality management plan: quality policy and objectives, standards and acceptance criteria, roles, planning, assurance, control, tools, nonconformance and corrective action, continuous improvement and records. Based on common project management practice; the structure uses ISO 10005:2018 (guidelines for quality plans) as a structural reference only. Replace every [bracketed] value and every row marked Example.

Document control

Approvals

Revision history

Contents

1. Scope and purpose
2. Quality policy and objectives
3. Quality standards and acceptance criteria
4. Roles and responsibilities
5. Quality planning
6. Quality assurance
7. Quality control
8. Tools and techniques
9. Nonconformance and corrective action
10. Continuous improvement
11. Quality records
12. References and glossary

1. Scope and purpose

This plan defines how quality will be managed on [Project name] so that its deliverables meet stakeholder requirements and the acceptance criteria in the scope baseline. It applies to all project deliverables, including those produced by suppliers, and to the project management processes used to produce them.

2. Quality policy and objectives

The project adopts the organisation's quality policy ([QP-001]) and interprets it as follows for this project: deliverables are fit for purpose, verified against agreed criteria before acceptance, and defects are found as early as possible where they are cheapest to fix.

3. Quality standards and acceptance criteria

Deliverables are built to the standards below and accepted against the listed criteria.

3.1 Applicable standards and requirements

3.2 Acceptance criteria by deliverable

4. Roles and responsibilities

Quality responsibilities are allocated as follows.

5. Quality planning

Quality activities are planned per stage and included in the project schedule.

The cost of quality is estimated so that prevention and appraisal are funded explicitly.

6. Quality assurance

Quality assurance confirms that the project is following its planned processes and that those processes are producing the expected quality. Findings are logged in the nonconformance register (section 9).

7. Quality control

Quality control verifies that deliverables meet their acceptance criteria before they are accepted.

7.1 Inspections and reviews

7.2 Testing

Testing is planned in [Test plan TP-001] and covers unit, integration, system, performance, accessibility, security and user acceptance testing. Test completion is reported in a test completion report.

7.3 Quality metrics

Defect removal efficiency is calculated as:

$DRE = \frac{D_{\text{before release}}}{D_{\text{before release}} + D_{\text{after release}}} \times 100\%$

Example: 180 defects found before release and 12 in the first 30 days after release give $DRE = 180 / 192 \approx 93.8\%$, which meets the target.

7.4 Quality reporting

Quality status is reported in every project status report as a RAG rating with the metrics above, open nonconformances by severity and any acceptance criteria at risk. A monthly quality review, chaired by the quality lead, looks at trends rather than single values: a rising defect inflow late in testing, or a falling first-time acceptance rate, is raised as a risk in the RAID log even when the current numbers are still within target. Before each stage gate the quality lead issues a short quality statement confirming which acceptance criteria are met, which are not, and the residual quality risk the sponsor is asked to accept.

8. Tools and techniques

The project uses the following tools and techniques.

9. Nonconformance and corrective action

Any deliverable or process that does not meet its requirement is recorded as a nonconformance (NC). The NC owner contains the problem, analyses the root cause, and agrees a correction and, where the cause could recur, a corrective action.

10. Continuous improvement

Quality data is reviewed at each stage gate and at monthly quality reviews. Improvement actions are recorded and tracked like other project actions; lessons that apply beyond the project are added to the lessons learned register.

11. Quality records

The following records are kept as evidence of quality management.

12. References and glossary

The following documents and terms are referenced in this plan.

Standard and licence note

Structure aligned with ISO 10005:2018, Quality management: Guidelines for quality plans, used only as a structural reference for the contents of a quality plan. Content is based on common project management practice. This template is original text written for this collection and reproduces no text from the standard; obtain the standard for its guidance. Template licence: MIT.