QUALITY MANAGEMENT PLAN

This template can be modified to meet a project’s specific needs. See example content below in gray. To use: 1)
download template 2) delete examples 3) input specific project information.

Project Title: Agile Projects Date Prepared: March 3, 20209/2019

Quality Standards (Identify the key project areas that can influence the Manage Quality process)

Software Quality, Standards, Quality Management

Quality Objectives: (Identify and describe the different project measurements that might impact
quality)

Metric or Specification Measure

1. Software Test Requirements 1. Clear, concise and unambiguous

requirements that leave no room for different
interpretations between the different
stakeholders: developers, testers and business
analysts
2. Unit Testing 2. Code peer review and unit test cases to
validate component during development
3. Defect Density 3. Average number of defects / bugs per KLOC
(thousand lines of code) for the software
module / application / product
4. Incomplete / Failed User Stories 4. Number of user stories in an Agile Sprint that
were not “accepted” and done at the end of the
Sprint.

Quality Roles and Responsibilities: (Identify and describe the various key roles of project stakeholders
who could have specific input into ensuring a project’s quality)

Roles Responsibilities

1. Project Manager 1. Ensures effective quality management which

2. Software Development Team
includes a a) quality plan that includes the
processes, metrics and standards b)
performance of quality assurance that results in
corrective actions, actionable process
improvement c) quality control via testing
throughout the cycle to meet product quality
requirements
2. Incorporate best practices during the
software development cycle – code peer

3. Business User / Customer
reviews and unit / integration/functional testing
during the development phase, b) system /
regression / performance testing during the
quality assurance phase c) Provide sign off for
the software release
3. a) Provide clear requirements, support during
review and approval of the quality testing
scope, approach and plan b) perform user
acceptance/alpha/beta testing and provide
feedback c) Approve remediation plan for
unresolved issues prior to release

Deliverables and Processes Subject to Quality Review: (Identify key project deliverables and
processes that are critical to Managing Quality)

Deliverables Processes

Quality Management Plan, Quality Metrics, Data gathering, data analysis, data
Quality Processes and Checklists, Corrective representation, review meetings, deliverables
Actions and Recommendations, Process walkthroughs, feature / functionality demos,
Improvement Plan, Quality Baseline change request, change management

Quality Management Approach: (Provide an overview of the various components inherent in a

successful Quality Management approach)

a) Define the way quality will be implemented (quality management plan), b) Define and
document how quality will be assured during the implementation of the project (quality
metrics, risk registers, issue logs, quality reports) c) Resources, processes needed to
ensure the defined quality is delivered (check lists, data analysis, audits) d) Adherence to
the quality standards and policies that are defined and in place at the organization e)
Continuous improvement and evolvement of the project quality management plan
throughout the implementation of the project.

Quality Control Approach: (Provide an overview of the various components inherent in a successful
Quality Control approach)

a) Data gathering using checklists, surveys and questionnaires b) Monitoring, recording and
analysis of results of the testing c) Data analysis via root cause analysis, reviews d) Utilize
organization’s best practices and process assets, project risk register, organization’s
lessons learned register during quality control management
 Applicable Quality Procedures: (Describe any additional Quality Procedures that might apply to this
project)

 Early and continuous delivery of software

 Frequent delivery of working solutions
 Continuous improvement to fine-tune processes
 Using test-driven development process (TDD), for example paired testing
 Tracking of defects by severity/defect management
 Accepting of new requirements at any stage in the development process
 Establishing success criteria
 Integration of QA testing throughout the development process
 End-to-end testing of product functionality
 Determining if product works as expected
 Using a professional tester to determine if unexpected user behavior will cause problems

Adapted from C. S. Dionisio’s book, A Project Manager’s Book of Forms: A Companion to the
PMBOK® Guide – Sixth Edition (3rd ed.), for PMIstandards+™ with contributions from Nara
Acharya, PMP®, CSM®, SAFe®, Agilist ©PROJECT MANAGEMENT INSTITUTE, INC.