PRINCE2
≈ 6 min read
Names in other languages
No names in other languages are held for this entry yet.
Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.
PRINCE2 (PRojects IN Controlled Environments) is a structured project management method 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. PRINCE2 training is available in many languages. PRINCE2 was developed as a UK government standard for information systems projects. In July 2013, ownership of the rights to PRINCE2 were transferred from HM Cabinet Office to AXELOS Ltd, a joint venture by the Cabinet Office and Capita, with 49% and 51% stakes respectively. In 2021, PRINCE2 was transferred to PeopleCert during their acquisition of AXELOS.
PRINCE2 (PRojects IN Controlled Environments) is a structured project management method 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. PRINCE2 training is available in many languages. PRINCE2 was developed as a UK government standard for information systems projects. In July 2013, ownership of the rights to PRINCE2 were transferred from HM Cabinet Office to AXELOS Ltd, a joint venture by the Cabinet Office and Capita, with 49% and 51% stakes respectively. In 2021, PRINCE2 was transferred to PeopleCert during their acquisition of AXELOS.
History
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". PRINCE2 is the second edition of the earlier PRINCE method which was initially announced and developed in 1989 by the Central Computer and Telecommunications Agency (CCTA), a UK government support agency. PRINCE2 was released in 19961 as a generic project management method. Since then, PRINCE2 became increasingly popular and is now a de facto standard for project management in many UK government departments and across the United Nations system. There have been three 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 evolution in practical business practices and feedback from PRINCE2 practitioners in the actual project environment. More recently, in 2023 AXELOS launched PRINCE2 7 - the 7th edition - which is described below.
Overview of PRINCE2
Seven aspects of project performance
These aspects are also called tolerances or performance goals. Tolerances define the delegated levels of authority which are set by a higher level of management to a lower level. The management level responsible must manage within the tolerances provided only as long as they are not forecast to be exceeded. Otherwise they are deemed to be an exception which requires escalating to the management level which delegated them. This way of managing is known as 'management by exception' and is one of the principles of PRINCE2. By managing in this way, it saves the time of senior management. In some organisations tolerances can be key performance indicators (KPIs). In the following table project level tolerances are summarised:
Seven PRINCE2 practices and the management products used to support each practice
Seven processes (who does what and when from start to finish)
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 is refined and project initiation documentation is assembled. Directing a project, in which the project board directs the project manager and oversees the project. Controlling a stage, in which the project manager authorises work packages to team managers, manages issues and risks, and reports progress to the project board. Managing product delivery, which provides an interface between the project manager and the team manager(s) by placing formal requirements on accepting, executing and delivering project work. Managing stage boundaries, in which the project manager prepares the information for the project board to decide whether to authorise the next stage or close the project. Closing a project, in which the project is the formally closed, follow-on actions are documented and assigned, lessons are learned, and benefits are evaluated.
People in PRINCE2
The 7th edition of PRINCE2 introduced a major new aspect to the method - the role of people. The purpose of a project is to deliver change, which will affect the people who perform business as usual (BAU) activities. How well the project delivers the change, depends on the capabilities of the project team, the strength of the relationships between them, and the people impacted by the change. For these reasons, PRINCE2 recommends that projects must incorporate change management to be able to successfully implement the change into the organization.
Integration with other techniques
The 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, Kanban boards, Gantt charts, PERT charts and critical path analysis. PRINCE2 can also be used to manage projects that use agile software development methods.
Quality review technique
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.
History of PRINCE2 editions
Below is a list of all the editions of PRINCE2. As of 1 January 2020, "PRINCE2 2017" was renamed "PRINCE2 6th Edition". Also, the previous edition, "PRINCE2 2009" was renamed "PRINCE2 5th Edition". There were no other changes except the name of the brand. The reason for the name change was to "ensure the format of the name is aligned with that used by other frameworks within the project management industry". As list of all versions of PRINCE2 are printed in the cover of the PRINCE2 manual: (*nth names added for other editions in order for context, but they were not referred to these names originally. However, they are referenced as such in the PRINCE2 manual cover page.)
See also
Agile software development Comparison of project-management software Gantt chart List of project management topics Work breakdown structure
References
External links
Guidelines for Managing Projects (fully consistent with PRINCE2) from the UK Department for Business, Enterprise and Regulatory Reform (BERR) PRINCE2.wiki
Text derived from https://en.wikipedia.org/w/index.php?oldid=1359078736 under CC BY-SA 4.0; modifications have been made.