In the context of PRINCE2 7, Quality Control represents the operational execution of the Quality Management Approach. While Quality Planning establishes the criteria and methods during the initiation or stage boundary processes, Quality Control is the active process of monitoring specific project r…In the context of PRINCE2 7, Quality Control represents the operational execution of the Quality Management Approach. While Quality Planning establishes the criteria and methods during the initiation or stage boundary processes, Quality Control is the active process of monitoring specific project results to determine if they comply with those standards and identifying ways to eliminate causes of unsatisfactory performance.
Quality Control in PRINCE2 focuses on the products, not the process, and consists of three distinct activities:
1. **Carrying out the Quality Methods:** This involves executing the inspections, testing, or reviews defined in the Product Description. A key technique in PRINCE2 is the 'Quality Review,' a structured meeting with defined roles (Chair, Presenter, Reviewer, Administrator) designed to assess a product against agreed criteria. This ensures a collaborative and objective assessment, checking the product against the specification rather than the individual who built it.
2. **Maintaining Records:** Every quality activity must generate evidence. This requires updating the Quality Register to reflect the current status of products (e.g., 'passed', 'failed', or 'provisional') and retaining Quality Records (such as test scripts, error logs, or review minutes). These records provide the necessary audit trail to prove the product is fit for purpose.
3. **Obtaining Acceptance:** Successful Quality Control is the prerequisite for approval. Once a product passes its quality checks, the designated authority provides formal sign-off, moving the product toward final acceptance.
Practitioners must distinguish this from Project Assurance. Assurance verifies that the project is being managed correctly and processes are followed, whereas Quality Control strictly verifies that the project's outputs (products) meet their defined requirements.
Quality Control
What is Quality Control? In the context of PRINCE2 v7, Quality Control refers to the operational techniques and activities used to fulfill requirements for quality. While Quality Planning defines the criteria and methods, Quality Control is the execution phase where you inspect, test, and review the project's products to ensure they meet the criteria defined in the Product Description.
Why is it Important? Quality Control is essential because it is the mechanism that prevents defective products from being delivered to the customer. It provides: 1. Verification: Evidence that products meet the agreed standards. 2. Acceptance: The formal approval required to move to the next stage or close the project. 3. Baseline: A known state of a product (approved) so it can be baselined and subject to change control.
How it Works Quality Control involves implementing the quality methods defined during planning. This typically follows this workflow: 1. Preparation: Ensuring the product and the reviewers/testers are ready. 2. Execution: Carrying out the quality method (e.g., a formal Quality Review, a software test, or a site inspection). 3. Assessment: Comparing the results against the Quality Criteria found in the Product Description. 4. Recording: Updating the Quality Register with the results (Pass, Fail, or Concession).
Exam Tips: Answering Questions on Quality Control When answering Practitioner questions, apply these specific strategies:
1. Differentiate Control vs. Assurance This is the most common trap. If the scenario involves checking a specific product (e.g., checking a wall for structural integrity), it is Quality Control. If the scenario involves checking that the team is following the right processes (e.g., checking if the team used the correct form to record the structural check), it is Project Assurance.
2. Watch the Quality Register If a question asks where to record the outcome of a test, the answer is almost always the Quality Register. The Quality Register is a dynamic management product used to track the progress of quality activities.
3. The Quality Review Technique Roles PRINCE2 defines specific roles for formal reviews. Questions may ask who should do what: - Chair: Runs the meeting, does not review the product details. - Presenter: Represents the producer, answers questions, fixes errors. - Reviewer: Inspects the product against criteria before the meeting. - Administrator: Records the results.
4. Handling Defects If a question describes a product that fails its criteria, look for answers involving the Issue Register (for major failures requiring an Exception Report) or the granting of a Concession (Off-specification) by the Project Board if the product is usable despite the error.