The PRINCE2 Product Description – Part 4
The PRINCE2 Quality review technique, and other quality inspection techniques, can yield substantial side benefits particularly in terms of:
Stakeholder engagement
Quality inspections are opportunities for effective cross functional communication.
Many important stakeholders may only have direct contact with the project through these reviews, so they provide a window into The project.
This is particularly true for users. Structured quality inspections are among the most effective ways of encouraging buy-in to the project. Generally, the more systematic and affected the reviews, the better the impression for the stakeholders.
Leadership
In many circumstances a focus on quality as in fitness for purpose, elicits a better response for review team members and users than simply by focusing on budgets and schedules.
Quality inspection techniques often provide excellent tips and soft guidance on effective behaviour and decision making in meetings.
Team building
Formal and informal quality inspections are opportunities to focus on building an effective project team, where members understand Each other’s contributions, needs and priorities.
Developing individuals
New starters learn from more experience personnel and sports commissions that others take for granted. Experienced personnel learn from the fresh perspectives bought by newcomers.
Quality documentation
Consistent and familiar quality records make for improvements in communication and in the analysis of quality metrics.
Quality culture
The PRINCE2 Quality Review Techniques Is generic. It can be employed on programmes, projects and services throughout an organization, resulting in a positive and familiar quality culture.
Quality records
It is important that evidence is gathered to demonstrate that the planned quality activities have been carried out. The records support entries in the quality register by providing the project manager and the project board with assurance that:
- Product really are complete and consequently that the related activities are finished
- Products have met their associated quality criteria and are fit for their intended purpose is. Alternatively, there are records of any quality failures and corrective action
- The agreed processes have been observed
- Approval authorities and key product stakeholders are satisfied
- Planned audits have been conducted and reported
Quality records should include references to the quality inspection documentation, such as a test plan; details of any defect statistics and actions required to correct errors and omissions of the products inspected; and any quality related reports for example an audit.
When these records are received by project support, the quality register entries for the relevant products Can be completed.
During the project and at project closure, the quality records provide a valuable source of information for analysis in accordance with the PRINCE2 Principle that projects should learn from experience.
For example, quality metrics, such as defect and trends, can be used as a source for lessons learned and process improvements.
Approval records
Where quality records provide evidence by each product has met its requirements as specified in its product description, is good practice to obtain a record that the product has been approved.
PRINCE2 does not specify the format or composition of approval records as these will depend on the level of formality required, the customer/Supplier relationship and the quality management system of the organization involved.
The format for approval records Could include, for example, and note in the minutes of a meeting, and e-mail, a letter, a signature on a document, or a certificate.
Acceptance records
Products are approved throughout the life of the project and ownership may even be transferred to the customer as part of a phased handover.
But, during the closing a project process, it is important to check that all forms of approval have been obtained and records kept for audit and/or Contractually purposes.
PRINCE2 It uses the term acceptance to describe the ultimate approval of the projects products.
Acceptance is frequently required for more than one set of stakeholders. An example of those using the projects products and those maintaining them in which case both categories of stakeholder should have been involved in defining the relevant products, participating in quality inspections and granting approval during the course of the project.
Acceptance may be qualified, and documented concessions can be granted. An example is if there are faults in the solution and some performance criteria has not been fully achieved.
Where concessions have been granted by the project board, it may be necessary to recommend follow on actions for later improvements or remedies for the products concerned.
This course is DEPRECATED
The old PRINCE2 6th Edition Foundation and Practitioner syllabus was upgraded in 2024. Check out the brand NEW PRINCE2 7th Edition Masterclass, covering all the current syllabus, training material and online exam benefits HERE
Your Route To PRINCE2 6th Edition Practitioner
Study PRINCE2 6 Foundation and Practitioner Exams with our famous on-line course with streaming HD Video Lessons, study guides and mock exams. In the last fifteen years we have had 6,000+ Academy students successfully transform their careers as PRINCE2 Practitioners.
