Quality Management Plan
[Project Name]

[School / Section / Unit Name]
[Sub heading as required]

Prepared by:

[Author] / [School/Division] / [Department]

[Status] – [Version] – [Date]

Project Information

Project Number

Project Name

Date

Project Ownership

Project Contacts

Name	Position	Phone	Email
Primary
Other
Other

Project Approval

Document Path

Version Control

Version Number	Date	Reason/Comments/Approval

Project Overview

Project Summary

Implementation Strategy

Stage 1

Stage 2

Roles and Responsibilities

Name	Role	Quality Responsibility

Quality Planning and Standards

The quality management plan documents the University’s quality management policy for effective execution of projects. It also provides guidelines to the project management team to record and effectively cross reference the project activities in accordance with the stated project objectives.

Quality Objectives

The following are the quality objectives of the project that reflect the overall intentions to be applied with regard to quality throughout the project.

Effective Project Delivery

To facilitate the delivery of the project on time and within +/- 10% budget, with successful achievement of the Project Objectives as defined in the project charter.

Effective Project Management

To ensure that the project management methodology is adhered to and all key processes involved in project management are undertaken effectively for the project. Including output of deliverables that align with the developed Project Framework:

Project Proposal

Project Charter

Stakeholder Register

Steering Committee Terms of Reference

Communication Plan

Risk Management

Quality Management Plan

Project Management Plan

Post Implementation Review

Change Request Process

Fit for Purpose Deliverables

Deliverables are efficient, effective and meet the requirements of all project team and stakeholder members.

Customer Satisfaction

Major stakeholders are satisfied with the final project outcome.

Quality Standards

This Quality Management Plan includes the selection of applicable process and product quality standards for the Alumni Management System (AMS) Project. Please see Appendix A – Quality Standards for a list of the generic quality standards used for software based projects. These standards were used and modified as follows to identify the specific quality standards for this project:

Identified only those process and product quality standards, risk cues or measurements appropriate for the Alumni Management System (AMS) Project based on the project’s current business and technical complexity assessment.

Added additional quality standards based on this type of project, current phase of the project, or expert opinion where the absence of the quality standard would present high risk to the project.

Eliminated unnecessary quality standards based on the project’s business and technical complexity assessment or current phase of the project. However, the following process and quality standards were not eliminated:

Process Quality Standards

Project Process Quality Standards	QS #

Product Quality Standards

Project Product Quality Standards	QS #

Quality Planning Techniques

Two quality management techniques are used to ensure optimal control over the project execution.

Tool	Description
Cost Benefit Analysis	Quality planning must consider the cost-benefits tradeoffs. The primary benefit of meeting quality requirements is less rework, which means higher productivity, lower costs, and increased stakeholder satisfaction. The primary cost of meeting quality requirements is the expense associated with the Project Quality Management activities.
Benchmarking	Benchmarking involves comparing actual or planned project practices to those of other projects to generate ideas for improvement and to provide a basis by which to measure performance. These other projects can be within the performing organisation or outside of it, and can be within the same or in another application area.

Quality Control

Change Requests

All proposed changes to the project will be required to be submitted through the formal Change Management process as outlined here. The individual proposing the change will be required to complete the accepted Change Request template which requires a detailed description of the proposed change and an analysis of the project impact.

Change Request Template:

The completed Change Request will be taken to Steering Committee for approval. If approved, the Project Manager will update the Project Plan and any other relevant documentation, including section 6 of the Change Request.

Quality Assurance

Quality Assurance Reviewer/s

Name	Position	Responsibility

Quality Assurance Reviews

Appendix A – Quality Standards

QS#	Quality Standard Description	Quality Standard Explanation
QS1	Project fit to the University	Project Objectives are aligned to Organisational Objectives
QS2	Definition of the project	Project is well defined with a scope that is manageable by the University
QS3	Project objectives	Verifiable project objectives with reasonable requirements
QS4	Leadership	Project has active sponsorship
QS5	Project Management approach	Product and process planning and controls are in place
QS6	Project Management communication	Clear communication of goals and status of the project, to team members and other relevant stakeholders
QS7	Project Management support	Project Manager has complete support of project team and management
QS8	Budget and resource allocations	Sufficient budget and resources are allocated to the project
QS9	Budget constraints	Funds allocated to the project are not constrained
QS10	Delivery commitment	Stable commitment dates
QS11	Development schedule	Project schedule is agreed to by team as achievable
QS12	Team availability	Team members are dedicated to the project, or readily available when required
QS13	Organisation roles and responsibilities	Organisation members understand their own roles and responsibilities and of others
QS14	Policies and standards	Development policies and procedures are defined and carefully followed
QS15	Stakeholder involvement	Stakeholders are highly involved in the project and provide significant input
QS16	User Acceptance	Relevant processes are in place for user approval

QS#	Quality Standard Description	Quality Standard Explanation
QS17	User Training Needs	Users training needs have been considered and relevant training plan has been put in place
QS18	Requirements stability	Little or no change to baseline requirements
QS19	Requirements complete and clear	Requirements are completely specified and clearly written
QS20	Testability	Requirements are able to be tested and plans are underway
QS21	Design difficulty	Well defined interfaces and design is well understood
QS22	System Dependencies	Clearly defined dependencies of the system, processes, hardware etc.
QS23	Change Control Process	Changes to committed scope or schedule are reviewed and approved by all involved, formal change control process is followed
QS24	Quality Assurance Approach	Quality Assurance process is accepted and followed
QS25	Development Documentation	All development documentation is complete and easily accessible
QS26	Development Process	An established development process is in place, is effective and is followed by all team members
QS27	Defect Identification	Defects are detected early through frequent peer reviews
QS28	Defect Tracking	Defect tracking process is defined, consistent and followed
QS29	Lessons Learned	Lessons learned are reviewed at project milestones or phase ends, improvements are made and incorporated into future projects
QS30	Hardware platform	Stable, no significant changes expected, capacity is sufficient
QS31	Tools availability	Project Tools are in place, documented and validated
QS32	Vendor Support	Complete support at a reasonable price and in the necessary timeframe

QS#	Quality Standard Description	Quality Standard Explanation
QS33	Technology experience	Project team have adequate technology experience
QS34	Technology expertise availability	Technology support and experts are readily available
QS35	Data Migration requirements	Much data to migrate, but good descriptions available of structure and usage
QS36	External Hardware or Software interfaces	Some interfaces required
QS37	Design Complexity	Design is structurally and administratively maintainable
QS38	Support Team	Support Team is in place, sufficiently experienced and sufficient in number