The History of PRINCE2

By Victor Hoang · Updated Oct 24, 2026

Picture October 1971. Parliament's Select Committee on Science and Technology reported on how government used computers. Out of that report came a new body in 1972. Its job was to bring the central computing functions of government together. Its descendants now sell a certification used around the world.

PRINCE2 has a commercial ancestor and a government parent. The ancestor is PROMPT, a method that accounts date to 1975 and credit to a company called Simpact Systems. The parent is the UK government's computer agency. It turned that method into PRINCE in 1989 and published the broader PRINCE2 in 1996. The throughline: a method built to stop government computer projects slipping became a general-purpose standard. It then changed hands from a civil service agency to a joint venture and finally to a private certification company.

This article follows the path between those two points. For the wider field, see the history of project management. For how the method works today, see the PRINCE2 methodology.

Timeline at a Glance

The PROMPT Years (1972-1988)

A commercial method waits for a government customer

The agency that would own PRINCE had a plain beginning. The National Archives' catalogue says the Central Computer Agency was established on 1 April 1972, following the Select Committee's report of October 1971, to bring together the central functions concerned with the use of computers in government. It absorbed the Civil Service Department's computer management division, the procurement division and the central computer bureau of the Stationery Office, plus a technical support unit from the Department of Trade and Industry. In 1973 it took on telecommunications policy as well. The agency's own entry adds that it changed its name to the Central Computer and Telecommunications Agency in 1979, passed to the Treasury in 1981, and by 1992 had its initials expanded to "the Government Agency for Information Systems".

Meanwhile a commercial method was taking shape elsewhere. One account on the PRINCE2 FAQ page says PRINCE was developed from PROMPT II, a project management method created by Simpact Systems Ltd in 1975. That account is retrospective, and the date rests on it alone. The shape of the relationship is clearer. PROMPT was a company's product. It was not a government standard, and it was not called PRINCE.

The same FAQ says the CCTA adopted PROMPT II in 1979 as the standard for government information systems projects. Treat that date with care. The documented event of 1979 in the agency's own catalogue entry is the renaming, and the accounts that give 1979 for the adoption cite no dated record of it. The firmer claim is the one that follows: in 1989, according to the same FAQ, PRINCE replaced PROMPT II in government projects.

This is where precursor and method need separating. Pyramid crews and Roman builders also planned work, and our piece on ancient megaprojects covers that older record. PROMPT is different in kind: a named, packaged method for managing computer projects, sold by a company and later adopted by a government. It is the nearest documented ancestor of PRINCE2, and the one the history has to start with.

What this means for teams today: a method that governments or large firms standardize usually started as someone's practical product. If your own team's working habits keep proving useful, writing them down is how a private habit becomes a standard.

The Government Standard (1989-1995)

PRINCE becomes the civil service's own method

PRINCE stands for PRojects IN Controlled Environments. Its first job was narrow: the government's information systems projects. Ten years after the agency took the name CCTA, the method came under its own roof.

What did PRINCE add to the picture? The catalogue records show a method surrounded by companion publications. HMSO, the government's publisher, issued a 1993 CCTA guide on using the CRAMM risk analysis method with PRINCE. A 1995 record in the Internet Archive's catalogue shows a guide on using Euromethod with TAP, PRINCE and SSADM. SSADM was the structured analysis and design method then used in UK public sector IT. Taken together the records say that PRINCE was one piece of a toolkit rather than a stand-alone book: methods for analysis and design, for risk, and for managing the work itself.

The agency itself existed because the government wanted central control over how it used computers, and a project method is that wish applied to a single project. The method describes a project in stages, with defined roles and a clear idea of who decides what, and a common vocabulary of that kind is what lets many departments work to the same rules.

What PRINCE could not do was escape its origin. The method was written by and for information systems people, and the 2016 study by Jamali and Oveisi in Modern Applied Science says plainly that it was developed by the CCTA for IT projects and only later widened. A method like that carries its origin in its vocabulary.

What this means for teams today: a method written for one kind of work carries that work's assumptions. When you borrow a method, ask who it was written for and what they took for granted.

The Rewrite (1996-2008)

The method leaves the computer room

The turning point is 1996. The Jamali and Oveisi paper says an analysis in 1996 extended the method's range from IT projects to any type of project. The product of that analysis was PRINCE2. A catalogue record lists a CCTA "PRINCE Manual" dated 1996 from the Stationery Office, and a 1997 CCTA publication, PRINCE 2: an outline, carries Colin Bentley's name in its catalogue entry. Bentley went on to write several practical guides to the method, including Practical PRINCE 2 in 1998 according to the same catalogue.

The broader scope changed what the method had to be. A product for IT projects could assume a software vocabulary. A product for any project could not. PRINCE2 had to describe a project in terms any sector could recognize and leave the technical specifics to the people doing the work. That is the single largest idea in the history: a management method gets to be a standard by saying less about the work and more about control.

The author on the title page changed. The catalogue records show the Office of Government Commerce as the author of the editions of Managing Successful Projects with PRINCE2 in 2002 and 2005. PeopleCert's later account says the 2005 version had eight processes.

Elsewhere in the profession a rival body of knowledge was growing. PMI had its guide, and our article on PMI and the PMBOK Guide tells that story. The two followed different paths: a professional association writing down what practitioners know, and a government agency writing a method to be applied. For the wider comparison, see the evolution of project management methodologies.

What this means for teams today: generalizing a method costs detail. If your internal process was built for one department, expect to remove its jargon before another department will use it.

The Joint Venture Years (2009-2020)

Fewer processes, then a change of owner

The 2009 edition made the method smaller. PeopleCert's own account says PRINCE2 has had seven core processes since the 2009 edition, reduced from eight in 2005. The catalogue also lists a companion volume, Directing Successful Projects with PRINCE2, for 2009, whose title points to the directing role rather than day-to-day management. The record shows a method adding a book on directing while cutting its own process count.

Ownership then moved. PeopleCert's 2021 announcement describes AXELOS as a joint venture company created in 2013 by the Cabinet Office. Capita's announcement of the sale gives the split: Capita 51 percent and the Cabinet Office 49 percent, with the business responsible for methodologies including PRINCE2 and ITIL. The method that a civil service agency had written in the 1980s and 1990s was now run as a commercial venture with a government minority holder.

A new edition followed: the catalogue lists a 2017 Managing Successful Projects with PRINCE2 from AXELOS. Agile delivery was spreading through the same years. Our pages on the agile methodology and the waterfall approach show the two ends of that argument, the history of the waterfall model traces where the staged approach came from, and the history of hybrid project management shows where many teams landed. PRINCE2 7 later lists compatibility with Agile, Lean and ITIL among its updates, which shows how that question was eventually answered.

What this means for teams today: a mature method has two ways to survive: add more or cut back. PRINCE2's own record, from eight processes to seven, is the argument for cutting. Review your own playbook the same way once a year.

The PeopleCert Era (2021-present)

A private certifier takes over and ships version 7

On 21 June 2021 Capita announced that it and the Cabinet Office had agreed to sell AXELOS to PeopleCert. The release says the deal values the joint venture at £380.0m on a cash-free, debt-free basis. A week later the Cabinet Office published a departmental minute of contingent liability relating to the sale of its stake. The government's stake in the method, which traces back to a 1972 agency, was being sold.

PeopleCert's pre-launch notice calls the PRINCE2 7 release "biggest launch since the acquisition of Axelos in 2021", and says the method is trusted by over a million certified professionals. Training and certification for the new version were available from 4 September 2023, and the company unveiled PRINCE2 7 at an event in London on 11 October 2023, where a PeopleCert executive framed the update against disruption across sectors.

The release lists seven updates: guidance that applies to everyone involved in projects, current AI guidance, more emphasis on people management, more flexibility and customization, digital tools and data management, sustainability built into project performance, and compatibility with Agile, Lean and ITIL. PeopleCert's evolution article adds that PRINCE2 7 keeps the same seven processes after practitioner feedback said they were working well.

Read that list against the history. A method written to control government computer projects now lists AI and sustainability among its updates. The scope grew from one department's IT in 1989, to any project in 1996, to anyone involved in a project in 2023. The core, seven processes, survived every change of owner.

What this means for teams today: the stable core and the shifting edges are the pattern to copy. Keep the handful of controls that work, such as stages, defined roles and a business case, and let the surrounding guidance change with the work you actually do.

Key People

Key Facts

• The Central Computer Agency was established on 1 April 1972 and took the CCTA name in 1979.
• One account dates PROMPT II to 1975 and says PRINCE replaced it in government in 1989.
• A 1996 analysis extended the method from IT to any type of project.
• PRINCE2 has had seven processes since the 2009 edition, down from eight in 2005.
• AXELOS was a 51/49 Capita and Cabinet Office venture when a 2021 deal valued it at £380m.
• PRINCE2 7 training became available on 4 September 2023.

The Pattern Behind the History

This is our synthesis, not published research. Five points repeat across the story of PRINCE2:

• A private tool becomes a public standard. PROMPT was a company's product before it was a government method.
• Scope widens by saying less. Moving from IT projects to every project meant dropping technical detail and keeping control.
• Ownership moves, the core stays. Agency, Office of Government Commerce, joint venture and PeopleCert each stood behind the method, and the seven processes survived.
• Companion material grows around the method. CRAMM, SSADM, a directing guide and later certification all sit beside the manual.
• The edges change with the era. Risk guides in the 1990s, agile compatibility in the 2010s, AI and sustainability in 2023.

What It Teaches Teams Today

• Keep a stable core. Seven processes lasted through four owners. Decide which few controls in your own method are not up for debate.
• Say what the method is for. PRINCE began as an answer to uncontrolled computer projects. A playbook that cannot name its problem will not survive a change of manager.
• Separate the core from the guidance. The method stayed; the surrounding material moved. Put your non-negotiables in one short page and the examples elsewhere.
• Write for the sponsor too. The 2009 directing guide recognized that the people who fund a project need their own instructions, not just the project manager.
• Know where your method came from. If you're comparing PRINCE2 with the PMBOK Guide, remember one grew from an association of practitioners and the other from a government agency, and that explains much of how they read. For credentials, see the history of the PMP certification.