Project Quality Management (PQM) is defined as the process through which quality is managed throughout the project. However, what constitutes 'Quality' varies to some extent by the client's expectation of the project deliverables which can carry a broad spectrum of requirements.
This blog post seeks to offer an understanding of what PQM is and how it compliments the Project Management Body of Knowledge (PMBOK) in the delivery of given projects.
In PQM there are three distinct phases that require consideration. They being:
1, Quality Management Planning.
This requires a thorough understanding of the 'Statement of Requirements' for a project, the project charter, the applicable standards, legislation and regulations that are to be applied, stakeholder and expectation mapping, and where such undertakings fall within classified boundaries, the Quality Grades to be applied.
2, Quality Assurance.
The level of inputs for Assurance depends on the type, value, size and stakeholders for a given project. For high value, high risk, and highly regulated projects (e.g. Nuclear, Defence, Energy, Infrastructure) one will find a Quality Strategy Document, an Audit Strategy and Schedule, a series of Phase Quality Plans, Risk Strategy and Register, Issues Log, Change Index and many other key management tools that exist within the PMBOK, Prince2 Guidance, and the Quality Management Body of knowledge. In addition there should be explicit guidance in addressing Non-Conformance as an when such events arise.
3. Quality Control
Here the project is measured and monitored against key attributes that are defined in the Project Management Plan (PMP), the Quality Strategy, bespoke company procedures and compliance to international standards and regulations as applicable.
These three phases are seen as the essential foundations to any project and help ensure that the SoR's are met and serve to mitigate any adverse events that could affect stakeholder expectation and value. In developing the Quality Management Plan care should be taken to ensure that the following is well defined:
- The effective implementation of the Quality Policy throughout the project lifecycle
- The method of Project Assurance to all stakeholders
- The Project Resource Planning throughout the complete project lifecycle whilst being aware that the requirements throughout the project remain dynamic
- The method of dealing with in-flight emergent issues without detriment to the baseline expectations of the project
- Alignment to defined cost profiles by way of delivery validation and verification
This blog post seeks to offer an understanding of what PQM is and how it compliments the Project Management Body of Knowledge (PMBOK) in the delivery of given projects.
In PQM there are three distinct phases that require consideration. They being:
1, Quality Management Planning.
This requires a thorough understanding of the 'Statement of Requirements' for a project, the project charter, the applicable standards, legislation and regulations that are to be applied, stakeholder and expectation mapping, and where such undertakings fall within classified boundaries, the Quality Grades to be applied.
2, Quality Assurance.
The level of inputs for Assurance depends on the type, value, size and stakeholders for a given project. For high value, high risk, and highly regulated projects (e.g. Nuclear, Defence, Energy, Infrastructure) one will find a Quality Strategy Document, an Audit Strategy and Schedule, a series of Phase Quality Plans, Risk Strategy and Register, Issues Log, Change Index and many other key management tools that exist within the PMBOK, Prince2 Guidance, and the Quality Management Body of knowledge. In addition there should be explicit guidance in addressing Non-Conformance as an when such events arise.
3. Quality Control
Here the project is measured and monitored against key attributes that are defined in the Project Management Plan (PMP), the Quality Strategy, bespoke company procedures and compliance to international standards and regulations as applicable.
These three phases are seen as the essential foundations to any project and help ensure that the SoR's are met and serve to mitigate any adverse events that could affect stakeholder expectation and value. In developing the Quality Management Plan care should be taken to ensure that the following is well defined:
- The effective implementation of the Quality Policy throughout the project lifecycle
- The method of Project Assurance to all stakeholders
- The Project Resource Planning throughout the complete project lifecycle whilst being aware that the requirements throughout the project remain dynamic
- The method of dealing with in-flight emergent issues without detriment to the baseline expectations of the project
- Alignment to defined cost profiles by way of delivery validation and verification