PRINCE2 (TM) Quality Management Strategy

To get an editable copy of this template to use on your project go to http://www.stakeholdermap.com/project-templates/prince-2-templates.html

Get Started. It's Free
or sign up with your email address
Rocket clouds
PRINCE2 (TM) Quality Management Strategy by Mind Map: PRINCE2 (TM) Quality Management Strategy

1. Overview

1.1. Purpose

1.1.1. 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.

1.2. Contents

1.2.1. The Quality Management Strategy should cover the following topics.

1.2.2. Introduction

1.2.3. Quality Management Procedure

1.2.4. Tools and Techniques

1.2.5. Records

1.2.6. Reporting

1.2.7. Timing of Quality Management Activities

1.2.8. Roles and Responsibilities

1.3. Advice

1.3.1. 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); Organizational standards; Supplier and customer quality management systems; Configuration management requirements; Change control requirements; Corporate or programme strategies; Facilitated workshops and informal discussions.

1.3.2. A Quality Management Strategy can take a number of formats, including: Stand-alone document or a section in the Project Initiation Document; Entry in a project management tool.

1.3.3. The following quality criteria should be observed:

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

1.3.3.2. The defined ways are sufficient to achieve the required quality

1.3.3.3. Responsibilities for quality are defined up to a level that is independent of the project and Project Manager

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

1.3.3.5. The strategy conforms to the corporate or programme quality policy

1.3.3.6. The approaches to assuring quality for the project are appropriate in the light of the standards selected.

2. How to use this template

2.1. How to share this template with your team

2.1.1. Send an email

2.1.1.1. 1. Click Share this map

2.1.1.2. 2. Select Invite People

2.1.1.3. 3. Write a message

2.1.1.4. 4. Click Invite

2.1.2. Send a link

2.1.2.1. 1. Click Share this map

2.1.2.2. 2. Tick Link to share

2.1.2.3. 3. Copy the link to share it

2.1.3. Export

2.1.3.1. 1. Click down arrow, bottom right

2.1.3.2. 2. Select the export option you want

2.2. How to complete this template

2.2.1. Complete the sections in square brackets

2.2.1.1. [....]

2.2.2. Read these sections for help on the template

2.2.2.1. Purpose

2.2.2.2. Advice

2.2.3. Navigate using the links in Contents

2.2.3.1. Contents

2.3. Attribution

2.3.1. Copyright © AXELOS Limited 2009. All rights reserved. Material is reproduced with the permission of AXELOS

2.4. Get this template here

3. Document information

3.1. Project Name

3.1.1. [name]

3.2. Date

3.2.1. [date]

3.3. Release

3.3.1. Draft/Final

3.4. Author

3.4.1. [author]

3.5. Owner

3.5.1. [owner]

3.6. Client

3.6.1. [client]

3.7. Document Number

3.7.1. [number]

3.8. Revision, Approvals & Distribution

3.8.1. Revision History

3.8.1.1. Revision # [....]

3.8.1.1.1. Revision Date

3.8.1.1.2. Previous Revision Date

3.8.1.1.3. Summary of Changes

3.8.1.1.4. Changes Marked

3.8.1.2. Revision # [....]

3.8.1.2.1. Revision Date

3.8.1.2.2. Previous Revision Date

3.8.1.2.3. Summary of Changes

3.8.1.2.4. Changes Marked

3.8.1.3. Revision # [....]

3.8.1.3.1. Revision Date

3.8.1.3.2. Previous Revision Date

3.8.1.3.3. Summary of Changes

3.8.1.3.4. Changes Marked

3.8.1.4. Date of next revision:

3.8.1.4.1. [....]

3.8.2. Approvals

3.8.2.1. Approval # [....]

3.8.2.1.1. Name

3.8.2.1.2. Signature

3.8.2.1.3. Title

3.8.2.1.4. Date of Issue

3.8.2.1.5. Version

3.8.2.2. Approval # [....]

3.8.2.2.1. Name

3.8.2.2.2. Signature

3.8.2.2.3. Title

3.8.2.2.4. Date of Issue

3.8.2.2.5. Version

3.8.2.3. Approval # [....]

3.8.2.3.1. Name

3.8.2.3.2. Signature

3.8.2.3.3. Title

3.8.2.3.4. Date of Issue

3.8.2.3.5. Version

3.8.3. Distribution

3.8.3.1. Distribution # [....]

3.8.3.1.1. Name

3.8.3.1.2. Title

3.8.3.1.3. Date of issue

3.8.3.1.4. Version

3.8.3.2. Distribution # [....]

3.8.3.2.1. Name

3.8.3.2.2. Title

3.8.3.2.3. Date of issue

3.8.3.2.4. Version

4. Introduction

4.1. [State the purpose, objectives and scope, and identify who is responsible for the strategy]

5. Quality Management Procedure

5.1. The Procedure should cover the following topics:

5.2. Quality planning

5.2.1. [...]

5.3. Quality control

5.3.1. [Document 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]

5.4. Quality assurance

5.4.1. [Document the project’s approach to quality assurance activities. This may include: Responsibilities of the Project Board, Compliance audits, and Corporate or programme management reviews]

6. Tools and Techniques

6.1. [Refer to any quality management systems or tools to be used, and any preference for techniques which may be used for each step in the quality management procedure]

7. Records

7.1. [Define what quality records will be required and where they will be stored including the composition and format of the Quality Register]

8. Reporting

8.1. [Describe any quality management reports that are to be produced, their purpose, timing and recipients]

9. Timing of Quality Management Activities

9.1. [State when formal quality management activities are to be undertaken, for example audits (this may be a reference to the Quality Register)]

10. Roles and Responsibilities

10.1. [Define the roles and responsibilities for quality management activities, including those with quality responsibilities from corporate or programme management]