Project Quality Management
The Quality Management Plan defines the acceptable level of quality, defined by the customer, and describes how the project will ensure this level of quality in its deliverables and work processes.The Quality Management Plan describes the following quality management components:
How to identify Quality requirements of Project's Product/Service/Results.
How to identify the relevant Quality Policies, Quality Objectives of the Organization which is relevant to the Project and its deliverable's.
How to look out and propose process improvements.
Key project deliverables and processes to be reviewed for satisfactory quality level
How the Quality control and assurance activities will be identified.
How the Quality roles and responsibilities will be identified and defined.
How to determine which Quality tools to use. Tools and techniques to be applied
How will the team measure quality and when?
How will Quality reporting be done? Plan for reporting quality control and assurance problems
Roles and responsibilities for quality managementWhat are the types of software testing environments needed?
What will be inspected and tested?
How will defects be tracked and reported?
How will deliverables be validated?
Glossary of quality management terms
Rationale/Purpose
The purpose of developing a quality plan is to elicit the customer’s expectations in terms of quality and prepare a proactive quality management plan to meet those expectations.
Quality Management plans apply to project deliverables and project work processes.
While Project Quality Management applies to all projects, regardless of the nature of their product, Product quality measures and techniques are specific to the particular type of product produced by the project. E.g. Quality management of software products entails different approaches and measures than nuclear power plants, while Project Quality Management approaches apply to both.
The Quality Management Plan helps the project manager determine if deliverables are being produced to an acceptable quality level and if the project processes used to manage and create the deliverables are effective and properly applied.
Quality - Degree to which requirements are fulfilled.
Grade - Features of a product/service/result but not core functionalities.
Balance between Quality and Grade needs to be established. This is usually done by the PM and Project team.
Not meeting Quality requirement could be an issue for project stakeholders.
Not meeting Grade may be ok.
Cell Phone - Quality - Call, Text, Screen
Cell Phone - Grade - Color, Casing