Project quality plan PQP

Project quality plan PQP

The term ‘quality assurance’ describes a set of planned, systematic actions to ensure that products and services comply with specified requirements. It not only involves checking the final quality of products to avoid defects, as is the case in quality control, but also checking product quality in a planned way through all the production stages. It is the development of work and product design procedures to prevent errors from occurring in the first place, based on planning, backed up by quality manuals and tools.

A project quality plan (PQP), sometimes referred to as a quality management plan, quality assurance plan or project quality management plan, is a project-specific quality plan that describes the activities, standards, tools and processes necessary to achieve quality in the delivery of a project.

It is sometimes considered to be interchangeable with the project execution plan (PEP) which sets out the overall strategy for managing the project, describing who does what and how, and defining the policies, procedures and priorities that will be adopted.

RIBA suggest that the PEP or PQP helps track and control projects which can progress erratically and intermittently and should pass the ‘what happens if ‘Fred’ is knocked-down by a bus’ test, describing the project and processes in such a way that competent people could take over the project and maintain the program, service and performance.

However, on large projects, the project execution plan might be an overarching document that includes (or references) a number of more detailed plans focusing on specific issues such as; the project quality plan, health and safety plan, risk management plan, value management plan, stakeholder management plan, and so on.

For more information, see Project Execution Plan.

The project quality plan should:

Some of these elements may be common to all projects, however, the PQP should not duplicate information that is available elsewhere (but rather should reference it), and it should be project specific, rather than an a generic box-ticking exercise.

edit]