The Project Initiation Documentation (PID) is one of the most significant artefacts in project management, which provides the foundation for the business project.
PID bundles the information, which was acquired through the Starting up a project and Initiating a Project processes in a PRINCE2 controlled project environment. The Project Initiation Document provides a reference point throughout the project for both the customer and the Project Team.
Working on a ‘virtual’ project? The PID is just as useful. PRINCE2 can also easily be applied to virtual projects.
What’s a PID?
Within a PRINCE2-context the PID (Project Initiation Documentation) is a logical set of documents that brings together the key information needed to start the project on a sound basis and that conveys the information to all involved with the project.
What is the purpose of the Project Initiation Documentation?
The purpose of the PID is to define the project, in order to form the basis for its management and an assessment of its overall success. The PID gives the direction and scope of the project and (along with the stage plan) form the “contract” between the project manager and the project board.
The three primary uses of the PID 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 for the project so that people joining the “temporary organisation” can easily and quickly find out what the project is about, and how it is being managed
The PID 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 management stage, to reflect the current status of its constituent parts.
The version of the PID that was used to gain authorisation for the project is preserved as the basis against which performance will later be assessed when closing the project.
PID Composition
The PID should include the following content:
Project definition: Explains what the project needs to achieve (background, project objectives and desired outcomes, project scope and exclusions, constraints and assumptions, the user(s) and any other known interested parties and interfaces).
Project approach: Defines the choice of solution that will be used to deliver the business option selected from the business case.
Business Case: Describe the justification for the project based on estimated costs, risks and benefits.
Project management team structure: A chart showing who will be involved with the project.
Role descriptions: These describe the roles of those in the project management team and any other key resources.
Management approaches: The procedures, techniques, and standards that need to be applied on a project and the distribution of the project’s responsibilities.
Benefits management approach: Establishes the benefits of management actions and reviews that ensure that the project’s outcomes are achieved and confirms that the project’s benefits are realised.
Change management approach: Establishes the target organisational state required for the project to meet its objectives together with the means by which the business will shift from the current state and through any interim states.
Commercial management approach: Describes the procedures, techniques, and standards to be applied and the responsibilities for effective commercial management. It covers the approach to secure, service, and maintain all commercial agreements required for the project to be a success. This may include activities such as market engagement, procurement, and contract management.
Communication management approach: Defines and describes the means and frequency of communication across the project ecosystem, supporting alignment, and shaping of the project. It facilitates engagement with stakeholders through the establishment of a controlled and bidirectional flow of information.
Digital and data management approach: Describes how data and information will be managed across the project ecosystem and through the project lifecycle and afterwards.
Issue management approach: Describes how issues will be captured and reported and explains how changes to the project baseline will be assessed and controlled.
Quality management approach: Describes the quality techniques and standards to be applied, and the roles and responsibilities for achieving the required quality specifications and acceptance criteria during a project.
Risk management approach: Describes the specific risk management techniques and standards to be applied, and the responsibilities for achieving an effective risk management procedure.
Project Plan: Describes how and when the project’s objectives are to be achieved, by showing the major products, activities and resources required on the project. It provides a baseline against which one can monitor the project’s progress, management stage by management stage.
Tailoring of PRINCE2: A summary of how PRINCE2 will be tailored for the project.
Chronological order:
Project Initiation Documentation Derivation
The PID includes the information available in the project brief. Indeed, the project brief describes the purpose, the cost, the deadlines, the performance requirements and the constraints of a project. It is developed before the start of the project during the Starting up a project process and used throughout the Initiating a project process to create the PID and its components. It is then replaced by the PID and is not kept.
Skip to content
