Project Initiation Document Template

[Project Name]

ProjectInitiation Document

[Full Date]

Prepared by

Approved by

Contents

1.Introduction

1.1Purpose

1.2Background

1.3PID Structure and Contents

2.Project Definition

2.1Project Objectives

2.2Project Approach

2.3Project Scope

2.4Project Deliverables

2.5Exclusions

2.6Constraints

2.7Interfaces

2.8Assumptions

3.Project Organisation

3.1Overall Governance

3.2Project Board

3.3Project Team

3.4User Reference Group

3.5Role Descriptions

4.Project Plan

5.Budget

6.Risk and Issue Management

7.Stakeholder and Communication Plan

8.Project Quality Plan

9.Project Controls

Appendices

Annex A - Project Product Descriptions

Annex B – Initial Risk Log

Configuration Management

Document Control

Approval Bodies

Document History

Distribution

  1. Introduction
  2. Purpose

The Project Initiation Document (PID) contains the key elements of information required to direct and manage a project. The PID has two principle purposes:

  • to ensure that the Project Manager has a sound basis on which to ask the Project Board to make a commitment to the project; and
  • to act as a base document against which the Project Manager and Project Board can assess progress, change management issues and ongoing viability questions.

1.1Background

1.2PID Structure and Contents

The contents of this PID are compliant with PRINCE2 guidelines and are set out as follows:

Section 2 defines the project, setting out the project objectives, approach, scope, deliverables, exclusions, constraints, interfaces to other projects and key assumptions;

Section 3defines the organisation of the project, detailing the project governance structure and the key roles and responsibilities of project staff;

Section 4provides details of the project plan, identifying the products and resources required to deliver the plan. It also identifies the different stages of the plan, in line with PRINCE2 guidance, to enable management to control project delivery and ensure that the Business Case remains valid;

Section 5 provides a full cost breakdown and identification of the sources of funding;

Section 6assesses the risks and issues facing the project and details the risk management processes that will be applied;

Section 7describes the approach to communications within the project to ensure that the objectives of the project are clearly communicated to all stakeholders;

Section 8sets out the quality plan for the project and how it will be used to ensure that the products meet user needs through a series of quality control procedures and reviews;

Section 9describes the project controls and how they will be applied.

The document is supported by a number of annexes providing additional detail to some sections.

2.Project Definition

2.1Project Objectives

2.2Project Approach

2.3Project Scope

2.4Project Deliverables

2.5Exclusions

2.6Constraints

2.7Interfaces

2.8Assumptions

3.Project Organisation

3.1Overall Governance

3.2Project Board

3.3Project Team

3.4User Reference Group

3.5Role Descriptions

4.Project Plan

5.Budget

6.Risk and Issue Management

7.Stakeholder and Communication Plan

8.Project Quality Plan

9.Project Controls

Appendices

Annex A - Project Product Descriptions

Annex B – Initial Risk Log

Configuration Management

Document Control

Title: / [Project] Outline Business Case
Document ID: / [ID]
Reason for last change / [Reason]
Security Class: / [ ]
Author: / [Title: Author]
[Organisation]
Owner: / [Title: Owner]
Organisation
Address
email]

Approval Bodies

The initial issue of this document requires the approval of the signatories below on behalf of the Project Board, and then based on project rate the approval of the signatories below on behalf of the eHealth Bodies.

Approved by:
Name / Title / Signature / Date
Project Board
PET
Programme Board
Strategy Board

Document History

Version No. / Date / Details of Changes included in Update / Highlight / Tracking

Distribution

Version / Date / Issued to / Capacity