PRINCE2 Fundamentals

with Claudine Peet

Quality Management Strategy

Project Name: BG Apps Flexible Working

Date: Today Release: Draft

Author: Project Manager

Owner: Senior User and Senior Supplier

Document Number:

NOTE: This document is a sample document intended to demonstrate the typical contents required. All
names and information relate to the fictitious scenario provided.

Revision History
Date of next revision:

Revision Date Previous Revision Date Summary of Changes Changes Marked

Today First Draft

Approvals
This document requires the following approvals. A signed copy should be placed in the project files.

Name Signature Title Date of Issue Version

Senior User Today V1.0

Senior Supplier Today V1.0

Executive Today V1.0

Distribution
This document has been distributed to:

Name Title Date of Issue Version

Complete Solutions, Jerry Brackshaw Account Manager Today V1.0

Darryl Smith QA Manager Today V1.0

PRINCE2 Fundamentals with Claudine Peet

1 of 5
Overview
Purpose A Quality Management Strategy is used to define the quality techniques and standards
to be applied, and the various responsibilities for achieving the required quality levels
during the project.

Advice The Quality Management Strategy is derived from the Project Board, Project Brief, project
management team structure (for roles and responsibilities), Project Product description
(for the customer’s quality expectations and acceptance criteria), organisational standards,
supplier and customer quality management systems, configuration management
requirements, change control requirements, corporate or programme strategies, facilitated
workshop, and informal discussions.

A Quality Management Strategy can take a number of formats, including stand-alone

document or a section in the Project Initiation Document, or entry in a project
management tool.

The following quality criteria should be observed:

• The strategy clearly defines ways in which the customer’s quality expectations will be met

• The defined ways are sufficient to achieve the required quality

• Responsibilities for quality are defined up to a level that is independent of the project and

Project Manager

• The strategy conforms to the supplier’s and customer’s quality management systems

• The strategy conforms to the corporate or programme quality policy

• The approaches to assuring quality for the project are appropriate in the light of the

standards selected

PRINCE2 Fundamentals with Claudine Peet

2 of 5
Introduction
(States the purpose, objectives, and scope, and identifies who is responsible for the strategy)

This strategy will set out the quality procedures and processes we will need to follow to ensure that we
deliver a fit for purpose output. The Senior User and Senior Supplier will be responsible for this strategy.

Quality Management Procedure

(A description of, or reference to, the quality management procedure to be used. Any variance from
corporate or programme management quality standards should be highlighted, together with a
justification for the variance.)

The procedure should cover the following topics:

Quality planning
Darryl Smith, the QA manager, will work with the external hardware and software suppliers to ensure the
correct standards and specifications are identified and communicate this to the Senior User.

The Senior User and Senior Supplier will need to meet and define the standards and types of testing
required to ensure a quality output on completion of the project.

Quality control
(The project’s approach to quality control activities. This may include quality standards, templates, and
forms to be employed (e.g., product description(s), Quality Register); definitions of types of quality
methods (e.g., inspection, pilot); and metrics to be employed in support of quality control.)

Standards:
• Compliance with health and safety standards for the office space

• Compliance with applicable industry hardware and software standards

• Equipment will be compliant with relevant quality standards (to be confirmed with suppliers)

Templates and forms:

• User acceptance testing will follow set test scripts (to be defined in the product specification
documents)

• Acceptance of hardware and software will be upon completion of UAT and will be documented in
the Acceptance Record template provided

PRINCE2 Fundamentals with Claudine Peet

3 of 5
Quality assurance
(The project’s approach to quality assurance activities. This may include responsibilities of the Project
Board, compliance audits, and corporate or programme management reviews.)

Quality assurance for the project will be undertaken by separate individuals appointed by the
Project Board performing Project Assurance. They will be responsible for checking the project is
following procedures and doing things correctly, providing advice and guidance where required,
and undertaking reviews where necessary to capture lessons and make any improvements.

Tools and Techniques

(Refers to any quality management systems or tools to be used, and any preference for techniques
that may be used for each step in the quality management procedure)

Tools:
• Health and safety legislation provides a checklist to be used

• Any tests or checks required for equipment will use the tools defined in the standards

Techniques:
• Remote access VPN testing to be carried out with an independent supplier specializing in
remote access testing

• PAT and other equipment testing will be carried out independently in compliance with
relevant standards

• The health and safety office will carry out a H&S audit upon completion of the project to
confirm compliance

Records
(Definition of what quality records will be required and where they will be stored including the
composition and format of the Quality Register)

A Quality Register will be created and maintained. This register will record which products are being
tested, when, by whom, how, and the result. It should also show target and actual dates.

Reporting
(Describes any quality management reports that are to be produced, their purpose, timing, and
recipients)
Quality reports are not required for this project. The Quality Register will hold all relevant testing
information required and can be provided at any time to the Project Board for further scrutiny.

PRINCE2 Fundamentals with Claudine Peet

4 of 5
Timing of Quality Management Activities
(States when formal quality management activities are to be undertaken; for example, audits—this
may be a reference to the Quality Register)
• A quality audit will be undertaken at the end of the project to ensure compliance with all
applicable legislation.

• The Quality Register must be up to date and reflect the latest quality activity on the project at
all times.

Roles and Responsibilities

(Defines the roles and responsibilities for quality management activities, including those with quality
responsibilities from corporate or programme management)
• Project Support will be responsible for maintaining the Quality Register.

• Team managers are responsible for informing Project Support of any up-to-date information for
the Quality Register.

• Project Assurance will confirm product acceptance to the Senior User.

• The project manager is responsible for reporting on status of product development and testing
as part of their highlight report.

PRINCE2 Fundamentals with Claudine Peet

5 of 5