Plan Quality Management in project management is the process of figuring out what quality standards ( template ) and requirements the project and its outputs need to meet and writing down how the project will show that it meets those standards and requirements. This process’s main benefit is that it tells you how to handle and check quality throughout the project. This step is either done only once or at set times during the job. Figure below shows what goes into and comes out of this process.
Planning for quality should happen at the same time as other planning tasks. For example, if you want to make changes to the products to meet certain quality standards, you might need to change the costs or the schedule and do a full risk analysis of how these changes will affect your plans.
Plan Quality Management: Inputs
Project Charter
The project charter gives an overview of the project and what the final result will be like. It also has the standards for project approval, measurable project goals, and success criteria that will affect how the project is managed in terms of quality.
Project Management Plan
The following are some of the parts of a project management plan:
Requirements management plan
For finding, analyzing, and handling requirements, the quality management plan and quality metrics will use the requirements management plan.
Risk management plan
The risk management plan lays out how to find problems, analyze them, and keep an eye on them. The information in the quality management plan and the risk management plan work together to make sure that the project and product are good.
Stakeholder engagement plan
The stakeholder engagement plan lays out how to record the wants and expectations of the stakeholders, which are what quality management is based on.
Scope baseline
It looks at the WBS and the deliverables listed in the project scope statement to decide which quality standards and goals are right for the project and which products and processes will be quality reviewed. The factors for accepting the deliverables are in the scope statement. The acceptance criteria description could make quality costs and, by extension, project costs go up or down by a large amount. When all acceptance factors are met, it means that all stakeholders’ needs have been met.
Project Documents
It’s possible to use the following project documents as inputs for this process:
Assumption log
The assumption log lists all the assumptions and limits that apply to meeting quality standards and requirements.
Requirements documentation
Documenting objectives lists the things that the project and product must do to meet the needs of stakeholders. Project and product quality standards are just a few of the things that make up the requirements documentation. The project team uses the requirements to help them plan how to keep quality high on the project.
Requirements traceability matrix
The requirements traceability matrix helps make sure that all the requirements in the requirements documentation are checked and connects product requirements to deliverables. The matrix shows a summary of the tests that need to be done to make sure the standards are met.
Risk register
The risk register has details about threats and chances that could affect quality standards.
Stakeholder register
With a focus on the wants and expectations of the customer and project sponsor, the stakeholder register helps to find those stakeholders who have a direct interest in or effect on quality.
Enterprise Environmental Factors
Along with other things, the following things in the Enterprise Environmental Factors can affect the Plan Quality Management (template )process:
- Rules made by government agencies;
- Rules, rules, and guidelines that are specific to the area of application;
- Geographic distribution;
- Organizational structure;
- Marketplace conditions;
- Working or operating conditions of the project or its deliverables; and
- Cultural perceptions.
Organizational Process Assets
The following are some examples of organizational assets that can have an effect on the Plan Quality Management process:
- Quality management method for an organization that includes rules, policies, and procedures;
- Solid templates, like check sheets, a traceability matrix , and others; and
- There are historical records and a repository for lessons learned.
Plan Quality Management: Tools And Technique
Expert Judgment
You should look at the information and experience of people or groups who are experts in the following areas:
- Quality assurance,
- Quality control,
- Quality measurements,
- Quality improvements, and
- Quality systems.
Data Gathering
For this process, you can use the following data-gathering methods, but they are not limited to them:
Benchmarking
Comparing a project’s planned or real practices or quality standards to those of similar projects can help you find the best ways to do things, come up with ways to make things better, and give you a way to measure performance. Benchmarked projects can be from the same application area or a different one, and they can be from the same company or a different one. Through benchmarking, it is possible to draw comparisons between projects in different businesses or use cases.
Brainstorming
Brainstorming is a creative way to get information from a group of team members or experts in the field so that you can make the best quality management plan (template )for the next project.
Interviews
You can find out what people need and expect from the quality of a project or product, whether they say it out loud or not, in an official or informal setting, by talking to experienced project participants, stakeholders, and subject matter experts. People should feel safe and secure during interviews so that they are more likely to give honest and fair information.
Data Analysis
For this task, you can use data analysis methods such as, but not limited to:
Cost-benefit analysis.
You can use a cost-benefit analysis to figure out which option is best for you by comparing its pros and cons. The project manager can use a cost-benefit analysis to see if the planned quality tasks are worth the money. Less rework, higher productivity, lower costs, higher stakeholder satisfaction, and higher profitability are the main benefits of meeting quality standards. Cost-benefit analysis looks at the expected benefit versus the cost of each quality action.
Cost of quality.
Costs of quality (COQ) for a project include at least one of the ones below:
- Prevention costs : Costs that come with making sure that the products, deliverables, or services for a certain job are of good quality.
- Appraisal costs : These are the costs of checking, measuring, auditing, and testing the project’s deliverables, goods, or services.
- Failure costs (internal/external) : Costs that come up when the products, deliverables, or services don’t meet the needs or expectations of the stakeholders.
Decision Making
If you need to make decisions in this situation, you can use a decision-making method like multicriteria decision analysis. You can use multicriteria decision analysis tools, like a prioritization matrix, to figure out what the most important issues are and how to rank the best possible solutions before making a choice. It is necessary to rank and weight the criteria before applying them to all the options in order to get a numerical score for each one. Next, the options are ranked by how well they did. It can help find the most important quality metrics when used in this way.
Data Representation
quality management plan( template ) process can use a number of different data representation methods, such as :
Flowcharts
People sometimes call flowcharts “process maps” because they show the order of steps and the different ways that a process can go from one or more inputs to one or more outputs. By mapping the operational details of processes that are part of a horizontal value chain, flowcharts show the activities, decision points, branching loops, parallel paths, and the overall order of processing. For example, a SIPOC model lists vendors, inputs, process, outputs, and customers.
Flowcharts can help you understand and guess how much it will cost to make a process good. Find out how much the expected conformance and nonconformance work will cost by using the workflow branching reasoning and the relative frequencies that go with it. When flowcharts are used to show the steps in a process, they are sometimes called process flows or process flow diagrams. They can be used to improve the process or find places where quality problems could happen or where quality checks should be added.
Logical data model
By using business words and not relying on a specific technology, logical data models show an organization’s data in a visual way. The logical data model can help you figure out where problems with data security or other quality can happen.
Matrix diagrams
Through the rows and columns that make up the matrix, you can see how strong the connections are between the different factors, reasons, and goals. Project managers can use different types of matrix diagrams based on the number of things they need to compare. These include L, T, Y, X, C, and roof-shaped diagrams. In this process, they help figure out the most important quality measures for the
Mind mapping
If you want to organize your ideas clearly, you can use mind mapping. People often make a mind map about quality by drawing an image of a single quality idea in the middle of a blank landscape page. They then add pictures, words, and parts of words that go with that idea. Mind-mapping might help you quickly come up with the quality standards, limits, dependencies, and relationships for a project.
Test And Inspection Planning
The project manager and the project team figure out how to test or inspect the deliverable, service, or product to meet the needs and demands of all stakeholders and to meet the goal for the product’s performance and dependability. These checks and tests rely on the industry. In software projects, they might be alpha and beta tests, in construction projects they might be strength tests, in manufacturing they might be inspections, and in engineering they might be field tests and nondestructive tests.
Meetings
To make the quality management plan, project teams may get together to plan. The project manager, the project sponsor, certain project team members, certain clients, anyone in charge of project quality management, and others as needed can all be there.
Plan Quality Management: Outputs
Quality Management Plan
The quality management plan is part of the project management plan. It explains how the policies, processes, and guidelines will be followed to meet the quality goals. It lists the things the project management team needs to do and the tools they need to get them done so the project meets its quality goals.
The plan for quality control can be formal or casual, specific or general. The needs of the project decide the style and level of detail of the quality management plan (template ) . Reviewing the quality management plan early on in the project will help make sure that choices are based on correct data. As a result of this review, the project’s value proposition may become clearer, costs may go down, and plan delays caused by rework may happen less often.
The following parts may be part of the quality management plan, but are not required to be:
- Quality standards that will be used by the project;
- Quality objectives of the project;
- Quality roles and responsibilities;
- Project deliverables and processes subject to quality review;
- Quality control and quality management activities planned for the project;
- Quality tools that will be used for the project; and
- Major steps that are important to the project, like how to deal with nonconformance, take appropriate actions, and keep improving.
Quality Metrics
An important part of the Control Quality method is making sure that a project or product meets certain standards. A quality metric spells out those standards in detail. As an example of quality metrics, the failure rate, the number of defects found each day, the total amount of downtime each month, the number of errors found per line of code, the percentage of requirements covered by the test plan, and the percentage of customer satisfaction scores are all examples of quality metrics.
Project Management Plan Updates
People in the company have to fill out a change request for any changes they want to make to the project management plan. The following parts of the project management plan may need a change request:
Risk management plan
The agreed-upon way of managing project risk may need to be changed if decisions about the quality management method are made. These changes will be written down in the risk management plan.
Scope baseline
If certain quality management tasks need to be added, the scope standard may change as a result of this process. The WBS dictionary also has a list of quality standards that might need to be changed.
Project Documents Updates
Because of this method, project documents like, but aren’t limited to, the following may be updated:
Lessons learned register
Problems that came up during the quality planning process are written down in the lessons learned register.
Requirements traceability matrix
The requirements traceability matrix keeps track of the quality requirements that this method sets.
Risk register
As quality management plan( template ) process goes on, any new risks that are found are written down in the risk register and managed using the risk management methods.
Stakeholder register
As a result of this process, more information about current or new stakeholders is gathered and added to the stakeholder register.
References :