MindMap Gallery Pid Project Initiation Document Template

Pid Project Initiation Document Template

The purpose of the Project Initiation Document (PID) is to capture and record basic information needed to correctly define and plan the project.

Edited at 2020-10-10 11:56:45

Fiona_

Pid Project Initiation Document Template

Fiona_

Recommended to you
Outline

purchase ordering workflow
- 2.9k
- 19
Mind Trainer
lean innovation with kanban
- 633
- 6
Mind Trainer
Project Management Process
- 2.9k
- 68
- 14
Oliveettom
Drivers of Changes in Selling and Sales Management
- 472
- 12
- 1
Oliveettom
profit tree example
- 1.5k
- 28
- 2
Oliveettom
human resource management
- 902
- 12
- 2
Oliveettom
External Environment influences on Apple
- 509
- 1
- 2
History Fanatic
How to Be Your Own Boss
- 439
- 16
- 2
Fiona_
Comparing the world's 3 leading water tools
- 662
- 5
Ashley
Bending The Freshwater Biodiversity Curve - An Emergency Recovery Plan
- 463
- 3
- 1
Ashley

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, inorder to form the basis for its management and an assessment of its overallsuccess. The Project Initiation Documentation gives the direction and scope of theproject and (along with the Stage Plan) forms the ‘contract’ between the ProjectManager and the Project Board.

The three primary uses of theProject Initiation Documentationare to:

Ensure that the project has a sound basis beforeasking the Project Board to make any majorcommitment to the project

Act as a base document against which theProject Board and Project Manager can assessprogress, issues and ongoing viability questions

Provide a single source of reference about the project so thatpeople joining the ‘temporary organization’ can quickly andeasily find out what the project is about, and how it is beingmanaged.

The Project Initiation Documentation is a living product in that it shouldalways reflect the current status, plans and controls of the project. Itscomponent products will need to be updated and rebaselined, asnecessary, at the end of each stage, to reflect the current status of itsconstituent parts.

The version of the Project Initiation Documentation that was usedto gain authorization for the project is preserved as the basisagainst which performance will later be assessed when closingthe project.

Contents

The Project InitiationDocumentation should cover thefollowing topics.

Project Definition

Project Approach

Business Case

Project Management TeamStructure

Role Descriptions

Quality ManagementStrategy

Configuration ManagementStrategy

Risk ManagementStrategy

Communication ManagementStrategy

Project Plan

Project Controls

Tailoring of PRINCE2

Advice

The Project Initiation Documentation is derived from theProject Brief and discussions with user, business andsupplier stakeholders for input on methods, standards andcontrols.

The Project Initiation Documentation could be a single document;an index for a collection of documents; a document with crossreferences to a number of other documents; a collection ofinformation in a project management tool.

The following quality criteriashould be observed:

Consideration has been given to the format of the Project Initiation Documentation. For smallprojects a single document is appropriate. For large projects it is more appropriate for theProject Initiation Documentation to be a collection of standalone documents. The volatility ofeach element of the Project Initiation Documentation should be used to assess whether itshould be standalone, e.g. elements that are likely to change frequently are best separatedout.

The controls cover the needs of the ProjectBoard, Project Manager and Team Managers andsatisfy any delegated assurance requirements

The Project InitiationDocumentation correctly representsthe project

It shows a viable, achievable project that is inline with corporate strategy or overallprogramme needs

The project management team structure is complete, with names and titles. All the roles havebeen considered and are backed up by agreed role descriptions. The relationships and lines ofauthority are clear. If necessary, the project management team structure says to whom the ProjectBoard 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 programmemanagement

It is clear who will administereach control

The project objectives, approach and strategies are consistentwith the organization’s corporate social responsibility directive,and the project controls are adequate to ensure that the projectremains compliant with such a directive

Project Management Team Structure

Add a chart showing who willbe involved with the project

Project Approach

Define the choice of solution that will be used in the project todeliver the business option selected from the Business Case. Takeinto consideration the operational environment into which thesolution must fit

Quality Management Strategy

Describe the quality techniques and standards tobe applied during the project, and theresponsibilities for achieving the required qualitylevels

Risk Management Strategy

Describe the specific risk management techniquesand standards to be applied, and the responsibilitiesfor achieving an effective risk managementprocedure

Project Controls

Summarize the projectlevel controls such asstage boundaries, agreed tolerances, monitoringand reporting

Communication Management Strategy

Identify the parties interested in the project anddocument the means and frequency ofcommunication between them and the project