PRINCE2 (TM) Project Initiation Document (PID)

To get an editable copy of this template to use on your project go to

Get Started. It's Free
or sign up with your email address
PRINCE2 (TM) Project Initiation Document (PID) by Mind Map: PRINCE2 (TM) Project Initiation  Document (PID)

1. Document information

1.1. Project Name

1.1.1. [name]

1.2. Date

1.2.1. [date]

1.3. Release

1.3.1. Draft/Final

1.4. Author

1.4.1. [author]

1.5. Owner

1.5.1. [owner]

1.6. Client

1.6.1. [client]

1.7. Document Number

1.7.1. [number]

1.8. Revision, Approvals & Distribution

1.8.1. Revision History Revision # [....] Revision Date Previous Revision Date Summary of Changes Changes Marked Revision # [....] Revision Date Previous Revision Date Summary of Changes Changes Marked Revision # [....] Revision Date Previous Revision Date Summary of Changes Changes Marked Date of next revision: [....]

1.8.2. Approvals Approval # [....] Name Signature Title Date of Issue Version Approval # [....] Name Signature Title Date of Issue Version Approval # [....] Name Signature Title Date of Issue Version

1.8.3. Distribution Distribution # [....] Name Title Date of issue Version Distribution # [....] Name Title Date of issue Version

2. Overview

2.1. Purpose

2.1.1. 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.

2.1.2. 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.

2.1.3. 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 re-baselined, as necessary, at the end of each stage, to reflect the current status of its constituent parts.

2.1.4. 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.

2.2. Contents

2.2.1. The Project Initiation Documentation should cover the following topics.

2.2.2. Project Definition

2.2.3. Project Approach

2.2.4. Business Case

2.2.5. Project Management Team Structure

2.2.6. Role Descriptions

2.2.7. Quality Management Strategy

2.2.8. Configuration Management Strategy

2.2.9. Risk Management Strategy

2.2.10. Communication Management Strategy

2.2.11. Project Plan

2.2.12. Project Controls

2.2.13. Tailoring of PRINCE2

2.3. Advice

2.3.1. 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.

2.3.2. 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.

2.3.3. 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 stand-alone documents. The volatility of each element of the Project Initiation Documentation should be used to assess whether it should be stand-alone, 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

3. Project Definition

3.1. Background

3.1.1. [...]

3.2. Project objectives

3.2.1. [covering time, cost, quality,scope, risk and benefit performance goals]

3.3. Desired outcomes

3.3.1. [...]

3.4. Project scope and exclusions

3.4.1. [...]

3.5. Constraints and assumptions

3.5.1. [...]

3.6. The user(s) and any other known interested parties

3.6.1. [...]

3.7. Interfaces

3.7.1. [...]

4. Project Approach

4.1. [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]

5. Business Case

5.1. [Describe the justification for the project based on estimated costs, risks and benefits]

6. Project Management Team Structure

6.1. [Add a chart showing who will be involved with the project]

7. Role Descriptions

7.1. [Role descriptions the project management team and any other key resources]

8. Quality Management Strategy

8.1. [Describe the quality techniques and standards to be applied during the project, and the responsibilities for achieving the required quality levels]

9. Configuration Management Strategy

9.1. [Describe how and by whom the project’s products will be controlled and protected]

10. Risk Management Strategy

10.1. [Describe the specific risk management techniques and standards to be applied, and the responsibilities for achieving an effective risk management procedure]

11. Communication Management Strategy

11.1. [Identify the parties interested in the project and document the means and frequency of communication between them and the project]

12. Project Plan

12.1. [Describe how and when the project’s objectives are to be achieved. Show the major products, activities and resources required on the project. Provides a baseline against which to monitor the project’s progress stage by stage]

13. Project Controls

13.1. [Summarize the project-level controls such as stage boundaries, agreed tolerances, monitoring and reporting]

14. Tailoring of PRINCE2

14.1. [Summarise how PRINCE2 will be tailored the project]

15. How to use this template

15.1. How to share this template with your team

15.1.1. Send an email 1. Click Share this map 2. Select Invite People 3. Write a message 4. Click Invite

15.1.2. Send a link 1. Click Share this map 2. Tick Link to share 3. Copy the link to share it

15.1.3. Export 1. Click down arrow, bottom right 2. Select the export option you want

15.2. How to complete this template

15.2.1. Complete the sections in square brackets [....]

15.2.2. Read these sections for help on this template Purpose Advice

15.2.3. Navigate using the links in Contents Contents

15.3. Attribution

15.3.1. Copyright © AXELOS Limited 2009. All rights reserved. Material is reproduced with the permission of AXELOS