PRINCE2 Plans

 

Whenever starting off on a journey you will always need a plan, for without a plan there is no control.  A plan should provide information on what is required, how it would be achieved and by whom, when events will happen, and it should prove that time, cost, quality, scope, risk, and benefit targets are achievable.

 

Once a plan has been created it will be approved by the project board and used as a baseline reference against which progress can be tracked and measured.

 

In PRINCE2 a plan is not just a schedule, it is a comprehensive document describing how, when and by whom a specific set of targets is to be achieved.  Plans are the backbone of the management information system.  Planning is the act of creating and maintaining a plan, as such, it is essential.

 

The planning horizon is the period of time for which it is possible to accurately plan, and it is therefore seldom desirable or possible to plan an entire project at the start.  For this reason, PRINCE2 recommends that there are different levels of plan, to reflect the needs of the different levels of management involved within the project.

 

The project plan is created by the Initiating a Project process, the Initiation Stage Plan is created within the Starting Up a Project process, and each successive Stage Plan Is created by the Managing a Stage Boundary process.  

 

Optional Team Plans are created by the Managing Product Delivery process.  Should an Exception Plan be required, and if approved, it will replace the original plan that would no longer finish within tolerances.  It is therefore not a different level.

 

The only other plan in PRINCE2 is the Benefits Review Plan, and as this covers activities both during and after the project, it may be part of a corporate or program plan.

 

The Project Plan Provides the Business Case with planned costs and timescales, identifying major control points such as management stage is and milestones.  It is used by the project board as a baseline against which to monitor project progress.

 

A stage plan is produced for each management stage but extracts the high-level stage detail In the Project Plan and plans down to day to day management level as an adequate basis for control by the project manager.  

 

Each stage plan is created near the end of the current management stage and will cover more detail but cover a shorter duration than the Project Plan.

 

Optional Team Plans are produced by the team Manager to cover the execution of one or more Work Packages, and PRINCE2 does not prescribe the format or composition of this type of plan.  Normally, the Team Manager will create their Team Plans at the same time as the Project Manager creates the Stage Plan.

 

If an Exception Plan is required, it will show the actions required to recover from the effects of tolerance deviation.  If it is approved it will replace the plan that was in exception and become the new baselined Project Plan or Stage Plan.  

 

Approval of an Exception Plan at stage level requires approval by the project board, but if the Project Plan needs to be replaced, it requires authorisation by corporate or programme management.

 

Optionally, the project manager may set tolerance at Work Package level.  If this is forecast to be exceeded by the team manager, then they should raise it as an Issue for the attention of the project manager and a decision on what to do next.  

 

If the project manager is forecasting that a Stage Plan or the Project Plan will exceed tolerance, then the project manager will raise an Exception Report.

 

For more information CLICK HERE