Project Management Plan
Project Management Plan
[Project Name]
Author: [Author]
Date: [yyyymmdd]
Version: [#.#]
Operator notes:
All instructional text is displayed in blue font colour in the template. These should be deleted prior to
the document being distributed for review and approval.
Update text within square brackets which is placeholder text with relevant text.
E.g. [yyyymmdd] should be changed to latest date 20190905
Use this basic structure and type sizing for all your covers. Do not manipulate or rescale any of the
graphic components. Use initial caps in your headings with capital letters for proper nouns only.
[Project Name]
Document Control
Document location
Location
Author
Position Name Contact no
Revision history
Version Issue date Author/editor Description/Summary of changes
Reviewed by
Version Issue date Name Position Review date
Approvals
Approval refers to the approver’s acceptance of the content and overall intention of this document, including
acceptance of any commitments described in order to successfully deliver the initiative. The approver, where
relevant, also confirms that this document complies with relevant strategies, policies and regulatory
requirements.
Version Issue date Name Position Approval date
Related documents
Document Location
Table of Contents
1 DOCUMENT PURPOSE........................................................................................................................... 4
2 PROJECT INFORMATION....................................................................................................................... 4
2.1 Key Contacts..................................................................................................................................... 4
2.2 Project Background........................................................................................................................... 5
3 PROJECT DEFINITION............................................................................................................................ 5
3.1 Project Objectives............................................................................................................................. 5
3.2 Project Scope.................................................................................................................................... 5
3.2.1 Inclusions 5
3.2.2 Exclusions 5
3.3 Assumptions..................................................................................................................................... 5
3.4 Constraints........................................................................................................................................ 5
3.5 Work Breakdown Structure............................................................................................................... 5
4 APPROACH.............................................................................................................................................. 6
4.1 Deliverables...................................................................................................................................... 6
4.2 Project Organisation Structure.......................................................................................................... 6
4.3 Roles and Responsibilities................................................................................................................ 6
5 GOVERNANCE AND REPORTING.......................................................................................................... 7
5.1 Governance Structure....................................................................................................................... 7
5.2 Reports............................................................................................................................................. 7
6 PROJECT CONTROLS............................................................................................................................ 7
6.1 Schedule & Dependencies Management.......................................................................................... 7
6.2 Financial Management...................................................................................................................... 7
6.3 Risk Management............................................................................................................................. 7
6.4 Issue Management........................................................................................................................... 7
6.5 Quality Management......................................................................................................................... 7
6.6 Change Control................................................................................................................................. 8
6.7 Resource Management..................................................................................................................... 8
6.8 Stakeholder Management................................................................................................................. 8
6.9 Communications Plan....................................................................................................................... 8
6.10 Lessons Learnt................................................................................................................................. 8
7 APPENDIX A: PROJECT SCHEDULE..................................................................................................... 9
8 APPENDIX B: RISKS............................................................................................................................. 10
1 Document Purpose
The Project Management Plan (PMP) is developed at the commencement of Initiate Phase of the Project
Delivery Framework. The information in this plan should be based on the Business Case or other artefact
used to gain approval.
The development of a PMP is applicable to Medium and Large projects. However, the level of detail and
completeness may vary to suit the type and nature of individual projects. The PMP is a Key Deliverable
required for submission at Stage Gate 2.
The purpose of this Project Management Plan (PMP) is to provide a detailed description of what the project
is about, its delivery method and controls to realise its defined scope and objectives. This document
provides context and guidelines for the conduct of the project and its interaction with stakeholders, the
project team, Project Management Office and other entities.
It is the formally approved authoritative reference that defines how the project is to be executed, monitored
and controlled. Accordingly, it will be maintained throughout the life of the project as a living document. As
new or revised elements of the management of the project are approved, the changes will be reflected in this
plan. The PMP is subject to formal change control.
2 Project Information
This Section is a quick overview of the project: what it is about, how it came to be, who owns it and who the
project manager is.
Project ID
Project Manager
Project Sponsor
3 Project Definition
This section defines the project to which this PMP applies.
3.2.1 Inclusions
Use this section to describe all the major deliverable components of the project.
The following items are included in the scope of the project:
3.2.2 Exclusions
This section provides the Project Manager with the opportunity to make it clear what is not in the scope of
the project. The Deliverables statement above implicitly excludes everything else. However, if the Project
Manager feels that there may be some ambiguity or the possibility that readers may make an incorrect
inference, this section allows the matter to be clarified. This may typically include products and activities
closely related to this project, such as pre-requisites, dependencies and interdependencies that will be
delivered as part of other projects or business processes.
The following items are excluded from the scope of the project:
3.3 Assumptions
There can be internal and external factors that can influence the course of the project that are outside of the
control of the project management team. Assumptions are factors that could affect the project.
Factors relating to Quality, Dependencies, Priority and Resources should be addressed via project planning
and may have associated risks to meet the plan
The following assumptions are made with regards to the project:
3.4 Constraints
Constraints are limitations on the project. These typically include budget limits or deadlines for delivery and
contractual constraints.
The following restrictions and limitations have been identified for the project:
The WBS organises and defines the total scope of the project and is a deliverable ‐oriented hierarchy of the
work to accomplish the project objectives. Significant work packages will have a Statement of Work, which is
the contract between the project manager and work package manager or vendor.
4 Approach
Describe the project approach, overall strategy and methods and procedures to be adopted for achieving the
project objectives. Describe any engagement models, sequencing of the work and reasons for such an
approach.
4.1 Deliverables
Use this section to describe all major deliverables of the project. Deliverables should be tracked though a
Deliverables Register to record information such as acceptance criteria, reviews required, approvers,
baselined delivery dates, actual delivery dates, etc.
The following table summarises the list of deliverables.
ID Deliverable Name WP Lead Participant Delivery date
Role Description
accordance to the project’s roles and responsibilities. They are responsible for identifying
and escalating any risks or issues encountered during the course of the project.
Project Analyst The Project Analyst carries out tasks and activities to assist with project performance and
status reporting. (e.g. schedule and budget)
Third Party Supplier The contractor/supplier (3rd party) will carry out the activities assigned to them as per the
agreed contract/ engagement terms and conditions.
Project Support Assists the Project Manager and Project Team in undertaking project management
functions.
Construction The Construction Coordinator carries out the tasks associated with the coordination of the
coordinator field activities.
5.2 Reports
Describe the reporting hierarchy and frequency. If the project is not reporting through the standard Project
Status Report, describe the alternative method, content of the report to be provided and the reason for the
deviation.
6 Project Controls
The following section is a list of standard project management controls which may be required depending on
the size and nature of the project.
635172427.docx Page 10 of 11
[Project Name]
8 Appendix B: Risks
The following table contains a list of the project risks identified at the time of this version’s release.
635172427.docx Page 11 of 11