Quality Management Plan

This guide provides a template and guide for developing a Project Quality Management Plan for medium projects. It includes methodologies, standards, quality review, and output quality control. The plan is developed to ensure that the project is managed in accordance with relevant methodologies and standards, and that project outputs are 'fit for purpose'.

Quality Management Plan
(Medium Projects)
Template and Guide
Version 1.0 April 2009
This guide is intended to be read in conjunction with the following template for the development of a Project
Quality Management Plan for medium projects. As such the Guide should be removed from the front of the
final document.
A template for a Quality Management Plan for a large project has also been developed. This is available at
www.egovernment.tas.gov.au.
The project management templates are being continuously improved. Feedback on suggested improvements
to this Template would be appreciated, and may be made to IAPPU by emailing
[e-mail].
DISCLAIMER
This material has been prepared for use by Tasmanian Government agencies and Instrumentalities. It
follows that this material should not be relied upon by any other person. Furthermore, to the extent that ‘this
material is relied upon’, the Crown in Right of the State of Tasmania gives no warranty as to the accuracy or
correctness of the material or for any advice given or for omissions from the material. Users rely on the
material at their own risk.
Inter Agency Policy and Projects Unit
Department of Premier and Cabinet

What is a Project Quality Management
Plan?
Planning for quality management in a
project increases certainty and reduces
the risk of project failure attributable to
inadequate project management
processes that result in outputs failing to
meet defined and agreed standards. A
Project Quality Management Plan is a
formal framework that defines the project
management processes that will be
applied to ensure that the project is
managed in accordance with relevant
methodologies and standards so that the
delivery of project outputs can be
confirmed by the Steering Committee as
‘fit for purpose’.
Why would you develop a Project
Quality Management Plan?
A Project Quality Management Plan is
developed to provide:
 An overview of the quality
methodologies and standards to be
adopted in managing the project and
in the production of the outputs;
 Agreed processes for the
management of changes, problems,
issues and incidents that emerge
during the production of the outputs;
 Confirmation of the roles and
responsibilities of relevant parties in
the project’s governance structure in
the production of the outputs.
 The project’s Steering Committee
with a documented framework to
ensure the production of quality
project outputs and the application
of quality project management
processes.
The document expands upon details
provided in the Project Business Plan that
provides detailed definition of the project
scope and the agreed management
framework for the project.
When would you develop a Project
Quality Management Plan?
Quality management includes two
components:
 Quality assurance (to assure quality
project management processes) and
 Quality control (establishing the
standards for acceptance of the
outputs, monitoring against this
criteria to determine if quality has
been achieved and maximising any
opportunities for their continuous
improvement as they are being
produced).
It is recommended that a Project Quality
Management Plan be developed for every
project as a formal framework to ensure
that the appropriate methodologies and
standards are applied and that project
outputs are ultimately delivered fit-for-
purpose. It is recognised that quality
management processes may vary from
project to project. For smaller, less
complex projects the details of the quality
management framework can be provided
within or as an appendix to the Project
Business Plan. However, for some
projects a stand-alone document is
required.
The Project Quality Management Plan
expands the approved proposal developed
in the Project Business Plan in order to:
 Define and gain authorisation for the
project and quality management
processes to be used throughout the
project.
What you need before you start:
 Endorsement of the Project
Business Plan by the Project
Sponsor and/or Steering Committee.
 Knowledge and understanding of
quality management, as outlined in
the Tasmanian Government Project
Management Guidelines.
(Medium Projects): Template and Guide Version 1.0 April 2009
Tasmanian Government Project Management Framework
i

Optional:
 Any of the following optional
documents – Project Proposal,
Project Business Case or Feasibility
Study
 Knowledge and understanding of
project planning, scope definition,
project governance, stakeholder
identification and risk identification
 Awareness of the environmental
factors that may affect the project
such as political, industrial,
legislative, technical, financial,
social, cultural and security/privacy
 Departmental Project Management
Guidelines
What you will have when you are
finished:
 A complete Project Quality
Management Plan that is ready for
acceptance by the Project Steering
Committee
The development process:
It should be noted that development of the
Project Quality Management Plan is not a
static process, and that aspects of the
project quality management approach
must be re-examined over the life of the
project, particularly where a great deal of
change in scope, schedule or budget is
involved. This iterative development
should involve the Project Team, the
Steering Committee and the Project
Sponsor. Any changes to project scope
have potential impacts for project quality
management, as does the process of risk
identification. The key is to determine the
effect of such changes and obtain clear
sign-off.
Maintaining document control:
In order to track the agreed changes to the
Project Quality Management Plan, and
record its distribution throughout the
document's development and subsequent
revision(s), a document version control
process is essential. Version control
provides for unique identification of
documents, whether electronic or hard
copy, and assists with the easy
identification of each subsequent version
of a document. The version number
changes as the document is revised
allowing released versions of a document
to be readily discernable from draft
versions.
Refer to the Project Management Fact
Sheet: Document Control for more
information.
How to use this template:
The template contains sections which are
either optional or can be developed at a
number of levels of detail depending upon
individual need.
All documents developed based on this
template should include an appropriate
acknowledgement.
A number of different text styles have
been used within the template, as follows:
 Text in italics is intended to provide
a guide as to the kind of information
that can be included in a section and
to what types of projects it might be
applicable.
 Text in normal font is intended as
examples.
 Text enclosed in <angle brackets> is
intended to be replaced by whatever
it is describing.
Where to Get Additional Help:
The following tools and resources are
available at www.egovernment.tas.gov.au:
 The Large Project Business Plan
Template provides high level detail
on the main components required in
defining the quality processes to be
implemented.
 Further information on quality
management is contained within the
Tasmanian Government Project
Management Guidelines - Section 9:
Quality Management.
Quality Management Plan (Medium Projects): Template and Guide Version 1.0 April 2009
Tasmanian Government Project Management Framework
ii

< The Fleet Base West Low
Level Bridge Repair
project>
Quality Management Plan
Version: <n.n>, Date: <dd-mm-yyyy>
Copy: Uncontrolled
The version number starts at one and increases by one for each release. It shows the release number and a
revision letter if in draft. The original draft is 0.A and subsequent drafts are 0.B, 0.C etc. The first accepted
and issued document is 1.0. Subsequent changes in draft form are 1.0A, 1.0B etc.. The accepted and issued
second version is 1.1 or 2.0, depending on the magnitude of the change.
Refer to the Project Management Fact Sheet: Document Control, for more information at
www.egovernment.tas.gov.au.
<enter name of unit>
Department of <enter name of department>

Acknowledgements
The contribution of the following individuals in preparing this document is gratefully
acknowledged:
<Contributors/reviewers/developers>
This document has been derived from a template prepared by the Department of Premier and
Cabinet, Tasmania. The structure is based on the Tasmanian Government Project Management
Guidelines.
For further details, refer to www.egovernment.tas.gov.au
<Project Title>
Quality Management Plan
Version <n.n> Date: <dd-mm-yyyy>
Page 4 of 13

Document Acceptance and Release Notice
This is <release/version> <n.n> of the < The Fleet Base West Low Level Bridge Repair project>
Quality Management Plan.
The Quality Management Plan is a managed document. For identification of amendments each
page contains a release number and a page number. Changes will only be issued as complete
replacement. Recipients should remove superseded versions from circulation. This document is
authorised for release once all signatures have been obtained.
PREPARED: Date: - -
(for acceptance) <Name>
<Project Title> Project Manager
ACCEPTED: Date: - -
(for release) <Name, Title>
< The Fleet Base West Low Level Bridge Repair >
Project Sponsor on behalf of the < The Fleet Base
West Low Level Bridge Repair > Project Steering
Committee
Document Development History
Build Status:
Version Date Author Reason Sections
<n.n>
List the most recent
amendment first
<dd-mm-yyyy> <name> Initial Release All
Amendments in this Release:
Section Title Section Number Amendment Summary
eg. This is the first release of this document.
Distribution:
Copy No Version Issue Date Issued To
1 <n.n> <dd-mm-yyyy> <name, title, organisation>
2
Electronic <n.n> <dd-mm-yyyy> Shared drive
<Project Title>
Quality Management Plan
Version <n.n> Date: <dd-mm-yyyy>
Page 5 of 13

Contents
1 Overview .................................................................................................................................. 3
1.1 Purpose of Quality Management Plan...............................................................................3
1.2 Quality Management Plan Components............................................................................3
2 Project Quality Assurance..........................................................................................................3
2.1 Methodologies and Standards..........................................................................................3
2.2 Quality Review.................................................................................................................. 3
2.2.1 Project Evaluation and Review.............................................................................3
2.2.2 Management of changes to project scope............................................................3
2.2.3 Role of Project Quality Consultants......................................................................3
2.3 Information Management..................................................................................................3
2.3.1 Document Management........................................................................................3
2.3.2 Record keeping.....................................................................................................3
3 Output Quality Control............................................................................................................... 3
3.1 Output Quality Criteria......................................................................................................3
3.2 Output Review Procedures...............................................................................................3
3.2.1 Role of Output or Technical Quality Consultants...................................................3
3.2.2 Output Change Control.........................................................................................3
3.3 Output Acceptance Procedures........................................................................................3
4 Appendices.................................................................................................................................. 3
<Project Name> Project Quality Management Plan
Version <n.n, dd-mm-yyyy>
Page 6 of 13

Overview
1 Overview
1.1 Purpose of Quality Management Plan
Project quality management plan is referred to as a process used to guide the project manager and
project team members to check that whether the project outcomes are meeting the expectation of
the clients or not. The purpose of using the quality document is to detail the way through which
quality processes involved to The Fleet Base West Low Level Bridge project should be
implemented to make sure that the outputs are all fit into the objectives. All the processes of
project management should be conducted followed by a quality manner. The quality management
plan not only develops during the project initiation stage but also it can be developed during the
progress phase also. It identifies those changes required to meet the project objectives.
Throughout the project development life cycle period theses changes should be incorporated by
the project manager and project team members.
1.2 Quality Management Plan Components
In order to achieve the quality management plan for The Fleet Base West Low Level Bridge project
the different components those should be considered by the project managers include quality
assurance, quality control and quality improvement, The quality assurance plan helps to make sure
that quality processes are being followed throughout the project life cycle period. The quality
control helps to implement quality project output and the quality improvement plan helps to improve
the quality of the project.
2 Project Quality Assurance
After applying quality project management processes quality assurance for The Fleet Base West
Low Level Bridge project should meet the quality assurance approach. The methodologies and
standards for the project quality assurance are also elaborated in this document.
2.1 Methodologies and Standards
In order to assure quality of projects different methodologies are processes are available those are
needed t be adopted and applied by the project team members. Basically with the help of different
testing mechanism quality assurance plan is conducted by the project managers and steering
committee members. Different methodologies used for assuring project quality include non
functional testing, functional testing, compatibility testing, usability testing etc. However theses are
applicable for construction projects. For the construction project the quality assurance processes
that are widely used include proper contract management, bidding, appropriate tendering, data
record keeping management, privacy management etc. The list of quality assurance standards
used for managing tis particular project include:
 Whether quality is matching the expected project outcomes or not
 Checking whether competitiveness is increasing or not
 Meeting all environmental objectives
 Increased consumers loyalty
 Reduce rate of loss across the business environment
 Internal processes are all under control
<Project Name> Project Quality Management Plan
Version <n.n, dd-mm-yyyy>
Page 7 of 13

Overview
2.2 Quality Review
2.2.1 Project Evaluation and Review
After taking quality assurance activities it become the responsibilities of the project team members
to review and evaluate the project once again to make sure that the assurance processes taken
are governing the project towards success direction or not. The quality review document given
high opportunities for future improvement, gives review on processes those are used for producing
the project outputs. It helps the project team members to learn regarding respective project quality
management actions. In addition to that it also helps the project team members to gain competitive
advantages and commercial revenue.
The project manager and other project team members and project manager is responsible to
arrange and manage the quality reviews. The reviews are all performed by the steering committee
members. The project sponsors and owner are responsible to review the post implementation
process. The reports are delivered to the project directors or project executives. The final report is
accepted by the project manager only. However, all the project stakeholders will take part in this
review process. As soon as the report is taken the change management plan is documented and
estimated respectively regarding when and how to be implemented. For these changes respective
budget and time line are also estimated by the project managers and project team members.
2.2.2 Management of changes to project scope
The change management plan for The Fleet Base West Low Level Bridge project needs to
be anticipate and planned with the help if risk assessment process. Appropriate issue
management processes should keep tracking for the emerging and unanticipated issues.
The project steering committee members are needed to focus on the potential issues once
more and re evaluate them to reduce its impact on project success. In order to change the
project scope iterative management activities should be implemented. The changes must
reflect in the project scope in project business planning iterations.
2.2.3 Role of Project Quality Consultants
The project quality consultants are responsible to bring various advices regarding constriction
activities while checking quality of The Fleet Base West Low Level Bridge project. The structure of
the project, processes involved ad progress review must be checked by the project quality
consultants, In addition to that, the quality consultant give individual feedback to the project
steering committee members also. Based on the area of expertise the role of the consultants
varies a lot from each other. The different roles plays by the project quality consultants include
legal issues related review, external and internal audit requirements, stakeholders interest and
quality review as well.
2.3 Information Management
2.3.1 Document Management
Whenever third parties act behalf of the assigned project contractors verification procedure
become useful for project success. The materials supplied for construction of the bridge were
much poor therefore this is needed to be changed. The version control will be managed using
descriptive commit massages, sharing the changes frequently, by avoiding indiscriminate
commitments and making coordination with co project workers. The controlled copies of accepted
version will be issued.
<Project Name> Project Quality Management Plan
Version <n.n, dd-mm-yyyy>
Page 8 of 13

Overview
2.3.2 Record keeping
The construction licence zoning approval and development application are to be recorded in
computerized system. These data must keep secured from external users. The project owners
should make sure that no external attackers are allowed to access any of the legal documents and
information from the server without permission. Apart from that, these data are all required to be
well managed also from the project quality management perspectives.
3 Output Quality Control
Quality control for the <Project Name> Project will be achieved by defining the relevant quality
criteria for the outputs, or what characteristics make them ‘fit for purpose’.
3.1 Output Quality Criteria
Quality management plan implementation does not give ultimate success to the project rather
whether the outputs are meeting all criteria or not is also important. Firstly the project manager and
steering committee members should check that whether the requested changes are helping the
project to meet the quality criteria or not. If not then based on feedback respective changes must
be incorporated. The other components on which focus are needed include risk management and
change management plan. The output of the quality must avoid all potential previous risks and
even after implementation of changes also no risks should be present. If these criteria are meet
then the project will be accepted and success implemented as well.
3.2 Output Review Procedures
The outputs will be reviewed before the business owner finally accepts the project. The testing and
final project review will be conducted by the project manager. Output testing and review,
progressive auditing or appraisals are needed to be conducted throughout the project development
life cycle period. Based on the test results the project managers should bring changes in the
project development activities. It is expected that if all possible technical, functional and non
functional activities are taken predominantly then the project would surely meet the acceptance
criteria and objectives.
3.2.1 Role of Output or Technical Quality Consultants
The role of the technical quality consultant is to review the technical aspects that are following
throughout the project development life cycle. Proper IT support will give security to the system
and plays quality roles in project activities. The steering committee members should play active
role to [provide respective feedback to both project team members about quality project outcomes.
3.2.2 Output Change Control
A change control log is attached in the appendix.
<Project Name> Project Quality Management Plan
Version <n.n, dd-mm-yyyy>
Page 9 of 13

Overview
3.3 Output Acceptance Procedures
The quality outputs should be accepted by the project owners after defining and reviewing the
complete document. The business owner checks the feasibility report and competitive market
analysis report before accepting the new requested changes. The process of output acceptance
also includes management accountabilities and responsibilities. The business owner will sign off
the project by exchanging official emails. In addition to this, for a formal project closure proper
output acceptance is required. The steering committee also plays active roles in output
acceptance procedures.
4 Appendices
<Project Name> Project Quality Management Plan
Version <n.n, dd-mm-yyyy>
Page 10 of 13

Overview
Appendix A: Change Request/Rectification Log
Date Output Request Impact Responsible
Officer
Authorisation
date
Completion
date
Comments
12/06/2019 Improved
record keeping
system
Record keeping system
improvement
Positive IT manager 12/6/2019 14/6/2019 Successful
15/06/2019 Quality raw
material
importing
Overall quality improvement Positive Resource
manager
15/6/2019 18/06/2019 Successful
20/06/2019 Hiring experts Hiring new experts Positive HR manager 20/6/2019 21/6/2019 Successful
<Project Name> Project Quality Management Plan
Version <n.n, dd-mm-yyyy>
Page 11 of 13