LARGE PROJECT PLAN Insert Project Title

LARGE PROJECT PLAN – [Insert Project Title]

[Insert Project Title]

Project Plan

Approval

Project Delegate / Approved/
Not Approved / Signature / Title / Date

Approval

Project Steering Committee Chair / Approved/
Not Approved / Signature / Title / Date
Author:
Version:
Date:

PAGE1OF10

THE AUSTRALIAN NATIONAL UNIVERSITY

LARGE PROJECT PLAN – [Insert Project Title]

1. Contact Details

[Provide details of the person to contact for further information in relation to this project plan] / NAME:
PHONE NUMBER:
E-MAIL:

1. Approach

[What approach will be taken to deliver the project deliverables] / ☐Standard project approach / ☐Agile / ☐Outsource
Reasons for the above decision. Also state who will manage the project if outsource is selected.

1. Governance

[What structures for over sighting the project will be put in place] / ☐Steering Committee / ☐Project Management Group / ☐Reference Groups / ☐Counsellors
Reasons for the above decision.

1. Team Structure and Roles

[Who will be on the project and their responsibilities] /

Structure

Roles and Responsibilities

Title / Role / Responsibilities

1. Project Success Measures

[How will the three levels of project success be measured] / Project Management / Project / Investment
Quality, Cost, Schedule / KPIs

1. Deliverables

[High level summary of deliverables required to obtain benefits] / OUTCOME / Business Outcome / Business Outcome1 / Business Outcome1 / Business Outcome1 / Business Outcome1
OUTPUT
Required Deliverable / User of deliverable / User of deliverable
Required Deliverable / User of deliverable / User of deliverable / User of deliverable
Required Deliverable / User of deliverable
Required Deliverable / User of deliverable

1. Work Breakdown Structure

[High level overview of the project effort] /

1. Schedule

/ Insert high level Gantt chart incorporating critical path

1. Budget

[Breakdown of the elements considered when estimating the budget] /

Project

Type / Cost / Funding Source / Approved By
External
Proposing Area
Impacted Area(s)
Division of Information
Total
Comments

Ongoing

Type / Cost per Annum / Funding Source / Approved By
Staff
Licensing
Maintenance
Total
Comments

1. Risks Management Plan

[Assessment of project risks and key risk response plans] /

Risk Assessment

Risk ID / Risk Event / Likelihood / Impact / Detection Difficulty / Phase
1 / Training Officers fail to own responsibility for new function process training / H, M, L / H, M, L / H,M,L / Planning

Detection Difficulty : High - no warningMedium - Some time to reactLow - Lots of time to react

Risk Response

Risk ID / Risk Event / Response / Plan / Trigger / Responsible Officer
1 / Training Officers fail to own responsibility for new function process training / Mitigate / Create training officer focus group to obtain buy in / Lack of engagement from training officers during planning / Joe Teamember

1. Issues

[Summary of the key issues facing the project] / ID / Issue / Importance / Responsible Officer / Status - Resolution
1 / Best format for knowledge transfer unclear / H, M, L / Sarah Teamlead / Resolved – training format obtained from client

1. Communications Plan

[Parties interested in the project and the means and frequency of communication with them] / Entity / Role / Information to be communicated / Frequency / Medium
Joe Cio / Project Executive / Project Status Report / Monthly / Email

1. Reporting Plan

[Details of reporting approaches to be used on the project ] / Type / Audience / Trigger
e.g. Status Report, Highlight Report, Checkpoint Report / e.g. Steering Committee, Client / e.g. SC Meetings, Major Event

1. Quality Plan

[Techniques and standards that will be applied to ensure quality and who is responsible ] / Deliverable / QA Technique / Responsible Officer / Approver

1. Change Management Plan

[Process for dealing with project change requests] /

1. Benefits Measurement Plan

[Plan for measuring expected benefits post project ] / Benefit / Current state (baseline) / How will we measure / Who will measure / When will we measure

1. Operational Support

[Outline the expected IT operational support structure once the project has been implemented] / Project product / Support Area / Responsible Director

1. Handover Strategy

[Plan for transferring skills and knowledge required for ongoing use/support of deliverables] / Task / Mechanism / Audience / Responsible Officer

1. Approvals

[Required executive approvals] / Name / Signature / Title / Approved / Date
Yes: ☐/ No: ☐
Yes: ☐/ No: ☐
Yes: ☐/ No: ☐
Yes: ☐/ No: ☐
Yes: ☐/ No: ☐
Comments

PAGE1OF10

THE AUSTRALIAN NATIONAL UNIVERSITY