Plan Quality Management Process

In the planning process of Quality Management, the main goal is to create a plan that shows how to manage and confirm quality throughout the project. In this process, we define the quality standards of the project, take into account the scope of the project, the risks, and requirements that it contains, and thus reducing outputs with defects and therefore we prevent the repetition of these errors.

The plan quality management process provides guidance on how to manage quality and how to decide whether quality requirements are met. The quality criteria required for the project to be successful are determined and archived through the planning process of quality management.

Quality management must be rigorously plated, as the final success of the project depends on the delivery achieved to meet the quality criteria set by the customer. The process of plan quality management, which is part of the planning process group, is located in the knowledge area of quality management. The quality management plan is created in a predefined point in the planning phase. It is updated throughout the project.

The main outputs created at the end of the project are the quality management plan and quality metrics.

What is the quality management plan?

The quality management plan is a subsidiary plan of the project management plan used for planning to satisfy the determined quality requirements of the project and defining the methodology to conduct efficient quality management. Additionally, the quality management plan documents how the project will prove compliance with the quality requirements.

Inputs to the creating quality management plan process

  • Project charter: This have lots of high level information to be used in planning quality management.
  • Requirements management plan: In order to know what quality requirements are, we need to have an approach to collecting requirements. This approach is also present in the requirements management plan.
  • Risk management plan: Risks are closely related with quality requirements, so this plan is an input together with the risk register.
  • Requirements traceability matrix and requirements documentation: These two are the most important inputs of the plan quality management process. Requirements are the main things that compose the quality. 
  • Risk register: As we said before, risks can bring some quality requirements so it is important to take this document into consideration.
  • Stakeholder engagement plan: Provides the quality expectations of the stakeholders and the way to meet these expectations.
  • Scope baseline: This includes acceptance criteria which is vital for the meeting the requirements. Scope baseline also has almost all information about the requirements of the product, so it is a must to take this as an input.
  • Assumption log: Assumptions and constraints may have influence over quality of the project.
  • Stakeholder register: Helps us to know stakeholders who are more prone to be affected by quality issues. It is also useful to manage their expectations.
  • Enterprise environmental factors: The structure of the organization, the conditions of the market, regulations of the government are examples of EEF.
  • Organizational process assets: The quality management system of the organization if it exists, processes, procedures and guides used by the organization, specific quality templates used by the organization such as check sheets, traceability matrix, etc and lessons learned from previous projects.

Tools & Techniques

  • Cost of quality: Any investment that needs to be made to comply with quality requirements and any costs resulting from failure to meet quality requirements should be considered and calculated as quality costs.
  • Cost-benefit analysis: In order to compare the expected benefit to the cost of quality a cost-benefit analysis should be conducted. The amount of spendable money is the limit of the quality objectives in any project.
  • Meetings: To develop the quality management plan according to the project's maturity, the project team should make meetings often.
  • Multicriteria decision analysis
  • Flowcharts
  • Test and inspection planning
  • Logical data model
  • Benchmarking
  • Brainstorming
  • Interviews
  • Matrix diagrams
  • Mind mapping
  • Expert judgment