Project Assurance vs Quality Review: Key Differences for PRINCE2 Foundation

• ✓ A.Project Assurance provides continuous independent oversight, while a quality review is a specific event to examine a product
• B.Project Assurance focuses on the Business Case, while a quality review focuses on the Project Plan
• C.Project Assurance is a role, while a quality review is a process in Managing a Stage Boundary
• D.Project Assurance is performed by the Project Manager, while a quality review is performed by the Project Board

Why A: Project Assurance is a continuous, independent oversight function that ensures the project remains viable and compliant with standards throughout its lifecycle, while a quality review is a specific, time-boxed event focused on examining a product's fitness for purpose. In PRINCE2, Project Assurance is a role (often assigned to the Project Board or a separate person) that provides objective checks, whereas a quality review is a technique within the quality management approach used to verify that a product meets its quality criteria. This distinction is fundamental because it separates ongoing governance from discrete product verification activities.

• A.Both are the same
• ✓ B.Project Assurance is a role; a quality review is a technique
• C.Project Assurance is performed by the Project Manager
• D.Quality review is a role; Project Assurance is a technique

Why B: Project Assurance is a role defined in PRINCE2, responsible for monitoring the project's compliance with its management stages, business case, and quality standards independently of the Project Manager. A quality review is a technique used to assess the quality of a product by examining it against predefined criteria, involving a structured meeting with reviewers. The key distinction is that Project Assurance is a governance role, while a quality review is a specific quality management technique.

• A.Project Assurance is performed by the Project Manager; quality review is independent
• B.Project Assurance only occurs at stage boundaries; quality review occurs throughout
• C.There is no difference; they are synonyms
• ✓ D.Project Assurance is a role; quality review is a technique

Why D: Project Assurance provides independent oversight of the entire project on behalf of the Project Board, whereas a quality review is a specific technique to assess the quality of a product.

• ✓ A.Project Assurance is a role providing ongoing independent oversight; a quality review is a technique to evaluate product quality
• B.Project Assurance is performed by the Project Manager; quality review is performed by the team
• C.There is no difference; quality review is another name for Project Assurance
• D.Project Assurance focuses on benefits; quality review focuses on products

Why A: Project Assurance is a continuous, independent oversight role for the Project Board, while a quality review is a specific technique to assess product quality at a point in time.

• A.Project Assurance is performed by the Project Manager; a quality review is performed by the Team Manager.
• B.There is no difference; both terms are interchangeable.
• C.Project Assurance focuses on risks; a quality review focuses on issues.
• ✓ D.Project Assurance is a role; a quality review is a process.

Why D: Project Assurance is an independent oversight role that monitors the project's adherence to standards and controls, while a quality review is a specific technique used to check that a product meets its quality criteria.

• A.Project Assurance focuses on the Business Case; quality review focuses on the project plan
• ✓ B.Project Assurance is a role; quality review is a technique
• C.Project Assurance is performed by the Project Manager; quality review is performed by the team
• D.Project Assurance is done at the end of a stage; quality review is done continuously

Why B: Project Assurance is an independent, ongoing role providing objective oversight to the Project Board. Quality review is a specific technique for reviewing product quality at defined points.

• ✓ A.Project Assurance focuses on the project's adherence to plans; quality review focuses on product quality.
• B.Project Assurance is performed by the Project Manager; quality review is performed by the team.
• C.There is no difference; they are interchangeable terms.
• D.Project Assurance is only for large projects; quality review is for all projects.

Why A: Project Assurance is a PRINCE2 role responsible for verifying that the project remains viable and compliant with its business case, plans, and standards, independent of the Project Manager. A quality review is a specific technique used to assess whether a product meets its defined quality criteria and to identify defects. The key difference is that Project Assurance provides ongoing oversight of the project's adherence to plans and governance, while a quality review focuses on the quality of a specific product at a point in time.

• A.Project Assurance is performed by the Project Manager; quality review is performed by the team
• B.Quality review is a role; Project Assurance is a process
• C.They are the same thing
• ✓ D.Project Assurance is a role; quality review is a technique

Why D: Project Assurance is a role within the PRINCE2 management structure, responsible for ensuring that the project remains viable and compliant with the business case, while a quality review is a technique used to assess the quality of a product. Option D correctly distinguishes between these two concepts: Project Assurance is a role, and quality review is a technique. This aligns with PRINCE2's separation of management responsibilities from quality control activities.