Overview
DP3 works on the PRINCE2 principle that a project should not continue without approval. It is invoked either when a management stage of a project is at its end and the next Stage Plan is prepared or an exceptional circumstance has occurred. In an exceptional circumstance an Exception Report is then followed by an Exception Plan (which is then presented to the Project Board in DP2 Authorising a Project).
The Project Board's responsibility is to:
Changes to the Business Case should be communicated to corporate or Programme Management.
Exception Plans should clearly outline changes to the Business Case, new Risks and their status, increased costs and changes to the Project Plan. Once approved the Exception Plan replaces the Stage or Project Plan.
If the project can not be corrected with the help of an Exception Plan the Project Board can request the Project Manager to close down the project using CP Closing a Project.
Responsibility for Authorising a Stage or Exception Plan lies with the Project Board.
Method links
Tips
- Get meeting dates organised as soon as possible.
- Prior to DP3 there should be frequent, informal discussions between the Project Manager and Project Board to avoid any surprises.
- When evaluating an exception plan it may pay to "go back to the drawing board" and restart with a new Project Initiation Document (PID).
Notes
Case studies and examples
Related links
| 
