2. Coincides with PMBOK 8.3
Process Group and Knowledge Area Mapping
Knowledge Areas Initiating Planning Process Group Executing Process Group Monitoring and Controlling Process Group Closing Process Group
4. Project Integration
Management
4.1 Develop Project Charter
4.2 Develop Project Management
Plan
4.3 Direct and Manage Project Work
4.4 Manage Project Knowledge
4.5 Monitor and Control Project Work
4.6 Perform Integrated Change Control
4.7 Close Project or Phase
5. Project Scope
Management
5.1 Plan Scope Management
5.2 Collect Requirements
5.3 Define Scope
5.4 Create WBS
5.5 Validate Scope
5.6 Control Scope
6. Project Schedule
Management
6.1 Plan Schedule Management
6.2 Define Activities
6.3 Sequence Activities
6.4 Estimate Activity Durations
6.5 Develop Schedule
6.6 Control Schedule
7. Project Cost Management
7.1 Plan Cost Management
7.2 Estimate Costs
7.3 Determine Budget
7.4 Control Costs
8. Project Quality
Management
8.1 Plan Quality Management 8.2 Manage Quality 8.3 Control Quality
9. Project Resource
Management
9.1 Plan Resource Management
9.2 Estimate Activity Resources
9.3 Acquire Resources
9.4 Develop Team
9.5 Manage Team
9.6 Control Resources
10. Project Communications
Management
10.1 Plan Communications
Management
10.2 Manage Communications 10.3 Monitor Communications
11. Project Risk
Management
11.1 Plan Risk Management
11.2 Identify Risks
11.3 Perform Qualitative Risk Analysis
11.4 Perform Quantitative Risk
Analysis
11.5 Plan Risk Responses
11.6 Implement Risk Responses 11.7 Monitor Risks
12. Project Procurement
Management
12.1 Plan Procurement Management 12.2 Conduct Procurements 12.3 Control Procurements
13. Project Stakeholder
Management
13.1 Identify Stakeholders 13.2 Plan Stakeholder Engagement
13.3 Manage Stakeholder
Engagement
13.4 Monitor Stakeholder Engagement
Control Quality
3. What is it?
Control Quality is the process of monitoring and recording results of
executing the quality management activities in order to assess
performance and ensure the project outputs are complete, correct,
and meet customer expectations.
Why?
The key benefit of this process is verifying that project deliverables
and work meet the requirements specified by key stakeholders for
final acceptance.
Control Quality
Coincides with PMBOK 8.3
4. Control Quality
Coincides with PMBOK 8.3
Inputs Tools & Techniques Outputs
1. Project management plan
• Quality management
plan
2. Project documents
• Lessons learned register
• Quality metrics
• Test and evaluation
documents
3. Approved change requests
4. Deliverables
5. Work performance data
6. Enterprise environmental
7. factors
8. Organizational process assets
1. Data gathering
• Checklists
• Check sheets
• Statistical sampling
• Questionnaires and surveys
2. Data analysis
• Performance reviews
• Root cause analysis
3. Inspection
4. Testing/product evaluations
5. Data representation
• Cause-and-effect diagrams
• Control charts
• Histogram
• Scatter diagrams
6. Meetings
1. Quality control measurements
2. Verified deliverables
3. Work performance information
4. Change requests
5. Project management plan
updates
• Quality management plan
6. Project documents updates
• Issue log
• Lessons learned register
• Risk register
• Test and evaluation
documents
Inputs, Tools & Techniques, Outputs
5. Coincides with PMBOK 8.3
8.3 Control
Quality
Project
Management
Plan
Enterprise/Orga
nization
• Change Requests
• Quality management plan
• Enterprise
Environmental Factors
• Organizational process
assets
Project
Documents
• Lessons learned register
• Quality metrics
• Test and evaluation
documents
Control Quality
4.6 Perform
Integrated
Change Control
• Deliverables
• Work Performance
Data
Project
Management
Plan
4.5 Monitor and
Control Project
Work
• Work Performance Information
Project
Documents
4.6 Perform
Integrated
Change Control
• Issue log
• Lessons learned register
• Quality control measurements
4.3 Direct and
Manage Project
Work
• Approved Change
Requests
• Risk register
• Test and evaluation documents
• Quality management plan
5.5 Validate
Scope
• Verified Deliverables
6. Overview
Coincides with PMBOK 8.3
Control Quality
Control Quality involves activities such as:
• Measuring all steps, attributes, and variables used to verify conformance or
compliance to the specifications stated during the planning stage.
• Quality control should be performed throughout the project to formally
demonstrate, with reliable data, that the sponsor’s and/or customer’s acceptance
criteria have been met.
• In Agile projects, the Control Quality activities may be performed by all team
members throughout the project life cycle.
• In waterfall model-based projects, the quality control activities are performed at
specific times, toward the end of the project or phase, by specified team members.
7. Control Quality - Inputs
Coincides with PMBOK 8.3
Project Management Plan
Project management plan components include but are not limited to the
quality management plan. The quality management plan defines how
quality control will be performed within the project.
8. Coincides with PMBOK 8.3
Project Documents
Project documents that can be considered as inputs for this process include:
• Lessons learned register
• Quality metrics
• Test and evaluation documents
Control Quality - Inputs
9. Coincides with PMBOK 8.3
Approved Change Requests
As part of the Perform Integrated Change Control process, a change log update
indicates that some changes are approved and some are not. Approved change
requests may include modifications such as defect repairs, revised work methods, and
revised schedules. Partial change completion may result in inconsistencies and later
delays due to incomplete steps or corrections. The implementation of approved
changes should be verified, confirmed for completeness, retested, and certified as
correct.
Control Quality - Inputs
10. Coincides with PMBOK 8.3
Deliverables
A deliverable is any unique and verifiable product, result, or capability to perform a
service that is required to be produced to complete a process, phase, or project.
Deliverables that are outputs from the Direct and Manage Project Work process are
inspected and compared to the acceptance criteria defined in the project scope
statement.
Control Quality - Inputs
11. Coincides with PMBOK 8.3
Work Performance Data
Work performance data contains data on product status such as
observations, quality metrics, and measurements for technical
performance, as well as project quality information on schedule
performance and cost performance.
Control Quality - Inputs
12. Coincides with PMBOK 8.3
Enterprise Environmental Factors
The enterprise environmental factors that can influence the Control Quality process
include:
• Project management information system
• quality management software can be used to track errors and variations in
processes or deliverables
• Governmental agency regulations
• Rules, standards, and guidelines specific to the application area
Control Quality - Inputs
13. Coincides with PMBOK 8.3
Organizational Process Assets
The organizational process assets that can influence the Control Quality process
include:
• Quality standards and policies
• Quality templates, for example, check sheets, checklists, etc
• Issue and defect reporting procedures and communication policies
Control Quality - Inputs
14. Data Gathering
Data-gathering techniques that can be
used for this process include:
• Checklists
• Check sheets
• Statistical sampling
• Questionnaires and surveys
Coincides with PMBOK 8.3
Control Quality – Tools & Techniques
Check Sheets Example
15. Data Analysis
Data analysis techniques that can be used for this process include:
• Performance reviews
• Root cause analysis
Coincides with PMBOK 8.3
Control Quality – Tools & Techniques
16. Inspection
An inspection is the examination of a work product to determine if it conforms to
documented standards. The results of inspections generally include measurements
and may be conducted at any level. The results of a single activity can be inspected, or
the final product of the project can be inspected. Inspections may be called reviews,
peer reviews, audits, or walkthroughs. In some application areas, these terms have
narrow and specific meanings. Inspections also are used to verify defect repairs.
Coincides with PMBOK 8.3
Control Quality – Tools & Techniques
17. Testing/Product Evaluation
Testing is an organized and constructed investigation conducted to provide objective
information about the quality of the product or service under test in accordance with
the project requirements. The intent of testing is to find errors, defects, bugs, or other
nonconformance problems in the product or service. Tests can be performed
throughout the project, as different components of the project become available, and
at the end of the project on the final deliverables.
Coincides with PMBOK 8.3
Control Quality – Tools & Techniques
18. Data Representation
Data representation techniques that can be used for this process include:
• Cause-and-effect diagrams
• Control charts
• Histogram
• Scatter diagrams
Coincides with PMBOK 8.3
Control Quality – Tools & Techniques
19. Meetings
The following meetings may be used as part of the Control Quality process:
• Approved change requests review.
• Retrospectives/lesson learned. A meeting held by a project team to discuss:
Successful elements in the project/phase
What could be improved
What to incorporate in the ongoing project and what in future projects
What to add to the organization process assets
Coincides with PMBOK 8.3
Control Quality – Tools & Techniques
20. Coincides with PMBOK 8.3
Quality Control Measurements
Quality control measurements are the documented results of Control Quality
activities. They should be captured in the format that was specified in the quality
management plan.
Control Quality – Outputs
21. Coincides with PMBOK 8.3
Verified Deliverables
A goal of the Control Quality process is to determine the correctness of deliverables.
The results of performing the Control Quality process are verified deliverables that
become an input to the Validate Scope process for formalized acceptance. If there
were any change requests or improvements related to the deliverables, they may be
changed, inspected, and reverified.
Control Quality – Outputs
22. Coincides with PMBOK 8.3
Work Performance Information
Work performance information includes information on project requirements
fulfillment, causes for rejections, rework required, recommendations for corrective
actions, lists of verified deliverables, status of the quality metrics, and the need for
process adjustments.
Control Quality – Outputs
23. Coincides with PMBOK 8.3
Change Requests
If changes occur during the Control Quality process that may impact any of the
components of the project management plan or project documents, the project
manager should submit a change request. Change requests are processed for review
and disposition through the Perform Integrated Change Control process.
Control Quality – Outputs
24. Coincides with PMBOK 8.3
Project Management Plan Updates
Any change to the project management plan goes through the organization’s change
control process via a change request. Components that may require a change request
for the project management plan include but are not limited to the quality
management plan.
Control Quality – Outputs
25. Coincides with PMBOK 8.3
Project Document Updates
Project documents that may be updated as a result of carrying out this process
include
• Issue log
• Lessons learned register
• Risk register
• Test and evaluation documents
Control Quality – Outputs
Editor's Notes
This process is performed throughout the project.
The Control Quality process determines if the project outputs do what they were intended to do. Those outputs need to comply with all applicable standards, requirements, regulations, and specifications.
The Control Quality process is performed to measure the completeness, compliance, and fitness for use of a product or service prior to user acceptance and final delivery.
This is done by measuring all steps, attributes, and variables used to verify conformance or compliance to the specifications stated during the planning stage.
The level of effort to control quality and the degree of implementation may differ between industries and project management styles; in pharmaceutical, health, transportation, and nuclear industries, for example, there may be stricter quality control procedures compared to other industries, and the effort needed to meet the standards may be extensive.
Agile projects, the Control Quality activities may be performed by all team members throughout the project life cycle.
In waterfall model-based projects, the quality control activities are performed at specific times, toward the end of the project or phase, by specified team members.
Lessons learned register - Lessons learned earlier in the project can be applied to later phases in the project to improve quality control.
Quality metrics - A quality metric specifically describes a project or product attribute and how the Control Quality process will verify compliance to it.
Test and evaluation documents - Test and evaluation documents are used to evaluate achievement of the quality objectives.
Checklists - Checklists help in managing the control quality activities in a structured manner.
Check sheets. Check sheets are also known as tally sheets and are used to organize facts in a manner that will facilitate the effective collection of useful data about a potential quality problem.
Statistical sampling. Statistical sampling involves choosing part of a population of interest for inspection (for example, selecting 10 engineering drawings at random from a list of 75).
Questionnaires and Surveys. Surveys may be used to gather data about customer satisfaction after the deployment of the product or service.
Performance reviews measure, compare, and analyze the quality metrics defined by the Plan Quality Management process against the actual results.
Root cause analysis is used to identify the source of defects.
Early testing helps identify nonconformance problems and helps reduce the cost of fixing the nonconforming components.
Different application areas require different tests. For example, software testing may include unit testing, integration testing, black-box, white-box, interface testing, regression testing, Alpha testing, etc.
In construction projects, testing may include cement strength, concrete workability test, nondestructive tests at construction sites for testing the quality of hardened concrete structures, and soil tests. In hardware development, testing may include environmental stress screening, burn-in tests, system testing, and more.
Cause-and-effect diagrams - Cause-and-effect diagrams are used to identify the possible effects of quality defects and errors.
Control charts - Control charts are used to determine whether or not a process is stable or has predictable performance.
Histograms - Histograms can demonstrate the number of defects by source or by component.
Scatter diagrams - Scatter diagrams can show the planned performance on one axis and the actual performance on the second axis.
Approved change requests review - All approved change requests should be reviewed to verify that they were implemented as approved. This review should also check that partial changes are completed and all parts have been properly implemented, tested, completed, and certified.
Issue log - Many times a deliverable that does not meet the quality requirements is documented as an issue.
Lessons learned register - The lessons learned register is updated with information on the source of quality defects and how they could have been avoided as well as approaches that worked well.
Risk register - New risks identified during this process are recorded in the risk register and managed using the risk management processes.
Test and evaluation documents - Test and evaluation documents may be modified as a result of this process in order to make future tests more effective.
