The History of the PMP and Project Certifications

By Victor Hoang · Updated Oct 24, 2026

Picture a conference exam in Philadelphia in October 1984. Project management had a growing institute but no credential. Eric Jenett, a vice president at Brown & Root in Houston, was one of the institute's founders. He earned the first Project Management Professional credential, PMP number one.

The first Project Management Professional (PMP) exam was held on October 6, 1984, at the PMI '84 conference in Philadelphia. Fifty-six people sat it that day, and 43 people passed it. It came out of a volunteer standards effort inside the Project Management Institute (PMI). It set off a long line of rivals: a European competence ladder, a British government method with its own exams, and Scrum certificates sold on a different promise.

The throughline is a question every credential keeps answering again: are you certifying what a person knows, what they've done, or how they work? This article follows how that exam was designed, how it spread, who audited it, who competed with it, and why its content outline was rewritten in 2021 and again in 2026. For the field as a whole, see the history of project management.

Timeline at a Glance

The Craft Tests (Antiquity-1960s)

Guilds and emperors certified skill, not project managers

The oldest test of competence for a large organization in this story belongs to China. The Qin dynasty built the first centralized bureaucratic empire and needed a way to staff it, and Britannica says the Han court went further: in 124 BCE Emperor Wudi set up an imperial university to train and test officials in Confucian government. The Sui dynasty applied the system more systematically, the Tang made the jinshi exam the main route to high office, and under the Song the exams ran on a three-year cycle after 1065. The system lasted until the Qing abolished it in 1905.

Europe's answer was the guild. Britannica describes the medieval craft guild as a hierarchy of masters, journeymen and apprentices. An apprentice served five to nine years without pay, became a journeyman who worked for wages, and could rise to master only by proving technical competence with a "masterpiece". Guilds also set quality standards and policed their members' workmanship, and Britannica says they flourished in Europe between the 11th and 16th centuries.

The modern echo is closer to the PMP's shape. In 1907 Wyoming passed the first engineering registration law, and NSPE says a licensed engineer today completes a degree, passes two exams and works four years under a PE. Experience plus an exam is a pattern the PMP would later share, though not through any law.

Be clear about what these were. Examiners certified officials, and guilds certified craftsmen. Nobody certified project managers, because nobody used the title yet. Builders of pyramids and aqueducts coordinated large work, as our piece on ancient megaprojects shows, but no test existed for the person in charge. The modern job took shape in the twentieth century, as the project management timeline lays out.

What this means for teams today: a credential has always been a bargain between a profession and the people who rely on it. Ask what a certificate actually proves, because the answer has changed every time the profession has.

The ESA Years (1969-1984)

Volunteers write the rules, then sit the first exam

PMI began in October 1969, when five people (James Snyder, Eric Jenett, Gordon Davis, E.A. "Ned" Engman and Susan Gallagher) are recognized as founders after a first formal meeting at Georgia Tech in Atlanta. The founders wanted a place to share planning and scheduling practice. A credential came later, after a decade of growth that included PMI's first Seminars & Symposium and an international meeting in Toronto in 1978.

The credential itself began as a volunteer project. Francis Webster, writing in PM Network in 1994, records that in 1981 a project team was assigned the job of developing standards, ethics and accreditation, at the suggestion of Matthew Parry, a past PMI president. Its report, ESA, was published in the August 1983 special issue of Project Management Quarterly. It proposed a code of ethics and a framework of knowledge areas (human resources, cost, time, communication, scope and quality), and it recommended a certification program.

Members wanted it. The first report of the Certification Committee, chaired by M. Dean Martin, appeared in December 1983 and found that 86 percent of members surveyed favored some type of certification. A detailed plan followed in March 1984. It let candidates earn points toward certification in three ways: education, experience and service to the profession. A planning meeting had already been held in Cullowhee, North Carolina, in June 1982, and the authors of PMI's ten-year review write that nobody there anticipated the program's eventual impact.

Then came the exam in Philadelphia. Fifty-six candidates took it, 43 passed, and the 43 became the first PMPs. A 2001 PM Network article puts the first sitting at about a dozen people, which doesn't match the 56 and 43 in PMI's program history, so this article uses the program history's counts: 43 certified in 1984, 28 in 1985 and 35 in 1986.

The new problem was a missing document. A credential needs something to test against, and the first body of knowledge was still a draft. The August 1986 special issue of Project Management Journal presented it, under the direction of R. Max Wideman. PMI's board approved the revised draft on March 28, 1987, effective September 1, 1987, and Webster says that product became the basis of the certification program. The standard itself has its own story, told in the history of PMI and the PMBOK Guide, and the guide as it stands today is covered in our PMBOK Guide article.

What this means for teams today: the PMP began as a project with a plan, a team, a survey and a deadline. If you're building an internal certification, start the way PMI did, by asking people who'll sit it whether they want it.

The Slow Climb (1985-1998)

Employers start asking for the letters

For years the PMP grew modestly. The program's own history shows annual new PMPs of 109 in 1988, 138 in 1990 and 253 in 1991, then 502 in 1992 and 811 in 1993, when 39.4 percent of all PMPs ever awarded had been earned in that single year. By the end of 1993 the cumulative total was 2,060. In June 1994, 750 people sat the exam in a single sitting and 2,630 designations had been awarded.

What drove it was corporate acceptance. Williamson and Ireland listed seven organizations that had formally accepted the program for their employees: AT&T/NCR, Digital Equipment Corporation, EG&G, GTE, Rust International, The Analytical Science Corporation and US West. A 1993 survey of PMPs was candid about the value. When asked whether the PMP helped them get their current position, 27.4 percent said yes and 67.1 percent said no. One respondent called the PMP the "only game in town" for a professional project manager seeking an association credential.

Elsewhere, two other traditions were forming. In Europe, a group of project pioneers had met in 1964 to discuss the critical path method, and in 1965 they founded what became IPMA, officially located in Switzerland. It was renamed IPMA in 1996 and began certifying individuals in 1998 with the first version of its competence baseline. IPMA's own account of its four-level scheme says the idea took shape in 1995, so the two years describe different steps. The ladder it built runs from Level D, Certified Project Management Associate, through Level C (Project Manager) and Level B (Senior Project Manager) to Level A (Projects Director). By 2015, Reinhard Wagner, a past IPMA president, wrote that more than 250,000 certificates had been awarded across all four levels, and he argued that knowledge-based certification is easier, faster and cheaper than competence-based certification, but proves less.

In Britain the credential came attached to a method. At a 1997 IET colloquium on professionalism in project management, P. Newman described PRINCE as originally meant for public-sector IT projects and by then a de facto standard. In 1996, he said, the CCTA launched PRINCE2 after a two-year development involving more than 150 organizations, and the new version was no longer specific to IT. Its exams, as a PRINCE2 FAQ from the APM Group era sets them out, were two papers: a one-hour Foundation exam and a three-hour open-book Practitioner exam. That two-step shape survives, since PeopleCert today lists PRINCE2 Project Management Foundation and Practitioner at Version 7. For the method itself, see PRINCE2 explained.

A 2001 PMI article lists the field as it stood. England's Association for Project Management offered a Certificated Project Manager designation, and the Australian Institute of Project Management launched its competency-based RegPM program in April 1997. The same article records PMI's annual numbers rising from 4,500 qualified in 1997 to 18,000 in 2000.

The new problem was meaning. If employers demanded the letters, what did the letters guarantee? MaryGrace Allenchey, chair of PMI's Certification Board, said in a 2001 PM Network piece that certification guarantees experience but doesn't mean a candidate will internalize project management.

What this means for teams today: when a credential becomes a hiring filter, it starts to measure whatever is easiest to check. Look at what your own job postings demand, and ask whether it's the skill or the certificate.

The Accreditation Age (1999-2010)

Standards bodies audit the exam itself

By 1999 the PMP had a growing following, and the next step was outside verification. In October 1999, PMI announced that its PMP Certification Program Department had attained ISO 9001 certification from The National Registry and the Dutch Council for Accreditation. The article calls it the first professional certification program in the world to receive that mark. The audit took six months, and it covered the whole department, including the PMP, the basic exam and the self-assessment test.

ISO 9001 audits a management system. The next step was to audit the way people are certified. In April 2007 PMI announced that the PMP credential program had earned ISO/IEC 17024 accreditation, a standard ISO had launched in 2002 and which the release said was endorsed by 85 countries. PMI called itself the first professional project management association to achieve it. The accreditation covers examination development and maintenance, plus quality management. PMI's current outlines word the accreditor differently: they say the PMP is accredited by the American National Standards Institute against ISO/IEC 17024, alongside ISO 9001.

Alongside the audit came a job analysis. A 2001 PMI article described a first-of-its-kind role delineation study, whose competencies would become the basis of the exam outline. The same article said a Certified Associate in Project Management (CAPM) was expected by January 2002 for practitioners who work with PMPs. By the 2007 release, PMI listed CAPM and the Program Management Professional (PgMP) as part of its range, with more than 218,000 PMP holders in over 160 countries. PMI's own history says the 50,000th PMP was awarded at its 2002 symposium to Carla Krieger Langsch of Porto Alegre, Brazil. For why program work earned its own credential, see program vs project management.

Specialist credentials followed. In July 2008, ProjectsAtWork reported that PMI had introduced the PMI Risk Management Professional (PMI-RMP), for project managers who specialize in risk. Applicants needed a bachelor's degree or equivalent and 3,000 hours of experience in project risk management, and the first exam window ran from August 29 to October 31, 2008.

The new problem was relevance. An audit shows that an exam is run consistently. It doesn't show that the content matches how projects are delivered.

What this means for teams today: a process audit is not a relevance audit. If you rely on a certificate, check both that it's run properly and that it still describes your work.

The Agile Split (2001-2019)

Scrum and agile credentials grow beside the PMP

This era overlaps the last one, because agile credentials started while the PMP was still being audited. Scrum Alliance says it was founded in 2001. Scrum.org says the Certified ScrumMaster course was developed by Ken Schwaber with the Scrum Alliance in 2002, and that in 2009 he designed the Professional Scrum Master course as a significant update to it. Two Scrum credentials, one framework, different rules. See what Scrum is for the method.

The model differed from the PMP's. Scrum.org's 2016 announcement restructured its Professional Scrum Master assessments into three levels (PSM I, II and III), set a minimum score of 85 percent, and noted that no class is required to sit the assessment. The Scrum Alliance route is built around its network of trainers, and the organization today describes a community of nearly 1.5 million professionals. Because the Scrum.org assessment was open to anyone, class or not, and was based on the Scrum Guide, it leaned on testing knowledge of the framework. The Agile Manifesto had set the values; these credentials taught ways to practice them.

PMI's reply came later. A conference paper from 2012 says PMI announced in October 2010 that agile practices had a place in every project manager's toolkit, and in May 2011 announced the PMI-ACP, with more than 550 members in the pilot exam. PM Network reported in December 2011 that PMI was granting its first batch of PMI-ACP credentials that month. PMI's history adds that, over the 2009 to 2019 decade, it also introduced the Professional in Business Analysis (PMI-PBA) and Portfolio Management Professional (PfMP) credentials. The PMI-ACP page today calls the exam agnostic across methods such as Scrum, Lean and Kanban.

Europe moved too. In 2015, IPMA released ICB4 and new versions of its standards. The ladder stayed at four levels, and Wagner wrote that the new baseline would open separate career paths for program and portfolio management.

The new problem was fragmentation. A project professional could now hold a knowledge badge, a competence level and a method certificate, none of which measured the same thing. The evolution of project management methodologies covers how the underlying methods split, and the credentials followed.

What this means for teams today: when you read a résumé, ask which of those three things each credential measures. A Scrum certificate, a PMP and an IPMA level answer different questions.

The Hybrid Exam (2021-present)

Half predictive, half agile, then AI joins the outline

On the PMP side, the turn came in January 2021. PMI's updated Examination Content Outline, developed after a global practice analysis and job task analysis, rebuilt the test around three domains: People 42 percent, Process 50 percent and Business Environment 8 percent. Its note on approaches was blunt: about half the exam would represent predictive approaches and the other half agile or hybrid, spread across all three domains rather than isolated in one. The outline also states that its task force was not bound by the PMBOK Guide.

PMI's reasoning came from the job task analysis, which found that practitioners worked in a variety of project environments and used different approaches. For the same shift seen from the practice side, see the history of hybrid project management.

PMI did it again in July 2026. Its page on the new exam says the update adds AI, sustainability and stakeholder engagement and shifts the domain weights to People 33 percent, Process 41 percent and Business Environment 26 percent. The 2026 outline sets the mix at approximately 40 percent predictive and the remaining 60 percent divided between adaptive/agile and hybrid. The outline says AI and sustainability were trends previously unaddressed in the exam. How AI is changing the work itself is covered in the history of AI in project management.

Holder counts show how far the credential has traveled. These readings are all PMI's own, each from a different year:

The other traditions continue in their own forms. PeopleCert, which now certifies PRINCE2, describes a Project Manager path of Foundation and Practitioner at Version 7. IPMA's four levels remain, with Level D still the starting point and Level A for experienced leaders of complex work.

The new problem is the old one. A wider outline asks a candidate to know more, and a multiple-choice exam still can't show how that person leads a real project through a real conflict.

What this means for teams today: treat a credential as a snapshot of what its makers valued in a given year. The 2021 and 2026 rewrites are evidence that even the largest credential keeps changing its mind.

Key People

Key Facts

• The first PMP exam was held on October 6, 1984, in Philadelphia, and 43 of 56 candidates passed.
• PMI's certification department received ISO 9001 certification in October 1999, after a six-month process.
• PMI announced ISO/IEC 17024 accreditation for the PMP in April 2007.
• The January 2021 outline said about half the exam is predictive and half agile or hybrid.
• The July 2026 outline sets about 40 percent predictive items and 60 percent agile or hybrid.
• IPMA reported more than 250,000 certificates across its four levels by 2015.

The Pattern Behind the History

This is our synthesis, not published research. Five points repeat across the history of project certification:

• A body of knowledge comes first. The ESA report and the first PMBOK draft had to exist before anyone could write an exam.
• Employers make a credential valuable. The PMP stayed small until companies such as AT&T and Digital Equipment accepted it for their staff.
• Every credential eventually gets audited. ISO 9001 in 1999 and ISO/IEC 17024 in 2007 checked the program, not the candidates.
• Rivals split by what they test. Knowledge, competence and method each found a certifier: PMI, IPMA, PRINCE2 and Scrum.
• The outline follows the practice, years late. PMI's own agile credential arrived in 2011, and the PMP outline gave agile and hybrid work half its weight only in 2021.

What It Teaches Teams Today

• Ask what a credential measures. A PMP, an IPMA level, a PRINCE2 Practitioner and a Scrum certificate answer different questions about the same person.
• Pair experience with a test. The PMP's mix of documented experience and an exam has the same shape as engineering licensure, and each half checks something the other can't.
• Don't let a letter replace a work sample. In PMI's 1993 survey, 27.4 percent of responding PMPs said the credential helped them get their position, and 67.1 percent said it didn't.
• Expect the content to change. If you require a certification, check its current outline, since the PMP's was rewritten in 2021 and again in 2026.
• Match the credential to your delivery model. A hybrid team may want people who can work across predictive and agile approaches, which is what both recent PMP outlines test.