4.6 Quality Practice & Quality Control

4.6 Quality Practice & Quality Control

Delivering a project on time and within budget is meaningless if the resulting deliverables fail to meet operational standards or are unsuitable for business use. The Quality Practice in PRINCE2 7 provides the management mechanisms required to define, implement, and verify that all project products are fit for purpose and satisfy customer expectations.

In PRINCE2, quality is not tested into a product at the end of a project; it is planned, designed, monitored, and controlled continuously throughout the product lifecycle.

---

Purpose and Key Terminology

PRINCE2 7 Definition: The purpose of the Quality practice is to define and implement the mechanisms to ensure that the project's products meet expectations and are fit for purpose.

Core Quality Definitions for the Foundation Exam

• Quality: The degree to which a set of inherent characteristics of a product fulfills requirements.
• Fit for Purpose: The condition where a deliverable satisfies its intended operational function and meets all defined quality criteria.
• Quality Management: The coordinated activities to direct and control an organization with regard to quality.
• Quality Planning: Defining the project's quality standards, customer quality expectations, acceptance criteria, product quality specifications, and quality control methods.
• Quality Control: Executing the operational techniques and inspections used to monitor product creation, verify compliance with quality criteria, and eliminate causes of unsatisfactory performance.

---

The Quality Lifecycle: Planning vs. Control

The Quality practice operates through two distinct but closely linked phases: Quality Planning (establishing expectations and standards) and Quality Control (executing inspections and verifying compliance).

┌─────────────────────────────────────────────────────────────┐
│                      QUALITY PLANNING                       │
│  - Capture Customer Quality Expectations in PPD             │
│  - Establish prioritized, measurable Acceptance Criteria    │
│  - Develop Quality Management Approach                      │
│  - Write Product Descriptions with Quality Criteria & Methods│
│  - Set up baseline Quality Register                         │
└──────────────────────────────┬──────────────────────────────┘
                               │  Executes against plan
┌──────────────────────────────▼──────────────────────────────┐
│                      QUALITY CONTROL                        │
│  - Execute Quality Checking Methods (Tests, Inspections)    │
│  - Log inspection results & pass/fail status in Register    │
│  - Resolve quality defects via rework                       │
│  - Secure formal Product Approval & Sign-off                │
└─────────────────────────────────────────────────────────────┘

Quality Planning Phase

Quality planning occurs during Starting up a project (SU) and Initiating a project (IP), with detailed quality planning repeated during stage boundaries. It establishes:

1. Customer Quality Expectations: High-level expectations stated in the Project Product Description (PPD).
2. Acceptance Criteria: Prioritized, measurable criteria defining product acceptance.
3. Quality Management Approach: Strategy detailing quality procedures, standards, tools, and responsibilities.
4. Product Descriptions: Explicit quality criteria, tolerances, methods, and responsibilities for each deliverable.
5. Quality Register: Baseline log to record planned quality events.

Quality Control Phase

Quality control occurs during Controlling a Stage (CS) and Managing Product Delivery (MP). Specialist teams execute quality methods specified in Product Descriptions. Inspection results are recorded in the Quality Register, defects are remediated, and formal sign-off is obtained from authorized approvers.

---

Customer Quality Expectations vs. Acceptance Criteria

A frequent exam focus is distinguishing between Customer Quality Expectations and Acceptance Criteria.

---

Core Quality Management Products

The Quality practice relies on two primary management products:

1. Quality Management Approach

Documented during Initiating a project (IP), the Quality Management Approach defines how quality will be assured and controlled across the project lifecycle.

• Contents include:
  • Quality standards to be applied (e.g., ISO 9001, IEEE software standards, internal corporate standards).
  • Quality control methods and testing techniques permitted.
  • Roles and responsibilities for quality activities.
  • Quality tools, templates, and automated checking systems.
  • Rules for updating and maintaining the Quality Register.
  • Timing and procedures for formal quality audits and reviews.

2. Quality Register

The Quality Register is an operational log established during initiation and maintained by the Project Manager (or Project Support). It tracks all planned and executed quality events.

Worked Example: Quality Register Log Entries

• Key Functions of the Quality Register:
  • Acts as a summary checklist of quality activities for the Project Manager.
  • Provides empirical evidence for stage end reports and Highlight Reports.
  • Ensures no deliverable is handed over without documented approval.

---

3. Product Register (Project Log)

• The Product Register is a project-log record that tracks the project's products (configuration items) and their status through the lifecycle.
• It complements Product Descriptions (which define quality criteria) and the Quality Register (which logs quality activities and results).
• In PRINCE2 7, quality and configuration awareness rely on knowing which product version is current—product register entries support that control.

Quality Assurance vs. Project Assurance

Understanding the distinction between Quality Assurance and Project Assurance is critical for the Foundation exam.

   ┌─────────────────────────────────────────────────────────────┐
   │                    QUALITY ASSURANCE                        │
   │  - Corporate / Programme level (Outside Project Team)       │
   │  - Ensures compliance with organizational quality standards │
   └─────────────────────────────────────────────────────────────┘
                                 ▲
                                 │ Independent Verification
   ┌─────────────────────────────┴───────────────────────────────┐
   │                    PROJECT ASSURANCE                        │
   │  - Project Board level (Inside Project Management Team)     │
   │  - Monitors project execution across Business/User/Supplier │
   └─────────────────────────────────────────────────────────────┘

Exam Tip: Project Assurance is a mandatory Project Board role and CANNOT be delegated to the Project Manager, Team Manager, or Project Support. Quality Assurance sits outside the project team entirely.

---

The PRINCE2 Quality Review Technique

The Quality Review Technique is a structured, four-role inspection process designed to review document-based products (such as designs, specifications, architectures, or management products).

The Four Roles in a Quality Review

1. Chair: Leads the review, maintains meeting focus, ensures standards are followed, and confirms final approval sign-off decisions. Must be independent of the product creation.
2. Presenter: The author/producer of the product. Presents the deliverable, answers queries, and accepts action items for remediation.
3. Reviewer: Independent specialist who inspects the product prior to the meeting against Product Description quality criteria, identifying defects or omissions.
4. Administrator: Administrative support (often Project Support) who records defects, logs action items, and publishes the review result.

The Three Stages of a Quality Review

  ┌──────────────────┐      ┌──────────────────────────┐      ┌──────────────────┐
  │  1. PREPARATION  ├─────►│ 2. QUALITY REVIEW MEETING├─────►│  3. FOLLOW-UP    │
  │                  │      │                          │      │                  │
  │ - Distribute PD  │      │ - Review defect list     │      │ - Perform rework │
  │   & Product      │      │ - Discuss issues         │      │ - Re-inspect     │
  │ - Reviewers check│      │ - Determine outcome      │      │ - Sign-off product│
  │ - Submit Question│      │   (Approve / Conditional │      │   in Register    │
  │   Lists          │      │    / Reject)             │      │                  │
  └──────────────────┘      └──────────────────────────┘      └──────────────────┘

Review Outcomes:

• Approved: Product meets all quality criteria; signed off immediately.
• Conditionally Approved: Minor defects found; signed off automatically once Presenter completes documented minor fixes (no re-meeting required).
• Rejected: Major defects found; product must undergo significant rework and a full re-review meeting.

---

Quality Control in Agile and Digital Environments

In modern digital and agile environments, PRINCE2 quality control mechanisms integrate seamlessly with automated delivery pipelines:

• Definition of Done (DoD): Functions as a universal Quality Description specifying mandatory quality criteria (e.g., unit test coverage > 85%, security scan clean, code reviewed) for all User Stories.
• Automated CI/CD Quality Gates: Replaces manual Quality Review meetings with automated continuous integration builds, linting scripts, and static security analysis tools. Inspection status in the Quality Register can be updated automatically via webhook integration.
• Test-Driven Development (TDD): Writing automated unit tests before functional code directly implements the PRINCE2 principle of defining quality criteria and verification methods before creating the product.

---

Roles & Governance in the Quality Practice