8.1 Quality: Planning, Control & Assurance

What the Quality Practice Is For

PRINCE2's Quality practice exists to ensure that the project's products are fit for purpose — that they genuinely meet the needs of the users and stakeholders who will rely on them. It does this by documenting, in a controlled way, what the user requires of each product and how the project will demonstrate that the requirement has been met. The practice is the operational expression of the focus on products principle: a project only succeeds when its outputs are clearly defined and demonstrably delivered, so quality cannot be an afterthought tacked onto the end of delivery.

A common exam trap is to treat quality as a single activity called 'checking the product'. It is not. The practice splits into three distinct, complementary parts that operate at different points in the life cycle and are typically performed by different people. Confusing them is one of the most reliable ways to lose marks on scenario questions.

The Three Parts of Quality

Quality planning is the up-front work of deciding how quality will be achieved for a given product or project. It defines the quality methods (the techniques that will be used to verify conformance), the quality criteria (the measurable, testable statements of what 'good' looks like), and the quality tolerances (the permissible deviation before a product is rejected). These are written into the Quality Management Approach at project level and into the Product Description for each individual product. Quality planning happens during initiation (and is refined as each product is planned), not after the product is built.

Quality control is the act of checking a specific product against its defined criteria — does this product actually meet the requirements we wrote down? Control activities include inspections, tests, reviews, measurements, and in-process checks. They are typically performed by the people building the product, by peers, or by specialists such as testers. The output of a quality control activity is a confirmed pass or fail against the criteria, plus any defects or action items.

Quality assurance is an independent check — not that the product meets its criteria, but that the quality methods being used are suitable and are being applied correctly. Assurance asks: are we doing the right things, in the right way, to give us confidence in quality? In PRINCE2, the Project Assurance role (appointed by the Project Board) is the primary vehicle for quality assurance. Because it is independent of the PM and delivery team, assurance can challenge the methods themselves, whereas control can only confirm conformance to them.

Quality Is Built In Up Front

A recurring theme in PRINCE2 scenario questions is that quality is established at the beginning of the project, not bolted on at the end. During Starting Up a Project, the Project Product Description is drafted to capture the customer's quality expectations and the acceptance criteria for the overall project product — the high-level statement of what the finished project must achieve and how the customer will accept it. These flow downwards into individual Product Descriptions during planning, each of which carries its own quality criteria, quality methods, and quality tolerances.

This is why the 'focus on products' principle and the Quality practice are so tightly coupled: the principle demands that products are defined before they are built, and the Quality practice provides the mechanism (criteria, methods, assurance) for proving that the defined products have been delivered correctly. A project that defines products but never specifies how they will be checked has planning without quality; a project that inspects outputs but never defined what 'good' means has control without planning.

Who Does What

The Project Manager is responsible for ensuring quality is planned and that quality control activities take place and are recorded. The Project Board approves the Quality Management Approach as part of the PID and is accountable for acceptance of the project product. Project Assurance, appointed by the board, independently verifies that quality methods are suitable and applied — this is the assurance layer. Team Managers and delivery staff perform the day-to-day control activities. Senior User representation on the board is critical because the user community owns the definition of 'fit for purpose'.

Exam Scenario Patterns

Three scenario shapes recur in the practitioner exam:

1. Control vs assurance distinction. A scenario describes someone 'checking that the inspection process is being followed' — that is assurance, not control. If they are 'checking the product against the specification', that is control. The independence of the actor is the tell: control is done by the team, assurance by an independent function.
2. Where quality criteria are defined. Criteria for a specific product live in its Product Description; the project-level approach to managing quality lives in the Quality Management Approach; the overall project product's acceptance criteria live in the Project Product Description. Match the level of the question to the right document.
3. Who performs quality assurance. The answer is Project Assurance, appointed by and reporting to the Project Board — not the PM, not the team, not an external auditor unless specifically commissioned. Assurance is internal to the project organisation but independent of the delivery line.