A stage is deemed to be in exception as soon as current forecasts for the end of the stage deviate beyond the delegated tolerances boundaries.
The project is in exception if the whole project is likely to go beyond tolerance boundaries.
If either a stage or the project is forecast to deviate beyond its agreed tolerance boundaries, it no longer has the approval of the Project Board.
A new plan must be presented to take the place of the current plan.
The deviation should have been recognised during 'Controlling a Stage (CS)'.
The Project Manager will have brought the situation to the attention of the Project Board through an Exception Report.
The Project Board will have requested that the Project Manager produce an Exception Plan.
The Exception Plan will then be presented to the Project Board at an Exception assessment.
If a stage or the project is forecast to go outside the tolerances agreed with the Project Board when the plan was approved and the situation cannot be rectified within tolerance, the Project Manager has no further mandate to carry on with the work.
The Exception Plan will have the same structure as other PRINCE2® plans.
It should run from the present time to the end of the plan that it replaces.
If it is the Project Plan that is in exception, a revised Project Plan should be created, taking into account the actuals to date.
The Configuration Item Records of all products included in the plan being replaced must be checked.
Where the status shows that work is outstanding, the Exception Plan should include this work.
The Configuration Librarian will provide a Product Status Account of the products in the plan that is to be replaced.
The Project Manager is responsible for producing Exception Plans with the help of Project Support.
Those responsible for Project Assurance should check the plan.
|Current Stage Plan||Input||This is the plan from which the deviation has occurred and that will define the tolerances and the extent of the deviation. It can also be used to extrapolate what would happen if the deviation were allowed to continue.|
|Exception Plan||Input||This will contain details, such as recommended action, that will contribute to the Exception Plan.|
|Issue Log||Input||This may contain details of the reasons for the project or stage being forecast to deviate beyond its tolerances.|
|Risk Log||Input||This may contain details of the reasons for the project or stage being forecast to deviate beyond its tolerances.|
|Project Plan||Input||This shows the products required from the stage.|
|Project Initiation Document||Input||Contains the ‘what’ and ‘why’ of the project and is the document that specifies the Project Board’s terms of reference.|
|Project Status Account||Input||This will provide information on products that are still incomplete.|
|Quality Log||Update||Add details of any new quality checks planned.|
|Exception Plan Report||Input||If the response to the Exception Report (CS8) caused the Project Board to ask for an Exception Plan (DP4), this would be passed on by CS8 as the trigger to this sub-process.|
|Exception Plan||Output||The product of this sub-process, a plan that replaces the current Stage Plan.|
|Project management team structure||Update||This should be updated with any changes for the remainder of the stage.|
These are given in tabular form in the file ‘SB6 producing and exception plan.doc’ in the product package.
If the project tolerances that are under threat, a revised Project Plan should be produced.
Where the project is part of a programme, the programme support office must examine the Exception Plan to ensure that the project remains consistent with the programme.
The Project Manager should be wary of overestimating the ability to recover from a forecast deviation.