Quality theme

Purpose

To provide a system to first define quality and then implement this quality and verify that products are fit to be used as intended.

Product Descriptions are written before development starts. These descriptions must include quality information. The quality information adds more information to the Product Descriptions.

What happens if quality is not as expected?

Answer: Expected benefits will not be achieved!

Definitions

Quality is defined as the total amount of features or characteristics of a product so it meets expectations or satisfies stated needs. All these features have to work as expected for a given amount of time.

Quality Management is a coordinated set of activities to direct and control an organisation with regard to quality.

Quality Management System is a complete set of quality standards, procedures and responsibilities for a site or organisation.

Quality Assurance provides a check that the project’s direction and management are adequate for the nature of the project and that it complies with relevant standards and policies. Quality assurance activities are outside the scope of PRINCE2. It is the responsibility of the Corporate / programme organisation.

The PRINCE2 approach to quality is in 2 steps:

• Plan how quality will be done: Quality Planning.
• Control quality throughout the project: Quality Control.

Approach to Quality

1. Quality Planning

The purpose of quality planning is threefold:

• Agree on the overall Quality Expectations with the Project Board.
  What are the customer’s quality expectations?
• Communicate these with all stakeholders.
• Establish how quality can be controlled during the project.
  How can we provide that we meet each specification?
  What are the Acceptance Criteria that the customer will use?

Quality Planning process consists of 6 steps:

1. Customer’s quality expectations

• Must be measurable
• Can have a tolerance
• Should be prioritised (MoSCoW technique)

2. Acceptance Criteria

• Prioritised list of attributes that the product must have (at each stage)
• Prioritisation technique: MoSCoW
• Acceptance status: Yes / No

3. Document (add) Quality Expectation and Acceptance Criteria in the Project Product Description

• Main Product of the project; do not confuse with other Product Descriptions
• Created in Start Up a Project process by Project Manager
• Product Descriptions are created in the Initiation Stage
• Used in Closing a Project stage for product acceptance

4. Quality Management Strategy

• Defines quality standards and Quality Control method
• Confirms how quality standards are going to be applied in the project
• Created in the Initiation Stage and is part of Project Initiation Documentation

5. Product Descriptions

• Of all major components (sub-products)
• Includes: identifier, title, purpose, composition, quality criteria, quality tolerance, quality method, quality skills required and quality responsibilities

6. Quality Register

• A log of quality events during the project
• Also used to plan quality activities
• Easy to use for quality control
• Provides quality history and quality audit trail
• Includes: product ID, product name, quality method, producer, approver, target & actual review dates, target & actual approve date, result (pass / fail)

2. Quality Control

Quality control takes place during the project. It’s aim is to implement and track the quality methods throughout the project in order to gain acceptance from the customer.

The Quality control process consists of 3 steps:

1. Carry out the quality methods as defined
2. Maintain Quality and Approval Records
3. Gain acceptance from the customer

Quality review technique is a quality inspection technique. It’s purpose is to inspect products to meet their quality requirements. There are 4 roles:

• Chair: Chair the meeting (independent)
• Presenter: Presents / represents the product (Team Manager)
• Reviewer: Reviews the product, ask questions (users)
• Administrator: Admin support for the chairperson

The focus of the review is to assess products, involve stakeholders, provide confirmation and baseline the product

The results of the review can be one of:

• Complete: The product is fit for purpose as is
• Conditionally complete: The product is fit for purpose subject to the actions agreed
• Incomplete: The product requires another quality review cycle

Roles and Responsibilities

Corp. Or Prog. Mgmt

Provide Quality Management Systems and Quality Assurance.

Executive

Approve Project Product Description and Quality Management Strategy.

Confirm acceptance of the Project Product.

Senior User

Provide Customer’s Quality Expectations, Acceptance Criteria.

Approve Project Product Description, Quality Management System.

Accept products.

Senior Supplier

Approve Project Product Description, Quality Management System.

Supply resources.

Approve Product Descriptions.

Project Manager

Document Quality Expectations and Acceptance Criteria.

Prepare Project Product Description, Product Descriptions and Quality Management Strategy.

Ensure Team Managers implement quality control measures agreed in Product Descriptions and Work Package.

Team Manager

Produces the products.

Manage Quality Control for the products.

Assemble Quality records.

Advise Project Manager of Product Quality Status

Project Assurance

Gives advice to Project Manager on Quality Management Strategy and suitable reviewers / approvers.

Assist the Project Board and Project Manager by reviewing Product Descriptions.

Assures the Quality Management system.

Project Support

Provides administrative support.

Maintain Records and Quality Register.