Project Execution Plan - PEP

July 7, 2009 | Author: PM Hut | Filed under: Project Management Definitions, Project Plan Development

Project Execution Plan - PEP
By The Office of Government Commerce - OGC, UK

Purpose of the Project Execution Plan - PEP

The Project Execution Plan is the core document for the management of a project. It is a statement of policies and procedures defined by the project director, although usually developed by the project manager for the project sponsor/project director’s approval. It sets out in a structured format the project scope, objectives and relative priorities.

For non-construction projects see Project plan.

Fitness for Purpose

Does the Project Execution Plan:

  • include plans, procedures and control processes for project implementation and for monitoring and reporting progress?
  • define the role and responsibilities of all project participants, and is a means of ensuring that everyone understands, accepts and carries out their responsibilities?
  • set out the mechanisms for audit, review and feedback, by defining the reporting and meeting requirements, and, where appropriate, the criteria for independent external review?

Suggested Contents in the Project Execution Plan - PEP

Much of a Project Execution Plan will be standardised, but the standard will need to be modified to meet the particular circumstances of each project. A typical PEP might cover the items listed below, although some may appear under a number of headings with a cross reference system employed to avoid duplication:

  • project definition and brief;
  • roles, responsibilities and authorities;
  • project cost plan and cost management procedures;
  • risk and sensitivity analysis;
  • programme management;
  • contracting and procurement;
  • administrative systems and procedures;
  • safety and environmental issues, such as the construction design and management regulations;
  • quality assurance;
  • commissioning; and
  • post project evaluation.

Notes

The PEP will change as a project progresses through its design and construction stages. It should be a dynamic document regularly updated and referred to as a communication tool, as well as a control reference.

Source Information

  • Project brief
  • Business case

Successful delivery toolkit, the Office of Government Commerce - © Crown Copyright 2009

Share this article:
  • Facebook
  • LinkedIn
  • TwitThis

Related Articles

1 person has left a comment

[...] See also the Project Brief, and the Project Execution Plan. [...]

Project Initiation Documentation - PM Hut wrote on November 27, 2009 - 11:34 am | Visit Link

feel free to leave a comment

Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

All fields marked with " * " are required.

Project Management Categories