A PID is a Project Initiation Document and is created once the authorisation to initiate a project has been given. The PID is the final result of the initiation phase of the project and describes the "what, why, who, how, where, when and how much" of the project. This document is fairly extensive within the Prince2 Project Management Model and will incorporate many documents, such as the project brief, project scope, project definition and project plan as well as the strategy for the project in terms of communication, quality, configuration management, risk and issues. More information on these individual topics can be found in the Prince2 book, so I will not go into detail here.
It is the project managers role to produce the PID and pass it on to the project board for authorisation. In reality the stakeholders, users and business analysts will need to be involved in producing much of the documentation.
The PID is a constantly evolving document and remains important throughout the project life cycle. The PID contains many documents/sections including the project plan, exception plans, risks/issues and therefore is updated throughout the project. It remains a reference point to who is doing "what, when, how, why".
Spend time keeping the PID updated and authorised.
It is the project managers role to produce the PID and pass it on to the project board for authorisation. In reality the stakeholders, users and business analysts will need to be involved in producing much of the documentation.
The PID is a constantly evolving document and remains important throughout the project life cycle. The PID contains many documents/sections including the project plan, exception plans, risks/issues and therefore is updated throughout the project. It remains a reference point to who is doing "what, when, how, why".
Spend time keeping the PID updated and authorised.
No comments:
Post a Comment