Pid Project Initiation Document Template

Pid-Project-Initiation-Document-Template
Document information
Project Name
name
Date
date
Release
Draft/Final
Author
author
Owner
owner
Client
client
Document Number
number
Revision, Approvals &
Distribution
Revision History
Revision # ....
Revision Date
date
Previous Revision Date
date
Summary of Changes
change
Changes Marked
change mark
Revision # ....
Revision Date
date
Previous Revision Date
date
Summary of Changes
change
Changes Marked
change mark
Revision # ....
Revision Date
date
Previous Revision Date
date
Summary of Changes
change
Changes Marked
change mark
Date of next revision:
....
Approvals
Approval # ....
Name
name
Signature
signature
Title
title
Date of Issue
date
Version
version
Approval # ....
Name
name
Signature
signature
Title
title
Date of Issue
date
Version
version
Approval # ....
Name
name
Signature
signature
Title
title
Date of Issue
date
Version
version
Distribution
Distribution # ....
Name
name
Title
title
Date of issue
date
Version
version
Distribution # ....
Name
name
Title
title
Date of issue
date
Version
version
Overview
Purpose
The purpose of the Project Initiation Documentation is to define the project, in
order to form the basis for its management and an assessment of its overall
success. The Project Initiation Documentation gives the direction and scope of the
project and (along with the Stage Plan) forms the ‘contract’ between the Project
Manager and the Project Board.
The three primary uses of the
Project Initiation Documentation
are to:
Ensure that the project has a sound basis before
asking the Project Board to make any major
commitment to the project
Act as a base document against which the
Project Board and Project Manager can assess
progress, issues and ongoing viability questions
Provide a single source of reference about the project so that
people joining the ‘temporary organization’ can quickly and
easily find out what the project is about, and how it is being
managed.
The Project Initiation Documentation is a living product in that it should
always reflect the current status, plans and controls of the project. Its
component products will need to be updated and rebaselined, as
necessary, at the end of each stage, to reflect the current status of its
constituent parts.
The version of the Project Initiation Documentation that was used
to gain authorization for the project is preserved as the basis
against which performance will later be assessed when closing
the project.
Contents
The Project Initiation
Documentation should cover the
following topics.
Project Definition
Project Approach
Business Case
Project Management Team
Structure
Role Descriptions
Quality Management
Strategy
Configuration Management
Strategy
Risk Management
Strategy
Communication Management
Strategy
Project Plan
Project Controls
Tailoring of PRINCE2
Advice
The Project Initiation Documentation is derived from the
Project Brief and discussions with user, business and
supplier stakeholders for input on methods, standards and
controls.
The Project Initiation Documentation could be a single document;
an index for a collection of documents; a document with cross
references to a number of other documents; a collection of
information in a project management tool.
The following quality criteria
should be observed:
Consideration has been given to the format of the Project Initiation Documentation. For small
projects a single document is appropriate. For large projects it is more appropriate for the
Project Initiation Documentation to be a collection of standalone documents. The volatility of
each element of the Project Initiation Documentation should be used to assess whether it
should be standalone, e.g. elements that are likely to change frequently are best separated
out.
The controls cover the needs of the Project
Board, Project Manager and Team Managers and
satisfy any delegated assurance requirements
The Project Initiation
Documentation correctly represents
the project
It shows a viable, achievable project that is in
line with corporate strategy or overall
programme needs
The project management team structure is complete, with names and titles. All the roles have
been considered and are backed up by agreed role descriptions. The relationships and lines of
authority are clear. If necessary, the project management team structure says to whom the Project
Board reports • It clearly shows a control, reporting and direction regime that can be implemented,
appropriate to the scale, risk and importance of the project to corporate or programme
management
It is clear who will administer
each control
The project objectives, approach and strategies are consistent
with the organization’s corporate social responsibility directive,
and the project controls are adequate to ensure that the project
remains compliant with such a directive
Communication Management Strategy
Identify the parties interested in the project and
document the means and frequency of
communication between them and the project
Project Controls
Summarize the projectlevel controls such as
stage boundaries, agreed tolerances, monitoring
and reporting
Risk Management Strategy
Describe the specific risk management techniques
and standards to be applied, and the responsibilities
for achieving an effective risk management
procedure
Quality Management Strategy
Describe the quality techniques and standards to
be applied during the project, and the
responsibilities for achieving the required quality
levels
Project Management Team Structure
Add a chart showing who will
be involved with the project
Project Approach
Define the choice of solution that will be used in the project to
deliver the business option selected from the Business Case. Take
into consideration the operational environment into which the
solution must fit
7