From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

PRINCE2 - Structure

PRINCE2 (PRojects IN Controlled Environments) is a structured project management method[1] and practitioner certification programme. PRINCE2 emphasises dividing projects into manageable and controllable stages.

It is adopted in many countries worldwide, including the UK, Western European countries, and Australia.[2] PRINCE2 training is available in many languages.[3]

PRINCE2 was developed as a UK government standard for information systems projects. In July 2013, ownership of the rights to PRINCE2 was transferred from HM Cabinet Office to AXELOS Ltd, a joint venture by the Cabinet Office and Capita, with 49% and 51% stakes respectively.[4]


PRINCE was derived from an earlier method called PROMPT II (Project Resource Organisation Management Planning Techniques). In 1989 the Central Computer and Telecommunications Agency (CCTA) adopted a version of PROMPT II as a UK Government standard for information systems (IT) project management. They gave it the name 'PRINCE', which originally stood for "PROMPT II IN the CCTA Environment". PRINCE was renamed in a Civil service competition as an acronym for "PRojects IN Controlled Environments". It soon became regularly applied outside the purely IT environment, both in UK government and in the private sector around the world.[5] PRINCE2 was released in 1996 as a generic project management method.[6] PRINCE2 has become increasingly popular and is now a de facto standard for project management in many UK government departments and across the United Nations system.[7] In the 2009 revision, the acronym was changed to mean 'PRojects IN a Controlled Environment'.

There have been two major revisions of PRINCE2 since its launch in 1996: "PRINCE2:2009 Refresh" in 2009, and "PRINCE2 2017 Update" in 2017. The justification for the 2017 update was the evolutions in practical business practices and feedbacks from PRINCE2 practitioners in the actual project environment.[8]

Overview of PRINCE2[edit]

Six Aspects[edit]

These aspects are also called tolerances or performance goals. They quantify the project tolerance and are considered during decision-making processes. In some organizations these can be KPIs. In the following table project level tolerances are summarized:[9]

Tolerance Type maintained in the project level Example
scope Project Plan The printer should print the documents only in black/white
timescale Project Plan The project/stage/team plan cannot last longer than 3 months
risk Risk Management Approach Printer might not work if it is in water
quality Project Product Description Printer should print at least 10 different standard page sizes
benefits Business Case Printer should be set up by the customer 10% faster than the ones from the competitors, and it must be 10% cheaper
cost Project Plan The cost of the project should not exceed £100,000

Benefits can have as target the cost of the benefit, but the cost tolerance above is related to the cost of the project, not the cost of the benefit.

Each management level is checked against these tolerances, coming from the upper level.

Management Level Tolerance type authorized to the lower level Exception type addressed to upper level plan type
Corporate/Programme project tolerance n/a programme
Project Board stage tolerance project exception project plan
Project Manager work package tolerance stage exception stage plan
Team Manager n/a issue team plan

Seven Principles[edit]

PRINCE2 is based on seven principles and these cannot be tailored. The PRINCE2 principles can be described as a mindset that keeps the project aligned with the PRINCE2 methodology. If a project does not adhere to these principles, it is not being managed using PRINCE2.

  1. Continued Business Justification: The business case is the most important document, and is updated at every stage of the project to ensure that the project is still viable. Early termination can occur if this ceases to be the case.
  2. Learn From Experience: each project maintains a lessons log and projects should continually refer to their own and to previous and concurrent projects' lesson logs to avoid reinventing wheels. Unless lessons provoke change, they are only lessons identified (not learned).
  3. Defined Roles and Responsibilities: Roles are separated from individuals, who may take on multiple roles or share a role. Roles in PRINCE2 are structured in four levels (corporate or programme management, project board, project manager level and team level). Project Management Team contains the last three, where all primary stakeholders (business, user, supplier) need to be presented.
  4. Manage by Stages: the project is planned and controlled on a stage by stage basis. Moving between stages includes updating the business case, risks, overall plan, and detailed next-stage plan in the light of new evidence.
  5. Manage by Exception: A PRINCE2 project has defined tolerances (6 aspects above) for each project objective, to establish limits of delegated authority. If a management level forecasts that these tolerances are exceeded (e.g. time of a management stage will be longer than the estimated time in the current management stage). it is escalated to the next management level for a decision how to proceed.
  6. Focus on Products: A PRINCE2 project focuses on the definition and delivery of the products, in particular their quality requirements.
  7. Tailor to Suit Project Environment: PRINCE2 is tailored to suit the project environment, size, complexity, importance, time capability and risk. Tailoring is the first activity in the process Initiating A Project and reviewed for each stage.

Not every aspect of PRINCE2 will be applicable to every project, thus every process has a note on scalability. This provides guidance to the project manager (and others involved in the project) as to how much of the process to apply. The positive aspect of this is that PRINCE2 can be tailored to the needs of a particular project. The negative aspect is that many of the essential elements of PRINCE2 can be omitted sometimes resulting in a PINO project – Prince in Name Only

Seven Themes[edit]

Theme Related to the Principle Explanation Management Products
Business Case Continued Business Justification Establishes mechanisms to judge whether the project is desirable, viable and achievable.
  • PID
  • Benefits Management Approach
Organisation Defined Roles and Responsibilities Define and establish the project's structure of accountability and responsibilities.
  • PID
  • Communication Management Approach
  • Defined Roles and Responsibilities
  • Focus on Products
  • Learn From Experience
Define and implement the means by which the project will verify that products are fit for purpose.
  • Quality Register
  • Quality Management Approach
  • Continued Business Justification
  • Manage by Stages
  • Manage by Exception
  • Defined Roles and Responsibilities
  • Learn from Experience
Facilitate communication and control by defining the means of delivering the products.

Product-Based Planning contains following steps:

  • Project Product Description (part of Project Brief and refined in the PID)
  • Product Breakdown Structure (minimum requirement)
  • Product Description
  • Product Flow Diagam

The last three are done for all levels of plan (project plan, stage plan and team plan)

  • Continued Business Justification
  • Defined Roles and Responsibilities
  • Learn from Experience
Identify, assess and control uncertainty and improve the ability of the project to succeed.
  • Risk Register
  • Risk Management Approach
  • Continued Business Justification
  • Defined Roles and Responsibilities
  • Learn from Experience
Identify, assess and control any potential and approved changes to the project baselines.
  • Issue Register
  • Change Control Approach
  • Manage By Exception
  • Manage by Stages
  • Continued Business Justification
  • Learn from Experience
To monitor and compare actual achievements against those planned.
  • Baselines for progress control: Project, Stage and Team Plans
  • Review: Issue Register, Product Status Account, Quality Register, Risk Register
  • Reporting: Checkpoint Report, Highlight Report, End Stage Report, End Project Report

Seven Processes[edit]

  • Starting Up A Project, in which the project team is appointed including an executive and a project manager, and a project brief is produced
  • Initiating A Project, in which the business case refined and Project Initiation Documentation assembled
  • Directing A Project, which dictates the ways in which the Project Board oversees the project
  • Controlling A Stage, which dictates how each individual stage should be controlled, including the way in which work packages are authorised and distributed
  • Managing Product Delivery, which has the purpose of controlling the link between the Project Manager and the Team Manager(s) by placing formal requirements on accepting, executing and delivering project work.[10]
  • Managing Stage Boundaries, which dictates how to transition from one stage to the next
  • Closing A Project, which covers the formal decommissioning of the project, follow-on actions and evaluation of the benefits.

Management Products[edit]

The PRINCE2 manual contains 26 suggested templates for documentation associated with the project, which it terms management products and which are divided into baselines, records and reports. Some examples of management products are:

  • Benefits Management Approach (In 2009 Edition it was called Benefits Review Plan): defines how and when a measurement of the project's benefits, expected by the Senior User, can be made.
  • Business Case: used to capture financial justification for the project. It is a PRINCE2 principle that a project must have continued business justification. As soon as a Business Case fails to make sense, change or stop that project.
  • Checkpoint Report: a progress report created by the Team Manager and sent to the Project Manager on a regular basis to report the status of the Work Package.
  • Communications Management Approach (In 2009 Edition it was called Communications Management Strategy): a description of the methods and frequency of communication to stakeholders, covering the flow of information in both directions to and from stakeholders (Information required to be provided from the project and information required to be provided to the project).
  • Configuration Item Record: provides a record of the product History, Status, Version, Variant, Details of any relationships between items/products, and Product owner/Product copy holders.
  • Change Control Approach (In 2009 Edition it was called Configuration Management Strategy): used to identify how the project's products will be identified, controlled and protected, this document is created by the Project Manager in the Initiating a Project process.
  • Daily Log: used to record informal issues.
  • End Project Report: reviews how the project performed against the original Project Initiation Documentation (PID)
  • Issues Register: an issue log of notes about change requests, problems and complaints sent by all project members.
  • Lessons Log: a set of notes of lessons learned which may be useful to future projects
  • Project Brief: used by the Project Board to authorize the Initiation Stage (1st stage of the project). In the Initiating a Project process, the contents of the Project Brief are extended and refined and the Project Brief evolves to form the Project Initiation Documentation (PID)
  • Quality Register: details of all planned quality control activities, dates, and personnel involved.
  • Risk Register: a record of identified risks (threats and opportunities) relating to the project

Integration with other techniques[edit]

The 26 Management Products described by PRINCE2 are only used for the "high-level" management of the project. Within its tasks, task managers must still decide on their own project management framework. Some suggestions given in the PRINCE2 manual are product based planning, change control, quality review technique, Gantt charts, PERT charts and critical path analysis.

PRINCE2 can also be used to manage projects that use agile software development methods.[11]

Quality review technique[edit]

The quality review technique ensures a project's products are of the required standard (i.e. meet defined quality criteria). This takes place in a quality review meeting, which identifies errors in the product. The quality review meeting will not attempt to solve the problems it identifies. The meeting brings together people who have an interest in the project's outputs (or products) and people on the project team able to address issues identified.

Differences between 2009 and 2017 versions[edit]

2009 version 2017 version[9] type
Benefits Review Plan Benefits Management Approach management product
Communication Management Strategy Communication Management Approach management product
Risk Management Strategy Risk Management Approach management product
Quality Management Strategy Quality Management Approach management product
Provisional Plan Contingency Plan management product

PRINCE2 Agile[edit]

PRINCE2 Agile is extension to the original PRINCE2 how to adapt PRINCE2 so that it can be deployed when using with agile behaviours, frameworks and additional techniques. An agile framework (e.g. SCRUM) is a project environment. This way an agile framework is made manageable by a project management method. Agile frameworks define neither decision-making governance, nor risk management. PRINCE2 on top of an agile framework fills this gap.[12]

Basically it uses following techniques:[11]

  • Cynefin framework to understand the complexity of the project to find out whether classical, process-based PRINCE2 or agile framework based PRINCE2 shall be used. It is used during the Starting Up a Project and Initiating a Project process.
  • Agilometer as a vehicle to understand how much tailoring and agility to be used in the PRINCE2 project, with focus on estimating the risk response performance of the project. It is reviewed, eventually updated during the Managing Stage Boundary process.
  • Scrum for timebox-based, Kanban for flow-based work package management.

Training and Certifications[edit]

PRINCE2 certifications, awarded by AXELOS, require the user to undertake a training course with an Accredited Training Organization (ATO) followed by an exam. The training and exam may be online or in person.[13] AXELOS requires that any organisation providing official PRINCE2 training must go through an accreditation process in order to validate the quality of the course content and delivery. Once approved, the organisation can use the title Accredited Training Organisation (ATO).[14] Trainers must be re-accredited every 3 years and undergo a surveillance check every 12 months.[15]

There are four levels of certifications for PRINCE2:[16]

  1. PRINCE2® 2017 Foundation: confirms the holder has sufficient knowledge and understanding of the PRINCE2 method to be able to work in a project management team working with this method.
  2. PRINCE2® 2017 Practitioner: confirms the holder has achieved sufficient understanding of how to apply PRINCE2 in a scenario situation and will, with suitable direction, be able to start applying the method to a real project. Qualified PRINCE2 Practitioners who go on to study for the APMP qualification of the Association for Project Management (APM) are exempt from certain topics of the syllabus that are covered in the PRINCE2 Practitioner qualification.[17] In the exam 38 out of 68 questions must be answered correctly (55%). If the examinee takes the exam in his native language, the exam duration is 150 minutes. Otherwise it is 188 minutes. The weighting of the questions: 35 questions from the theme, 25 questions from the processes, 8 questions from the principles. The test exams offered by Axelos and test centers include all the aspects of the real exam. It is strongly advised to the examinees to read the book and go through the test exam many times.
  3. PRINCE2® Agile Foundation: was released in June 2018 and confirms the holder has sufficient knowledge and understanding of the PRINCE2 method and agile way of working and how agile can be combined to PRINCE2.
  4. PRINCE2® Agile Practitioner: confirms the holder is able to apply the project management principles of PRINCE2 whilst combining agile concepts such as Scrum and Kanban.

AXELOS publishes a successful candidate register which can be searched on the web.[18]

Advantages and criticisms[edit]

PRINCE2 provides a method for managing projects within a clearly defined framework, but project management is a complex discipline and using such a framework is no guarantee of a successful project.

Some of the advertised benefits of PRINCE2 are: increased quality of the finished products, efficient control of resources, avoidance of either "heroic" (under-regulated) or "mechanistic" (over-regulated) working, and increased confidence among the project team.

PRINCE2 is sometimes considered inappropriate for small projects or where requirements are expected to change, due to the work required in creating and maintaining documents, logs and lists. The deliverable structure may also lead to focus on producing deliverables for their own sake, to "tick the boxes" rather than do more useful work.

The general response of PRINCE2's authors to criticism has been to point out that the methodology is scalable and can be tailored to suit the specific requirements and constraints of the project and the environment.[19] This strong emphasis on tailoring has led some users to complain that PRINCE2 is unfalsifiable, i.e. it is impossible to tell whether PRINCE2 "works" or constitutes "best practice" if any problems encountered with a project can be blamed on inappropriate application of PRINCE2 rather than on PRINCE2 itself.

The experiences of the Blair administration in the UK between 1997 and 2007 (and of subsequent UK governments) arguably undermine PRINCE2's claim to be "best practice", given the string of high-profile failed IT projects charged to the taxpayer during that time,[20][21][22] and the controversy surrounding the financial relationship between the Blair government and PRINCE2's co-owners Capita.[23][24] PRINCE2's training material addresses these failures, blaming them on inappropriate tailoring of PRINCE2 to the project environment, and advocating for more PRINCE2 training for government project managers to solve the problem.

Differences from PMP[edit]

Project Management Professional (PMP) may be seen as a competitor of PRINCE2. In general, UK, Australia and Europe prefer PRINCE2, and the US and American countries prefer PMP. Asia, Africa and the Middle East area have no strong preference for PMP or PRINCE2. The important thing is that PMP (PMBOK) can be used with PRINCE2.

PRINCE2 and PMP acknowledge each other's existence in their advertising material and attempt to position themselves as complementary products – PRINCE2 as a "methodology" and PMP as a "standard"[25] – which can be used alongside each other. In practice, companies and practitioners choose one system or both depending on the project environment, their geographical location and costs involved.

See also[edit]


  1. ^ "What is PRINCE2®?". AXELOS. Retrieved 1 February 2017.
  2. ^ PRINCE2® - PRojects IN Controlled Environments - Consulting Organisations List
  3. ^ "PRINCE2 STUDY Guide) ® Handbook" (PDF). Project Management Institute. Retrieved 15 December 2017.
  4. ^ Reid, Amy (30 July 2013). "Capita acquires majority stake in ITIL and PRINCE2". Association for project management. International project management association. Archived from the original on 30 January 2016. Retrieved 22 February 2016. AXELOS has been revealed as the name of the new joint venture between Capita and the Cabinet Office set up to manage the best management practice training tools and accreditations, including PRINCE2, and ITIL. [...] Capita and the Cabinet Office have established a 51:49 per cent stake in the new organisation that will own the intellectual property (IP) of this portfolio of products [...]
  5. ^ OGC - PRINCE2 - News
  6. ^ "OGC brings its shining quartet back into the limelight" (Press release). Office of Government Commerce. 14 December 2005.
  7. ^ Official PRINCE2 website
  8. ^ "Introducing the PRINCE2 2017 Update" (Press release). Axelos. 11 December 2017.
  9. ^ a b "Managing Successful Projects with PRINCE2, 2017 Edition". Axelos.
  10. ^ PRINCE2 manual
  11. ^ a b "PRINCE2® Agile". Axelos. Archived from the original on 15 March 2015. Retrieved 6 March 2015.
  12. ^ "PRINCE2 Agile®". Axelos.
  13. ^ [1]
  14. ^ Find an Accredited Provider
  15. ^ - PRINCE2 accreditation scheme
  16. ^ PRINCE2 2017 update from AXELOS
  17. ^ "- APMP for PRINCE2 Practitioners". Archived from the original on 1 November 2013. Retrieved 30 October 2013.
  18. ^ AXELOS Successful Candidates Register
  19. ^ OGC Best Management Practice - PRINCE2
  20. ^ "The Blair IT projects".
  21. ^ The Blunders of our Governments. 2013. ISBN 978-1780742663.
  22. ^ "The costly trail of British government IT and 'big bang' project disasters".
  23. ^ "Blair avoids MPs' questions on Capita".
  24. ^ "Capita chairman quits after criticism of loans to Labour".
  25. ^ "Project Management Professional (PMP) ® Handbook" (PDF). Project Management Institute. Retrieved 18 September 2009.

External links[edit]