PRINCE2 7 Quality Practice
PRINCE2 7 Quality Practice purpose
The purpose of the quality practice is to document the user’s requirements of the project products and to establish how they will be met.
Quality is concerned with ensuring that the project products meet the user’s requirements and
expectations and enable the desired benefits to be realized.
The quality practice addresses the quality concepts, guidance, techniques, management products, and responsibilities for the project products.
Definition of quality
The degree to which a set of inherent characteristics of a product, service, process,
person, organization, system, or resource fulfils its requirements.
The PRINCE2 7 method includes systematic activities to:
- explicitly confirm the user’s quality expectations and acceptance criteria for the project
- products in the project product description
- identify the project products to the level at which the project can exert control
- define the project products in product descriptions, including the quality specifications by which they will be assessed, the quality techniques to be used in checking their quality, and the quality responsibilities of those involved
- implement and track the quality techniques employed throughout the project.
- Quality should be built into everything; not just tested at the end of the project.
Key quality terminology
PRINCE2 7 uses a specific set of terms to characterize information about the needs of project stakeholders and enable effective quality planning, quality control, and quality assurance.
These terms are:
- user’s quality expectations
- requirements
- acceptance criteria
- quality specifications.
All project stakeholders have expectations of how the project will be performed and of the products
it will deliver.
However, in PRINCE2, the term user’s quality expectations only applies to the
statements found in the project product description.
Similarly, the PRINCE2 7 method distinguishes between needs and expectations that are captured in
an approved management product (such as a product description) and those that are not.
Captured and documented needs or expectations are considered requirements, which constitute part of the project scope.
Needs and expectations that are not captured in an approved management product are not part of the project scope. This distinction is essential to enable effective monitoring and control.
Acceptance criteria are stated in the project product description.
In effect, they are owned by the business, and the project board approves these on behalf of the business. Acceptance criteria are typically described in terms of the functional capabilities the business expects to achieve upon the acceptance of the project products.
Quality specifications are stated in product descriptions.
These are typically both derived from the user’s quality expectations and determined by aspects of the business or operational context.
Operational context could include applicable regulatory requirements or requirements driven by existing policies and practices.
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.
