Overview
This sub stage is a wrap-up of all previous substages in IP. Here we collate all the management products (Risk Log, PB, PMTS, Job Desc, Project App, Proj Quality Plan, Proje. Plan, Business Case, RL, Project Controls, and the Communications Plan) into a Project Initiation Document. This does not have to be one physical (or one virtual) document. it can be split in to several more manageable files.
The purpose of creating a PID is to get approval from DP2, for the project to proceed and confirm commitment from the Project Board, Together with PID approval, the next stage approval is also important, and invokes the SB process. Finally there is a close down of the initiation stage and approval that the initiation stage delivered on its' own stage plan. Responsibility for assembling the PID lies with the Project Manager.
Method links
Tips
- Be sure to cross check that the components of the PID so they are consistent. remember to authorise the next stage.
- Keeping the communications plan is often a good way to let people know when they will be approached with project information while not bogging them down with unnecessary project administration information.
- Consider including a glossary of PRINCE2 and specialist terms to help the board understand. A loose A4 page (perhaps a Crazy Colour PRINCE2 Process Map!) is ideal to stop flicking though the document.
- To keep the PID slim perhaps put the job descriptions as a separate document providing when asked for.
Notes
Case studies and examples
Related links
|
