Project Smart ~ Exploring trends and developments in project management today

Calendar iconNot recorded
Adobe PDF icon

The History of PRINCE2

~ By Duncan Haughey

PRINCE2 logo

It is true to say the public sector has hardly covered itself in glory with their ability to deliver projects on time, within budget and scope and to the right quality. PROMPTII, PRINCE and PRINCE2 were all introduced to address the common causes of project failure.

1975 PROMPTII

Project Resource Organisation Management and Planning Techniques

A project management method developed by Simpact Systems Ltd., PROMPTII, was a response to the outcry that many computer projects were overrunning on time estimated for completion and original budgets as set out in feasibility studies. It was not unusual to experience factors of double, treble or even ten-times the original estimates. PROMPTII was trying to set down guidelines for the stage flow of a computer project as follows:

  • Feasibility Study: to decide whether the project should and can be done, and whether it will work if it is done
  • Initial Stage: where the project organisation is set-up
  • Specification Stage: development of the user specification
  • Design Stage: where the logical, and from this, the physical design of the computer system is developed
  • Development Stage: when the system is built and tested
  • Installation Stage: where the user accepts a working system
  • Operation Stage: when the system is tuned for the work in hand

In 1979, the UK Government's Central Computing and Telecommunications Agency (CCTA) adopted the method for all information systems projects. This led to PRINCE's development ten years later.

1989 PRINCE

PRojects IN Controlled Environments

Published by the UK Government agency CCTA, Projects in Controlled Environments (PRINCE) became the UK standard for all government information systems projects.

The main features are:

  • A defined management structure
  • A system of plans for resourcing and technical issues
  • A set of control procedures
  • A focus on products; deliverables to the customer and project deliverables used for managing the project

A feature in the original method, not seen in other methods, was the idea of "assuring progress" from three separate, but linked perspectives:

  • Business Assurance Co-ordinator (BAC): whose role is to oversee the project is in line with the business mission of the company and to report at progress meetings. This assures the project stays in the best interests of the company
  • Technical Assurance Co-ordinator (TAC): who oversees the technical aspects of the project and assures it does not get into technical difficulties
  • User Assurance Co-ordinator (UAC): who represents the eventual user

However, the PRINCE method developed a reputation as being too unwieldy, too rigid and applicable only to large projects, leading to a revision in 1996.

1996 PRINCE2

PRojects IN Controlled Environments 2

An upgrade to PRINCE was considered to be in order and the development was contracted out but assured by a virtual committee spread among 150 European organisations. The BAC, TAC and UAC were removed in the official version. Most companies who adopt a PRINCE approach to project management adapt the method to their commercial environment and use those parts of PRINCE that work for them. This is acceptable as the puritanical days of sticking rigidly to a method are seen now as undesirable and unnecessary.

Originally developed for IS and IT projects to cut cost and time overruns; the second revision was made more generic an applicable to any project type.

In 2002 and 2005 PRINCE2 was updated in consultation with the international user community.

2009 PRINCE2 Major Revision

A major revision has seen the method made simpler and more easily customisable, a common request from users. The updated version has seven basic principles (not in the earlier version) that contribute to project success:

  1. Continued Business Justification
  2. Learn From Experience
  3. Defined Roles and Responsibilities
  4. Manage by Stages
  5. Manage by Exception
  6. Focus on Products
  7. Tailor to Suit Environment

The updated method aims to give project managers a better set of tools to deliver projects on time, within budget and to the right quality.


Comments

No comments have been posted yet.

Add a comment



(never displayed)



 
1000
Type the numbers for four hundred seventy-two.
Notify me of new comments via email.
Remember my form inputs on this computer.

Managing Small Projects

A project management workflow diagram written on yellow sticky notes

Project management best practices can easily be applied on small projects to enable you to plan and manage your project successfully.

The Four Stages of Recovering a Project

Road sign reading Road to Recovery

If a project is in trouble, the project manager needs to work to recover it and get back on track. Four steps will help the PM facilitate the recovery.

The Most Common Sourcing RFP Mistakes

Manager passing a document to a colleague

Five of the most common mistakes in internally developed RFPs and how companies can better manage these issues by improving their RFP processes.

Effective Project Communications

Business people shaking hands, finishing up a meeting

Communication is something to think about every day. Are your messages clear? Have you provided enough context? Are your expectations for any outcome apparent?

PROJECT SMART is the project management resource that helps managers at all levels improve their performance. We provide an important knowledge base for those involved in managing projects of all kinds. With weekly exclusive updates, we keep you in touch with the latest project management thinking.

WE ARE CONNECTED ~ Follow us on social media to get regular updates on what's happening in the world of project management.


Latest Comments

Mel commented on…
Successful Project Management: Eight Simple Steps to Follow
- Thu 27 August 3:39am

John Reiling commented on…
Seeing the Project Through to the End
- Mon 24 August 6:07pm

Duncan Haughey commented on…
Protecting Sensitive Project Information
- Thu 20 August 2:57pm

Latest tweets

General Project Management • MSc Research Survey https://t.co/rB4KxCJhCF #pm #projectsmart about 4 days ago

Generating Momentum in a Project http://t.co/KOt91O1Q1m #pmot #projectsmart about 4 days ago

General Project Management • Re: Moving From an Environmental Consultant to a Project Manage... https://t.co/LGFGoSItIK #pm #projectsmart about 5 days ago