UNIVERSITY of GLASGOW

IT Services
home > services > IT Services > For Staff > Project office > PRINCE2 Methodology

PRINCE2 Methodolgy

The PRINCE (Projects In Controlled Environments) model was originally established in 1989 by the Central Computer and Telecommunications Agency. The updated version of the model, PRINCE2 was launched in 1996 and since then, has become the dominant project management model within the UK, both in the private and public sectors.

The University has adopted "parts" of the PRINCE2 Methodolgy and used them in conjuction with our own procedures to develop a robust process for the management of projects. Details of this can be found in the "GU Methodology" section of the website.

The PRINCE2 model is based on a set of best practise processes for the effective selection and management of projects. The best practises have been developed from other existing project management methods and lessons learned from dozens of case studies as well as consultation with over 150 users. Since the organisations involved in developing the best practises spanned across many disciplines, this means that the model is highly adaptable to different project circumstances across a broad span of industries and sectors. Since the model has been tried and tested in a variety of project environments and organisations, adoption of PRINCE2 avoids the pitfalls of trial and error for an organisation and gives them a fast track to effective project management and the benefits that come from managing change well.

The PRINCE2 approach moves for a clear business case for every project and checks the validity of that business case at key progress points throughout the project’s life. This smoothes the progress of the decision making process and allows prioritisation of projects as there is a common means for comparing costs and benefits across candidate projects. This in turn allows the project to get back on track if it has digressed in any way, or alternatively, allows the University to cease work on the project at the earliest opportunity with a minimum amount of time, effort and resources. The University can give appropriate consideration to the deployment of resources and be confident that these resources address the changes that will deliver the greatest return. By using the PRINCE2 model, we can ensure that many of the issues normally associated with an ad hoc approach to change management are avoided.

Benefits of PRINCE2

A well-applied project management approach provides the controlled environment that will allow senior management to initiate projects confidently and delegate some of the responsibility and authority for their management. The PRINCE2 method allows senior management to define the parameters within which the project can operate. PRINCE2 uses exceptions management, which means that senior management maintain control over the project but not to the extent where minor alterations must go to management for a decision. This means that the PRINCE2 model is very flexible which allows reactions to minor changes that will inevitably occur.

The benefits of the PRINCE2 model for management is that it provides a framework within which delegation of planning and execution of change can take place.

This is done by ensuring:-

Clarity of purpose

Objectives of the project are clearly understood by mapping them against the big picture of where the organisation is going.

Credible planning

Implementation of the strategy is tested by looking at the project capability and capacity available to manage the changes required.

Commitment

Where buy-in is achieved from all areas of the organisation through effective communication processes.

Control

Where projects are planned and delivered in phases allowing important review points.

PRINCE2 Characteristics

There are a number of key characteristics that typify a PRINCE2 project based approach.

These key characteristics are:-

  • Each change has a clear business case.
  • Clarity of ownership, responsibility and decision making.
  • Focus on project outcomes rather than activity.
  • Planning as a core discipline.
  • Clear definition of scope and benefits at the outset and their continual review.
  • Buy-in from key stakeholders throughout the life of the project.
  • Effective cross functional working.
  • Principle of a ‘customer’ and a ‘supplier’ relationship.
  • Low management overhead through management by exception whilst allowing high levels of control.
  • Chunking of the project into manageable pieces with control points at the completion of each chunk to test the ongoing justification for the project.
  • Appropriate attitude to the management of risk and issues.
  • End user involvement to ensure realistic definition and realisation of project benefits.
  • Clear communication and reporting structures to drive effective decision making.
  • Quality defined as ‘fitness for purpose’ rather than an abstract concept.
  • Fully supported through accredited trainers and consultants.
  • Allows learning from experiences, both good and bad, for the ongoing development of project best practises.
  • No ‘routine bureaucracy’.