PRINCE2 Quality Review Technique
The PRINCE2 Quality Review technique is a Quality Inspection technique. It has defined roles and a specific structure to follow. The purpose is to inspect and ensure that a product is complete, that it respects the customer’s Quality standards and meets the Quality criteria listed in the Product Description.
Note: This technique checks if the product is complete and meets all quality criteria.
It does not include Product Approval, as the person listed in the Quality Register will not sign off until they see the product has been complete. After this, you can say the product is complete and is therefore baselined.
The PRINCE2 Quality Review Technique Roles
The Quality Review technique has four specific roles. The roles are:
I will explain each so that it is easy to remember.
Chair: This role is responsible for chairing the review meetin
Presenter: This role presents the products and represents the producers of the product.
Reviewer: This role reviews the products, submits questions and confirms corrections or improvements.
Administrator: This person provides admin support for the chairperson (e.g., taking minutes and recording results and next actions).
As these are roles, the minimum number of people involved in a Quality Review technique can be two: one person taking the chair & reviewer roles and another taking the presenter and administrator role.
How to prepare for a Quality Review meeting?
The followings tasks can be done to get ready for a Quality Review meeting:
- The chairperson will make arrangements for the review (invite, book room, etc.). They will also ensure that the product is ready for review
- The presenter will distribute copies of the product to the review team with the Product Description
- The reviewers can review the product against the Quality criteria in the Product Description and can also submit a question list to the chair ahead of the Quality review
- The chair will send this question list to the presenter before the review meeting.
I would like to point out the following: The product can be reviewed and the reviewers can already give feedback before the Quality Review meeting. This can give time for the producer or presenter to address this feedback and prepare a response. This makes for a smoother & efficient Quality Review meeting.
How the Quality Review meeting is run?
Here is an overview of how a Quality Review meeting might be run
- Chair would coordinate the introductions
- The presenter would provide a brief product introduction
- Chair will invite each reviewer to ask questions about the product and if any further actions are needed. These are agreed and noted by the administrator
- The presenter can provide a product walk-through. Again, any required actions are agreed and noted
- Towards the end of the meeting, the reviewer will read back the actions and responsibilities
- Lastly, the chair will decide if the product is complete, conditionally complete (means a few actions are yet required) or incomplete (another Quality Review meeting is required).
There are also some follow-up actions after the review such as:
- Carry out the actions that were agreed at the meeting and get these signed off
- The Chair can then note the product as complete
- The next step after the product is completed is to request approval for the product. This is usually a signature from the person listed as approver in the Quality Register.
To summarize, the purpose of the Quality Review technique is to inspect that a product is complete, that the product respects the customer’s quality standards and meets the quality criteria listed in the Product Description, and to identify any actions that are still required.
The PRINCE2 Quality Review Responsibilities
Here are some of the responsibilities relevant to the Quality Theme:
What is the Corporate or Program Management responsible for with regard to Quality?
- Provide details of the Corporate or Program Quality Management System. (They inform the project about the existing Quality systems in place.)
- Provide Quality Assurance to the project.
What is the Senior User responsible for?
- Provide the companies’ Quality Expectations and Acceptance Criteria for the Project Product. This makes sense, as the Senior User is also responsible for the product specifications
- Approve the Project Product Description and Quality Management Strategy. This could also be done by the Executive
- They can also approve the Product Descriptions for key products
- Provide acceptance of the Project Product.
What is the Executive Responsible for?
- They can also approve the Project Product Description & Quality Management Strategy with the Senior User.
What is the Senior Supplier responsible for?
- Provide resources to undertake supplier Quality activities.
What is the Project Manager responsible for?
- Document the customer’s Quality Expectations and Acceptance Criteria. They will work with the Senior User on this
- Prepare the Project Product Description with other persons involved in the project
- Prepare the Quality Management Strategy document, which defines how Quality will be done in the project
- Ensure that the Team Managers implement the Quality Control measures agreed in the Product Descriptions and Work Packages.
What is the Team Manager responsible for?
- Produce products consistent with Product Descriptions
- Advise the Project Manager of the product Quality status.
What is Project Assurance responsible for?
- Advise the Project Manager on the Quality Management Strategy and on suitable reviewers and approvers
- Assure the Project Board members on the implementation of the Quality Management System.
What is Project Support responsible for?
- Provide administrator support for Quality Control
- Maintain Quality Register and the Quality Records