Prince2: Quality Theme
The PRINCE2 theme of Quality is concerned with ensuring that products are fit for their intended purposes and satisfy the quality expectations of customers and users.
Quality expectations are set and restated through the life of a project and initially within the
- Project Mandate
- Project brief
- Project Initiation Documentation (PID)
There are four inter-related Quality Management areas:
- Quality System
- Quality Assurance
- Quality Planning
- Quality Control
Quality Management Systems
The Quality systems and methods employed within a project usually operate within a larger Quality Management System adopted by the organisation (such as ISO9000). PRINCE2 suggests that this should include at minimum
- A quality manual
- Statement of quality policy
- Include documentation of
Quality Assurance should be external to the project team. If a corporate QA function does not exist, it should usually be managed from within the Project Board by the Project Assurance role.
Project Management responsibilities include…
- Overall approach
- Stage quality activities
- Objectives and Requirements
- Overall approach
Capture of customer expectations of quality
- Project brief
- The quality management strategy section of the Project Initiation Document
There are two broad kinds of quality methods – “In-process” and “Appraisals”.
Difference between Quality Assurance and Quality Control
- Quality Assurance sets standards, defines processes, ensures they are followed
- Quality Control inspects products to ensure they meet specifications
Product Descriptions consist of
- Purpose of product
- Products comprising this product
- Customer quality expectations
- Acceptance criteria
- Project level quality tolerance
Product descriptions are mandatory and should also include quality specifications and a description of quality methods. They are used to manage product delivery.
Quality Review techniques should be based upon product descriptions.
Quality Management Strategy
Produced by the ‘Initiating a Project’ Process. The strategy consists of
- Quality Management Systems
- Applicable Standards
- Approach to Project Assurance
Provides an audit trail of planned and undertaken quality events. As products are produced appropriate control techniques are used to test them. The quality review technique described in PRINCE2 is one such control technique.
Reviews ensure that products meet quality standards. Reviews can be invoked at any time during a project, usually as part of the ‘Managing Product Delivery’ process.
Reviewers use quality criteria from the product descriptions to ensure the required standards are met.
Quality Review Objectives
- Assess product against set criteria
- Provide wider acceptance of product
- Confirm product is complete
- Baseline product for change control
Quality Review Technique
Consists of Preparation, Agenda and Follow-up
- Time and Location
- Distribute copy of product
- Assess against quality criteria
- Prepare question list
- Review errors
- Agree actions
- Sign-off of products (if appropriate)
- Document actions
- Complete actions
- Communicate results
- File records
When the review is complete, the product is approved by an appropriate person or group.
As a result of the review a product can be considered as complete, conditionally complete or incomplete.
Quality Review Roles
- Chair (In a quality review, this role would produce a consolidated question list prior to the review meeting agenda. The chair of a quality review is first identified in the Stage Plan)