PROJECT EXECUTION PLAN Project Name

Project Execution Plan

---------------------------- Project
Client :
Contract No :
Cost Centre No :
Commencement Date :
Project Duration :

1
 PROJECT EXECUTION PLAN Project Name

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 ©

PCD Manager
(if applicable)

Procurement Manager
(if applicable)

Finance Manager
(if applicable)

HR Manager
(if applicable)

2
 PROJECT EXECUTION PLAN Project Name

Contents

1. Overview
1. Executive Summary
2. Management Summary
2. Project Scope
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

3
 PROJECT EXECUTION PLAN Project Name

1. 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:

 History, requirements and proposed solution

 Project vision, goals deliverables and timeframes
 Resources, budget and success criteria.

[Write your content here]

i. Background

1. History/ Lessons Learned

Before describing the proposal in depth, you need to provide a brief historical view of the related
projects, so that it sets the context upon which the project will be initiated. As this is the basis
upon which the project is created, you need to describe all of the relevant history that has taken
place up until now.

[Write your content here]

2. Requirements
From the lessons learned stated above if you have any requirements to avoid problem or risk
areas, you can mention them here.

[Write your content here]

ii. Proposal

In the background section above, you have described the general basis upon which the project will be
created. You've described the problem or opportunity that exists in the business and the solution that the
project needs to deliver. In this section, it is now time to describe the project that you are proposing is
initiated.

iii. Vision and Goals

4
 PROJECT EXECUTION PLAN 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]

[Write your Goals 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 …

5
 PROJECT EXECUTION PLAN Project Name

3. Organization
Describe the internal project organization and all organizational issues affected by the project result or the project
is dependent on

i. Organizational Boundaries and Interfaces

i. Client
Client Name :
Team Leader :
Engineers in charge :

ii. Sub-contractors
Sl. Subcontractor Name Scope of Work Target Remarks
No Finish Date
.

iii. Suppliers
Sl. Supplier Name Material Supplied Target Remarks
No Finish Date
.

6
 PROJECT EXECUTION PLAN Project Name

ii. Project Organization

iv. Steering Committee

Project
Team

Procureme
HR Team
nt Team

Finance
PCD
Team

v. Project Team

7
 PROJECT EXECUTION PLAN Project Name

PROJECT
MANAGER

PLANNING
ENGINEER

MECHANICA ELECTRICAL CIVIL

L ENGINEER ENGINEER ENGINEER

MECHANICA ELECTRICAL CIVIL

L FOREMAN FOREMAN FOREMAN

iii. Project Constraints

Sl. Constraint Items Type of Constraint Constraint Remarks

No Date
.

iv. Critical Activities/ Long Lead Items

Sl. Description Duration Remarks
No
.

8
 PROJECT EXECUTION PLAN Project Name

4. Schedule and Budget

i. Work Breakdown Structure
Cum. Plan %
Sl. TOTAL WT
Description Remarks
No %
Progress % WT

1 HSE, PHSER & EIA STUDIES

2 ENGINEERING
3 PROCUREMENT

4 CONSTRUCTION

5 TRAINING

6 TESTING & PRE-

COMMISSIONING
7 COMMISSIONING

Total

ii. Schedule and Milestones

i. Schedule
Detailed Project Schedule in bar chart format shall be attached.

9
 PROJECT EXECUTION PLAN Project Name

ary February March Apr

ID Task Name Duration 5/01 12/01 19/01 26/01 2/02 9/02 16/02 23/02 1/03 8/03 15/03 22/03 29/03
3 INITIATION 16 days
4 Develop Business Case 4 days

10 Perform Feasibility Study 5 days

17 Establish Terms of Reference 4 days
23 Appoint Project Team 3 days
28 Set-up Project Office 3 days
33 Perform Stage-Gate 1 day

34
35 PLANNING 48 days
36 Create Project Plan 9 days
47 Create Resource Plan 5 days

54 Create Financial Plan 5 days

61 Create Quality Plan 4 days
67 Create Risk Plan 6 days
75 Create Acceptance Plan 4 days

81 Create Comm unications Plan 4 days

87 Create Procurement Plan 4 days
93 Contract Suppliers 6 days
101 Perform Stage-Gate 1 day
102
103 EXECUTION 5 days
104 Build Deliverables 3 days
109 Monitoring and Control 4 days
122 Perform Stage-Gate 1 day

123
124 CLOSURE 7 days
125 Perform Project Closure 6 days
132 Review Project Completion 1 day

iii. Milestones
Remark
Start Finish
ACTIVITY ID ACTIVITIY DESCRIPTION s

10
 PROJECT EXECUTION PLAN 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 project’s 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
 PROJECT EXECUTION PLAN Project Name

Risk 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 EXECUTION PLAN Project Name

Initial Project Risk Assessment

Risk Risk Level Likelihood Mitigation Strategy

L/M/H of Event
Project Size
Person Hours H: Over 20,000 Certainty Assigned Project Manager,
engaged consultant,
comprehensive project
management approach and
communications plan
Estimated Project H: Over 12 months Certainty Created comprehensive
Schedule project timeline with frequent
baseline reviews
Team Size at Peak H: Over 15 members Certainty Comprehensive
communications plan,
frequent meetings, tight
project management
oversight
Number of Interfaces to H: Over 3 Certainty Develop interface control
Existing Systems document immediately
Affected
Project Definition
Narrow Knowledge M: Knowledgeable Likely Assigned Project Manager(s)
Level of Users of user area only to assess global implications
Available M: More than 75% Likely Balance of information to be
documentation clouds complete/current gathered by consultant
establishment of
baseline
Project Scope Creep L: Scope generally Unlikely Scope intially defined in
defined, subject to Project execution Plan,
revision reviewed monthly by three
groups (Project Manager and
Steering Committee) to
prevent undetected scope
creep
Consultant Project L: Well defined Unlikely Included in Project execution
Deliverables unclear Plan, subject to amendment
Vendor Project M: Estimated, not Somewhat Included in Project execution
Deliverables clearly defined likely Plan, subject to amendment

Cost Estimates L: Thoroughly Unlikely Included in Project execution

Unrealistic predicted by Plan, subject to amendment
industry experts as new details regarding
using proven project scope are revealed
practices to 15%
margin of error

13
 PROJECT EXECUTION PLAN Project Name

Risk Risk Level Likelihood Mitigation Strategy

L/M/H of Event
Timeline Estimates M: Timeline Somewhat Timeline reviewed monthly by
Unrealistic assumes no likely three groups (Project Manager
derailment and Steering Committee) to
prevent undetected timeline
departures

Number of Team L: Team well versed Unlikely Project Manager and

Members in business consultant to identify
Unknowledgeable of operations impacted knowledge gaps and provide
Business by technology training, as necessary
Project Leadership
Steering Committee L: Identified and Unlikely Frequently seek feedback to
existence enthusiastic ensure continued support
Absence of L: Understands Unlikely Frequently seek feedback to
Commitment value & supports ensure continued support
Level/Attitude of project
Management
Absence of L: Understands Unlikely Frequently seek feedback to
Commitment value & supports ensure continued support
Level/Attitude of Users project
Absence of Mid- L: Most understand Unlikely Frequently seek feedback to
Management value & support ensure continued support
Commitment project
Project Staffing
Project Team M: Distributed team Somewhat Continuous review of project
Availability makes availability likely momentum by all levels.
questionable Consultant to identify any
impacts caused by
unavailability. If necessary,
increase committmment by
participants to full time status
Physical Location of M: Team is Likely Use of Intranet project
Team prevents effective dispersed among website, comprehensive
management several sites Communications Plan
Project Team’s Shared M: Some have Somewhat Comprehensive
Work Experience worked together likely Communications Plan
creates poor working before
relationship
Weak User Participation L: Users are part- Unlikely User Group Participants
on Project Team time team members coordinated by full time
employee
Project Management
Procurement L: Procurement Unlikely N/A
Methodology Used Methodology familiar
foreign to team to team
Change Management L: Well-defined Unlikely N/A
Procedures undefined
Quality Management L: Well-defined and Unlikely N/A
Procedures unclear accepted

14
 PROJECT EXECUTION PLAN Project Name

6. Sub-contract Management
List which part of work is out-sourced to which sub-contractor.
Refer to the sub-contractor’s 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 Sub-contracted Ref. to sub-
Remark
Company Contact Work contract

7. Communication and Reporting

State the principles for reporting and distributing information within the project for the different groups of
internal and external stakeholders. Include, for example, how often the reporting will take place, the type
of reports or information, the type of media in which it is presented, and the type of meetings that will take
place.

a) Internal communication and reporting: ensure that all information is available to those who
need it. – Plan project meetings, how often they take place, and who will participate – Define
how project information will made available to the internal stakeholders (e.g. project library) –
Define how and how often sub-projects and sub-contractors report to the project manager –
Define who participates milestone meetings – Define how events will be communicated

b) External communication and reporting: – Define what information will be provided to which
stakeholders – Define how and how often information will be provided to which stakeholders
often (e.g. project report) – Plan regular meetings with external stakeholders (e.g. SteCo
meetings)

Type of Method / Tool Frequency/Sch Information Participants /

Communication edule Responsibles
Internal Communication:
Project Meetings Excel sheet Weekly and on Project status, Project Mgr
event problems, risks, Project Team
changed
requirements
Sharing of project data Shared Project When available All project Project Mgr(s)
Server documentation Project Team
and reports Members
Milestone Meetings Excel sheet Before Project status Project Mgr Sub-
milestones (progess) project Mgr
Final Project Meeting Excel sheet M6 Wrap-up Project Mgr
Experiences Project Team

15
 PROJECT EXECUTION PLAN Project Name

Type of Method / Tool Frequency/Sch Information Participants /

Communication edule Responsibles
External Communication and Reporting:
Project Report Excel sheet Monthly Project status - Project
progress - ManagerSub-
forecast - risks Project
Managers
SteCo Meetings Excel sheet Monthly Project Manager, SteCo Meetings
SteCo

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 EXECUTION PLAN 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