PRINCE2 Management Stages

Management Stages.

 

PRINCE2 defines management stages as partitions of the project with management decision points, they also equate to the commitment of resources and authority to spend.  A management stage therefore is a collection of activities and products whose delivery is managed as a unit.

 

Every project using PRINCE2 will have a minimum of two management stages: the initiation stage where the Project Initiation Documentation is created, and at least one delivery stage, so-called, because a delivery stage is where the specialist products are created and approved.

 

Therefore management stages only occur one at a time; they do not overlap.  There are many advantages of splitting a project into a series of management stages:

 

Providing at the end of the stage, an end stage assessment, to allow review and decision points for the project board to assess the project viability at regular intervals rather than letting it run on in an uncontrolled manner.  

 

Another advantage is that stages give the ability to make key decisions prior to investing in the detailed work and cost of the following stage.  Management stages also facilitate the management by exception principle by delegating authority to the project manager on a stage by stage basis.

 

The project board will release the project to the project manager one stage at a time, and only after considering the business case, project plan, next stage plan, and End-Stage Report.  The next stage will only be authorised if there is sufficient business justification for the project to continue.

 

With management by Exception implemented, there is no need for “regular progress meetings”. Don’t’ get confused, the end stage assessment is fundamentally a business review (although progress information is gathered and presented).

 

The project manager will have the authority for day to day management and control of a stage as long as the agreed tolerances are forecast not to be exceeded. By virtue of this, the project board can manage by exception while reducing the administrative overhead of being involved while still keeping in control.

 

When considering how many management stages within a project, there are several key questions that need to be asked to help define this number.  For example, how far ahead in the project is it sensible to plan?  Where do key decision points need to be?  

 

In addition, if the project is a risky one then management stages will tend to be shorter in duration.  The confidence of the project board and project manager in the project, will also determine how many stages and how long particular stages needs to be.

 

There is clearly a balance between many short stages with an increase in overhead, versus few long stages resulting in less control.  The number of stages in a project should be chosen by asking the question “ where do the end stage assessments need to be so that project viability can be checked?”

 

It is important that management stages are not confused with technical stages.  These are often called phases, and refer to sensible groupings of products and techniques.  Technical stages of the overlap, whereas management stages do not.  Technical stages are typified by the use of a particular set of specialist skills.

 

Whenever a technical stage spends beyond a management stage boundary, the technical stage should be broken down so that each management stage contains a whole number of specialist products.

 

For more information CLICK HERE