The History of PMI and the PMBOK Guide

By Victor Hoang · Updated Oct 24, 2026

In early 1969, some practitioners sat down to dinner at the Three Threes Restaurant, a few blocks from City Hall in Philadelphia. According to PMI's own founders page, it was a continuation of months of talks between Jim Snyder and Gordon Davis. It ended with a decision. Project managers needed a way to associate, share information and discuss common problems.

The Project Management Institute began with a first formal meeting at Georgia Tech in Atlanta on 9 October 1969. Its Guide to the Project Management Body of Knowledge reached book form in 1996, after a committee report in 1983 and board-approved drafts in the 1980s. The throughline: a handful of practitioners with no professional home wrote down what they shared. The writing became the profession's standard. By 2021 that standard had to be rewritten because projects no longer fit one process.

Nobody at that dinner had a name for what they wanted to join, because the job they all did had no society, no exam and no agreed list of what a practitioner should know. This article follows how that dinner became PMI, how PMI wrote its guide, and what the guide's changes tell a team today. For the wider story of the field, see the history of project management. For how the guide works as a reference today, see the PMBOK Guide explained.

Timeline at a Glance

The Precursor Years (Antiquity-1968)

Builders and architects kept records, but nobody wrote a project manager's curriculum

Project professionals have long reached for the oldest possible ancestor. PMI's own journal published a 1985 history by R. Max Wideman that notes many in the field date it to King Zoser and the Saqqara pyramid before it turns to PMI's founding. The record from that world is real. Our piece on ancient megaprojects covers the work diary of a pyramid-era crew inspector, and a Roman architect named Vitruvius went further by writing down what an architect must know. He lists geometry, history, philosophy, music and law, and says that practice and theory are architecture's parents.

Vitruvius is the nearest ancient precursor to a body of knowledge, but he wrote for architects. The pyramid crews and Roman builders ran projects, and nobody called it project management. A written body of knowledge for managing projects as such needed a profession that did not yet exist.

That profession's tools came first. The network methods of the 1950s gave practitioners a shared technique, and the history of the critical path method and the history of PERT tell that side. Software followed. Ned Engman, one of PMI's founders, sold the McAuto Project Management System for a division of McDonnell Douglas, and PMI's 1994 profile says that meeting potential users of his product was among his interests in PMI.

A second body formed in Europe first. According to IPMA's own history, Pierre Koch of France invited colleagues from the Netherlands and Germany in 1964 to discuss the critical path method, and in 1965 the group founded what it called the International Management Systems Association, based in Switzerland. It later took the name INTERNET and, in 1996, became the International Project Management Association. Alan Stretton, who wrote a short history of modern project management, describes INTERNET as a forum for European network planning practitioners to exchange knowledge.

Accounts of PMI's own idea differ. Wideman's article says the idea of forming an organization came from Engman, Snyder and Susan Gallagher while working together in the fall of 1967 in Philadelphia. PMI's founders page puts the decisive dinner in early 1969. Both can be true: an idea in 1967, a decision in 1969.

What this means for teams today: a shared craft usually exists years before anyone writes it down. If your team keeps solving the same problems with the same private habits, you're sitting where project managers sat in 1967.

The Atlanta Meeting (1969-1980)

Five founders turn a dinner into an institute

The first formal meeting happened where it did because of a teacher and a student. J. Gordon Davis earned his doctorate at Georgia Tech, stayed to teach there, and began teaching project management. One of his students was Jim Snyder. According to PMI's 1994 profile of its founders, Snyder arranged for Davis to present a workshop in Philadelphia, and when it was time to hold a meeting, Davis's location at Georgia Tech was the obvious venue.

Wideman's article describes the official announcement of PMI's founding on 9 October 1969, during a two-day seminar in Atlanta. Shortly afterward, articles of incorporation were filed in Pennsylvania, signed by five people PMI recognizes as its founders: James Snyder, Eric Jenett, Gordon Davis, Ned Engman and Susan Gallagher. They were practitioners, not full-time institution builders. Snyder and Gallagher worked at Smith, Kline and French, Jenett worked at Brown and Root, and Engman sold project management software. For years, PMI's headquarters was the kitchen table in the Snyder home. Snyder held membership number 2, Jenett number 3 and Davis number 4.

The name nearly came out differently. PMI's history page says the organization was almost called The American Planning and Scheduling Society, until the founders realized the subject was bigger than scheduling. That choice mattered. A society for schedulers would have stayed a society for a technique, and a society for project management could claim the whole job. The same page records the first Seminars and Symposium, titled "Advanced Project Management Concepts," in Atlanta, the first chapter in Houston and a second symposium in Toronto.

Davis supplied the idea that gave the group its argument. He described project management as the "accidental profession", and wanted PMI to be a forum for emerging concepts in a field that wasn't yet seen as a profession. Stretton lists Davis's paper "The Accidental Profession" among three 1970s papers that treated project managers as new professionals, alongside work by David Cleland and Desmond Cook on certification.

The decade ended with a question. Patrick Weaver, a scheduling historian, reports that PMI's 1976 Montreal seminar discussed whether project practices could be documented and whether project management was a profession. A society now had members and chapters but no agreed answer to what a member should know.

What this means for teams today: communities form before standards do. If you want a shared method, begin with a regular place to compare notes, as the first PMI members did, and write the standard once the notes pile up.

The Paper Years (1981-1996)

A committee writes down what a project manager must know

The work began as an entry in PMI's own project list. The June 1981 issue of Project Management Quarterly carried a first report on Project No. 31, Project Management Standards, whose aim was to develop standards, ethics and accreditation. Francis Webster's 1994 history in PMI's magazine says it was instigated at the suggestion of Matthew Parry of the Toronto chapter, and that it might have seemed a routine team assignment. Two years later the team published its report in the August 1983 special issue of Project Management Quarterly.

The report is the root of everything that followed. It proposed a code of ethics and a set of topic areas for the field's unique body of knowledge. Webster lists the six areas: human resources, cost, time, communication, scope and quality management. Twenty-six people contributed, and seven motions went to the PMI Board. Stretton notes that the report added four functions to the traditional time and cost functions, and that the PMI Board approved a certification program in October 1983. The first certification exam took place in Philadelphia on 6 October 1984, which is where the Project Management Professional credential begins, and that credential has a story of its own.

Then the body of knowledge itself went through drafts. Under R. Max Wideman, a team of more than 50 contributors produced the first PMBOK, published in the August 1986 special issue of the Project Management Journal. Members discussed it at PMI's 1986 meeting and sent written comments until 1 December 1986. The Board approved the revised draft on 28 March 1987, effective 1 September 1987, and Webster says it became the basis for the certification program. Contract and procurement management had been added in 1986, and risk management before approval. That makes eight areas, which Stretton traces from the 1983 six to eight "functions" by August 1987. By the end of 1989, PMI had 6,199 members and had given 264 PMP certifications.

The first-edition date is a matter of what you count. The 1987 document was a compilation, Wideman's framework volume appeared in 1991, and the PMBOK Guide in 1996. Muhamed Abdomerovic, writing in the PM World Journal, notes that PMI counts the 1996 guide as its first edition while the field's first compilation dates to 1987 and its publication to 1991. This article follows PMI's numbering for editions and gives the earlier dates where they matter.

The second thing that changed was the form. William Duncan, PMI's Director of Standards, led the 1996 guide, which Abdomerovic describes as the first process-based edition, adding for each function its processes with inputs, outputs, tools and techniques. Weaver credits the 1991-1996 review under Duncan with adding the Integration area. A list of topics had become a method for describing a project.

What this means for teams today: a list of subjects tells people what to learn, and a list of processes tells them how the pieces connect. If your own playbook is only a checklist of topics, ask what goes in and what comes out of each step.

The ANSI Standard (1996-2012)

A guide becomes a formal American standard

By 1996 the guide existed, but it was still PMI's own document. Turning it into a recognized standard took a two-step project that Jay Holtzman described in PMI's magazine in December 1999. ANSI, the American National Standards Institute, accepted PMI as an accredited standards developer in October 1998, and in September 1999 approved the PMBOK Guide as an American National Standard.

The people who drove it ran it like a project. Judith Doll and Cynthia Berg of the PMI Standards Member Advisory Group told Holtzman that they drew up a charter and scope statement and set timelines, costs and benefits. Berg said the toughest part was formalizing PMI's own way of writing standards, which had been loose before, as Holtzman's article reports. He adds that a 1998 report for PMI found standards play a role in how professions such as law, medicine and architecture earn recognition, and that ANSI approval was part of an effort stretching back at least 15 years to the first attempts to describe the body of knowledge. The pattern is notable: a body whose guide described how to run projects had to run a project to get that guide recognized.

The editions that followed came on a steady cycle. Abdomerovic lists the 2000 edition, led by standards manager Steven Fahrenkrog and project leader Cynthia Berg; the 2004 edition, which introduced data flow diagrams to show how processes connect; and the 2008 edition, which advanced them. Weaver describes roughly four-yearly revisions from 2000 onward. This was the high point of the process era. PMI's own history page puts the first Global Project Management Forum, with attendees from 23 countries, in the same decade as the first edition, and the 50,000th PMP in 2002.

Europe took a different route to the same place. IPMA, renamed at its 13th World Congress in Paris in 1996, began certifying individuals in 1998 and published ICB version 1.0. The two bodies pursued credentials and written standards on separate tracks. For another structured approach from the same period, see PRINCE2, and for the single-document view of how these approaches differ, see the evolution of project management methodologies.

What this means for teams today: a standard's authority comes from how it was made as much as what it says. When you adopt one, ask who reviewed it, how objections were handled and how often it is revised.

The Agile Pressure (2013-2020)

Iterative teams push a process guide to bend

The fifth edition, dated 2013 in Abdomerovic's list, carried one visible addition. Weaver reports that this update added Stakeholder Management as a knowledge area. The more important pressure came from outside. PMI's history page lists the PMI Agile Certified Practitioner credential and the fifth and sixth editions of the guide among developments of the 2009-2019 decade.

The sixth edition of 2017, according to Abdomerovic, offers more discussion on agile adoption, closer alignment with ISO 21500 and with other PMI standards. That is a guide organized around planned processes adding notes for teams that plan in short cycles. The new problem was structural. A book built on inputs, outputs and a defined order of work sits awkwardly beside teams that deliver in increments. Our pages on the agile methodology and the waterfall approach show the two sides, and the history of hybrid project management shows what happened when teams combined them.

What this means for teams today: a standard that adds an appendix for a new way of working is a signal, not a fix. If you're bolting agile onto a process-heavy method, look for where the underlying assumptions clash.

The Principles Turn (2021-present)

The guide drops its process spine and returns to it in a lighter form

In 2021, PMI published The Standard for Project Management together with the Seventh Edition of the guide, and the guide dropped its process-based structure. Martin Smit, summarizing PMI's own statements in the PM World Journal, reports that PMI said the process-based orientation of past editions could not be maintained in a way that reflected the full value delivery landscape, so the standard moved to principles. Eight performance domains replaced the knowledge areas, guided by 12 principles. The edition added a dedicated section on tailoring and a section on models, methods and artifacts, and it moved the detailed "how to" into a digital platform, PMIstandards+.

Reaction split. Smit asked whether practitioners would absorb principles, and noted that the seventh edition no longer carries detailed inputs, outputs and techniques. Abdomerovic argued that because the edition does not say how to do the work, the long-standing process approach may be left in limbo. These are commentators' opinions, not findings, but they show what the change cost.

PMI answered four years later. According to PMI's own page for the standard, the Eighth Edition arrived in November 2025 at 408 pages. It keeps the principles-and-domains foundation but simplifies it to six core principles and seven performance domains: governance, scope, schedule, finance, stakeholders, resources and risk. It also reintroduces process guidance "in an evolved, non-prescriptive way" and adds coverage of AI, PMOs and procurement. PMI says the edition draws on input from thousands of professionals and more than 48,000 data points.

So the guide has gone from a topic list to a process library to principles and back toward lighter process guidance. A quick tour of what each edition keeps: the PMBOK Guide explained covers the structure as it stands now, and the project management timeline places these editions among the other milestones.

What this means for teams today: you need both layers. Principles tell a team what good looks like, and process guidance tells a new project manager what to do on Monday. A team with only one of them will feel the gap.

Key People

Key Facts

• PMI's founders page records the first formal meeting on 9 October 1969 at Georgia Tech, and five signers of the Pennsylvania incorporation papers as the founders.
• The ESA report of August 1983 listed six knowledge areas and 26 contributors.
• The PMI Board approved the first body of knowledge on 28 March 1987, effective 1 September 1987.
• ANSI approved the PMBOK Guide as an American National Standard in September 1999.
• By the end of 1989, PMI had 6,199 members and 264 PMP certifications.
• The Eighth Edition, published November 2025, has six principles and seven performance domains.

The Pattern Behind the History

This is our synthesis, not published research. Five points repeat in the history of PMI and the PMBOK Guide:

• Community comes first. A dinner, a seminar and a chapter existed years before a standard.
• Writing it down makes the profession. The ESA report, the PMBOK and the certification program followed one another within four years.
• A list becomes a method. Six topic areas in 1983 grew into processes with inputs and outputs by 1996.
• Standards need their own process. ANSI approval forced PMI to document how it writes standards.
• Every canon meets work it didn't plan for. Agile delivery pushed a process guide toward principles, then back toward lighter process.

What It Teaches Teams Today

• Write down what your team knows. PMI's body of knowledge started as a committee asking what practitioners had in common. A one-page list of your team's repeated practices is the same act at small scale.
• Show inputs and outputs. The 1996 guide's big step was connecting each step to what feeds it and what it produces. Do the same in your own playbooks.
• Keep principles and procedure together. The seventh edition's critics and the eighth edition's return to process guidance point the same way: people need both the why and the how.
• Review your standards on a cycle. PMI revised its guide roughly every four years. A team playbook untouched for longer than that is probably describing work you no longer do.
• Know your lineage. Methods such as PERT and the work breakdown structure feed the guide. Knowing where a practice came from helps you decide when to drop it.