Escolar Documentos
Profissional Documentos
Cultura Documentos
Client
Contract No
Cost Centre No
Commencement Date
Project Duration
Project Name
Project Name
Document Control
Document Information
Information
Document Id
Document Owner
Issue Date
Last Saved Date
File Name
[Name]
Document History
Version
Issue Date
Changes
[1.0]
[Date]
Document Approvals
Role
Name
Project Sponsor
Project Manager
PCD Manager
(if applicable)
Procurement Manager
(if applicable)
Finance Manager
(if applicable)
HR Manager
(if applicable)
Signature
Date
1. Included
2. Excluded
3. Organization
1. Organizational Boundaries and Interfaces
i. Client
ii. Sub-contractors
iii. Suppliers
2. Project Organization
i. Steering Committee
ii. Project Team
3. Project Organization Chart
4. Project Constraints
1. Project Constraints
2. Critical Project Barriers
3. Long Lead Items
5. Schedule and Budget
1. Work Breakdown Structure
2. Schedule and Milestones
3. Resources
4. Budget
6. Risk Management
7. Sub-contract Management
8. Communication and Reporting
9. Sign Off Sheet
Project Name
1.
Project Name
Overview
1. Executive Summary
The first step to completing a Project Execution Plan is to write an Executive Summary. This
section will summarize the entire document by describing the background for the project and the
proposed Vision, Goals and Timeframes. So summarize each of the sections in this document
concisely by outlining the:
Project Name
State the vision and goals of the project. They need to be Smart which means Specific,
Measurable, Action orientated, Realistic and Time based. Where possible, try and link in the
business problem or opportunity into the Vision so that the project team knows exactly what is
being solved by the vision.
[Write your Vision here]
2. Management Summary
DATE OF COMMENCEMENT
DATE OF COMPLETION
DURATION (Days)
CONTRACT VALUE
PROVISIONAL SUM
2. Project Scope
Clarify what the project will (and will not) deliver, in order to avoid future shifts in the level of
ambition.
i. Included
ii. Excluded
State what is specifically excluded from the project but what the customer may expect to be
included. This could, for example, be clarifying that training of end-users is excluded.
This project will exclude
Project Name
3. Organization
Describe the internal project organization and all organizational issues affected by the project result or the project
is dependent on
Team Leader
:
Engineers in charge :
ii. Sub-contractors
Sl.
No
.
Subcontractor Name
Scope of Work
Target
Finish Date
Remarks
Material Supplied
Target
Finish Date
Remarks
iii. Suppliers
Sl.
No
.
Supplier Name
Project
Team
Procureme
nt Team
HR Team
PCD
v. Project Team
Finance
Team
Project Name
Project Name
PROJECT
MANAGER
PLANNING
ENGINEER
MECHANICA
L ENGINEER
MECHANICA
L FOREMAN
ELECTRICAL
ENGINEER
CIVIL
ENGINEER
ELECTRICAL
FOREMAN
CIVIL
FOREMAN
Sl.
No
.
Constraint Items
Sl.
No
.
Description
Type of Constraint
Constraint
Date
Duration
Remarks
Remarks
Project Name
Description
TOTAL WT
%
Cum. Plan %
Remarks
Progress %
ENGINEERING
PROCUREMENT
CONSTRUCTION
TRAINING
COMMISSIONING
Total
ii. Schedule and Milestones
i. Schedule
Detailed Project Schedule in bar chart format shall be attached.
WT
Task Name
INITIATION
Duration
16 days
4 days
10
5 days
17
4 days
23
3 days
28
3 days
33
Perform Stage-Gate
ary
5/01
February
2/02
9/02
Project Name
16/02 23/02
March
1/03
8/03
Apr
15/03 22/03 29/03
1 day
34
35
PLANNING
48 days
36
9 days
47
5 days
54
5 days
61
4 days
67
6 days
75
4 days
81
4 days
87
4 days
93
Contract Suppliers
6 days
101
Perform Stage-Gate
1 day
102
103
EXECUTION
5 days
104
Build Deliverables
3 days
109
4 days
122
Perform Stage-Gate
1 day
123
124
CLOSURE
125
132
7 days
6 days
1 day
iii. Milestones
ACTIVITY ID
10
ACTIVITIY DESCRIPTION
Start
Finish
Remark
s
Project Name
iv. Resources
In order for your sponsor to approve the Project Execution Plan, they will want to have an
understanding of the amount of resources required to undertake it. Complete the following table
which sets out the generic resources including people, equipment and materials needed to
undertake the project. These are only generic figures to give the Project Sponsor an idea of the
level of resourcing required to finish the project.
Project Resources
Type
Quantity
Notes
[list here]
[list here]
[list here]
[list here]
[list here]
[list here]
[list here]
[list here]
[list here]
v. Budget
A summary of Project budget can be provided.
5. Risk Management
Describe the procedure to be used for managing risks in the project. The procedure should specify
who is responsible for risk management, when risk situation is regularly considered (e.g. at each
project status meeting), and which roles risks are communicated to, etc.
Also refer to the Risk Management Plan (or Risk Sheet) where the risks are listed, assessed, and
mitigation and contingency is defined.
3. Risk Assessment
The initial Risk Assessment (following page) attempts to identify, characterize, prioritize and document a mitigation
approach relative to those risks which can be identified prior to the start of the project.
The Risk Assessment will be continuously monitored and updated throughout the life of the project, with monthly
assessments included in the status report (see Communications Plan) and open to amendment by the Project
Manager.
Because mitigation approaches must be agreed upon by project leadership (based on the assessed impact of the risk,
the projects ability to accept the risk, and the feasibility of mitigating the risk), it is necessary to allocate time into
each Steering Committee meeting, dedicated to identifying new risks and discussing mitigation strategies.
The Project Manager will convey amendments and recommended contingencies to the Steering Committee monthly,
or more frequently, as conditions may warrant.
Project Risks
11
Details
Likelihood
[list here]
[list here]
[list here]
[list here]
[list here]
[list here]
[list here]
[list here]
[list here]
Project Issues
Issue
Details
Impact
[list here]
[list here]
[list here]
[list here]
[list here]
[list here]
[list here]
[list here]
[list here]
12
Project Name
Project Name
Risk Level
L/M/H
Likelihood
of Event
Mitigation Strategy
Project Size
Person Hours
H: Over 20,000
Certainty
Estimated Project
Schedule
H: Over 12 months
Certainty
H: Over 15 members
Certainty
Number of Interfaces to
Existing Systems
Affected
H: Over 3
Certainty
Narrow Knowledge
Level of Users
Available
documentation clouds
establishment of
baseline
Project Scope Creep
M: Knowledgeable
of user area only
M: More than 75%
complete/current
Likely
L: Scope generally
defined, subject to
revision
Unlikely
Consultant Project
Deliverables unclear
Vendor Project
Deliverables
L: Well defined
Unlikely
M: Estimated, not
clearly defined
Somewhat
likely
Cost Estimates
Unrealistic
L: Thoroughly
predicted by
industry experts
using proven
practices to 15%
margin of error
Unlikely
Project Definition
13
Likely
Project Name
Risk Level
L/M/H
M: Timeline
assumes no
derailment
Likelihood
of Event
Somewhat
likely
Unlikely
L: Identified and
enthusiastic
L: Understands
value & supports
project
Unlikely
L: Understands
value & supports
project
L: Most understand
value & support
project
Unlikely
Unlikely
Project Team
Availability
M: Distributed team
makes availability
questionable
Somewhat
likely
Physical Location of
Team prevents effective
management
Project Teams Shared
Work Experience
creates poor working
relationship
Weak User Participation
on Project Team
M: Team is
dispersed among
several sites
M: Some have
worked together
before
Likely
Unlikely
L: Procurement
Methodology familiar
to team
L: Well-defined
Unlikely
N/A
Unlikely
N/A
L: Well-defined and
accepted
Unlikely
N/A
Timeline Estimates
Unrealistic
Number of Team
Members
Unknowledgeable of
Business
Mitigation Strategy
Timeline reviewed monthly by
three groups (Project Manager
and Steering Committee) to
prevent undetected timeline
departures
Project Manager and
consultant to identify
knowledge gaps and provide
training, as necessary
Project Leadership
Steering Committee
existence
Absence of
Commitment
Level/Attitude of
Management
Absence of
Commitment
Level/Attitude of Users
Absence of MidManagement
Commitment
Unlikely
Project Staffing
Somewhat
likely
Project Management
Procurement
Methodology Used
foreign to team
Change Management
Procedures undefined
Quality Management
Procedures unclear
14
Project Name
6. Sub-contract Management
List which part of work is out-sourced to which sub-contractor.
Refer to the sub-contractors agreement that should include or refer to the statement of work, the
execution process, milestones, quality assurance, configuration management, communication structure,
hand-over procedure, acceptance criteria, and quality audits.
Sub-contractor
Company
Contact
Sub-contracted
Work
Ref. to subcontract
Remark
Frequency/Sch
edule
Information
Participants /
Responsibles
Weekly and on
event
Project Mgr
Project Team
Shared Project
Server
When available
Milestone Meetings
Excel sheet
Excel sheet
Before
milestones
M6
Project status,
problems, risks,
changed
requirements
All project
documentation
and reports
Project status
(progess)
Wrap-up
Experiences
15
Project Mgr(s)
Project Team
Members
Project Mgr Subproject Mgr
Project Mgr
Project Team
Project Name
Type of
Method / Tool
Communication
External Communication and Reporting:
Project Report
Excel sheet
Frequency/Sch
edule
Information
Participants /
Responsibles
Monthly
SteCo Meetings
Monthly
Project Manager,
SteCo
Project
ManagerSubProject
Managers
SteCo Meetings
Excel sheet
Sign-off Sheet
I have read the above Project execution Plan and will abide by its terms and
conditions and pledge my full commitment and support for the Project
execution Plan.
Project Sponsor:
Date
Project Manager:
Date
Steering Committee:
Date
Steering Committee:
Date
Steering Committee:
Date
Steering Committee:
Date
Steering Committee:
Date
16
Project Name
Steering Committee:
Date
Steering Committee:
Date
Steering Committee:
Date
Steering Committee:
Date
Steering Committee:
Date
Steering Committee:
Date
Steering Committee:
Date
Steering Committee:
Date
Steering Committee:
Date
Steering Committee:
Date
17