stakeholdermap.com
Project Management, project planning, templates and advice
<. MANAGING RISKS IN SITE OPERATIONS. (FALLING FROM HEIGHT)>
<UNIT 1>
PROJECT MANAGEMENT PLAN
stakeholdermap.com
PROJECT MANAGEMENT PLAN
DOCUMENT CONTROL
DOCUMENT INFORMATION
Information
Document Id
[Document Management System #]
Document Owner
[Owner Name]
Issue Date
[Date]
Last Saved Date
[Date]
File Name
[Name]
DOCUMENT HISTORY
Version
Issue Date
Changes
[1.0]
[Date]
[Section, Page(s) and Text Revised]
DOCUMENT APPROVALS
Role
Name
©
Signature
Date
Project Sponsor
Project Review Group
Project Manager
©
stakeholdermap.com
i
PROJECT MANAGEMENT PLAN
Quality Manager
(if applicable)
Procurement Manager
(if applicable)
Communications Manager
(if applicable)
Project Office Manager
(if applicable)
stakeholdermap.com
ii
PROJECT MANAGEMENT PLAN
Table of Contents
<PROJECT NAME> ................................................................................................................................................. I
<PROJECT REFERENCE> ........................................................................................................................................ I
PROJECT MANAGEMENT PLAN ..................................................................................................................... I
DOCUMENT CONTROL................................................................................................................................. I
DOCUMENT INFORMATION ....................................................................................................................................... I
DOCUMENT HISTORY .............................................................................................................................................. I
DOCUMENT APPROVALS ......................................................................................................................................... I
TEMPLATE GUIDE ...................................................................................................................................... 1
PROJECT LIFE CYCLE: ............................................................................................................................... 2
DEVELOPMENT APPROACHES: .................................................................................................................... 2
SUBSIDIARY MANAGEMENT PLANS: ............................................................................................................. 2
VARIANCE THRESHOLDS: ........................................................................................................................... 3
BASELINES: ............................................................................................................................................... 4
stakeholdermap.com
iii
PROJECT MANAGEMENT PLAN
TEMPLATE GUIDE
How to use this template
This is a guide to the common sections included in a Project Management Plan. Sections may be
added, removed or amended to suit your project. Example tables have been added (where relevant)
these are just a suggestion, you may decide to format these sections differently.
Text in Blue italics is designed to assist you in completing the template. Delete this text before sharing
the final document.
stakeholdermap.com
1
PROJECT MANAGEMENT PLAN
PROJECT LIFE CYCLE:
Describe the project life cycle. This may be tailored to the industry, or to a particular project
management method, it should include phases for a controlled start, the work itself, quality assurance
and project close.
Phase
Phase
Key Activities
Reviews
Key Deliverables
Entry Criteria
Exit Criteria
DEVELOPMENT APPROACHES:
Describe the development approach that will be used to create each Deliverable. Approaches could
use a traditional waterfall method, an iterative approach or an agile approach.
Deliverable
Development Approach
SUBSIDIARY MANAGEMENT PLANS:
Note the supplementary management plans for the project. You can reference file names and filepaths or include hyperlinks to electronic versions of the plans.
stakeholdermap.com
2
PROJECT MANAGEMENT PLAN
Name
Comment
Scope
Scope Management Plan Template
Time
Cost
Quality
Resources
Communications
Risk
Risk Register Template
Procurement
Stakeholder
Stakeholder Management Templates
Other Plans
VARIANCE THRESHOLDS:
Document the allowable variances for each aspect of the project. Include the baseline from which
variances will measured. For example, allowable scope variance for chosen building material might
be a flame spread rating of between 10 and 20 (class I). Unacceptable building material would have a
class II or lower rating.
Scope Variance Threshold
Scope Baseline Management
For example:
Describe how the scope controlled will be
managed. Include what actions would be
taken in the event of a threshold being
breached or forecast to be breached. Most
likely change control would be invoked, but
some revisions might be allowable without
change control.
•
Performance criteria e.g. speed, or
availability.
•
Features e.g. 4 colour printing or 2 colour.
•
Quality of materials e.g. 400 gsm paper or
100 gsm paper or water proof to x PSI.
Schedule Variance Threshold
Schedule Baseline Management
Describe acceptable variances, warnings and
unacceptable variances from the schedule.
Explain how the baseline will be monitored
and managed. Describe what the responses
will be to acceptable, warning and
unacceptable variances. Include what would
trigger the change control process and/or
For example:
stakeholdermap.com
3
PROJECT MANAGEMENT PLAN
•
Use of x% of float for a given task versus
use of all float delaying dependent tasks.
•
Delay to a task that won’t impact the
critical path vs delay that will impact
critical path tasks.
•
% of delay from the schedule baseline.
•
Use of x proportion of a schedule reserve.
corrective action.
Cost Variance Threshold
Cost Baseline Management
Document the cost variances for example:
Show how the baseline will be monitored and
managed. Describe what the responses will
be to acceptable, warning and unacceptable
variances. Say when you would trigger the
change control process and/or corrective
action.
•
0 – 5 % increase or decrease in Forecast
Cost at Completion is acceptable.
•
6 – 10% indicates an issue and will trigger
an investigation with action taken to
document and mitigate any risks or issues
that are found.
•
Greater than 10% variance will trigger
corrective action.
See an Example Project Tolerance and
Acceptance Procedure
BASELINES:
Attach all project baselines.
MORE FREE PROJECT MANAGEMENT TEMPLATES
Microsoft Project Plans [tried and tested]
Project Management Templates [FREE]
Stakeholder Management Templates
stakeholdermap.com
4