Who Invented Project Management? The People Behind the Discipline

By Victor Hoang · Updated Oct 21, 2026

Picture a boat on the Nile around 2600 BCE. An inspector named Merer is writing down where his crew slept each night. They are hauling limestone from the Tura quarries to the Great Pyramid. He has no word for what he is doing.

Nobody invented project management. People have run big, one-time jobs for roughly 4,500 years. A handful of engineers built the first project-specific scheduling methods between 1956 and 1959. The profession itself took shape when a small group founded the Project Management Institute in 1969. Which name you give depends on what you mean: the practice, the chart, the management process, the network math or the profession.

Merer's crew was forty men by one reading of his papyri and about 200 by another. Nobody else had a word for what he was doing for the next forty-five centuries. This article follows the strongest candidates through their decisions, says plainly what each one added, and ends with our verdict. For the full map of the field, see the history of project management, and for every dated milestone see the project management timeline.

Timeline at a Glance

This table follows the people and what each contributed. The complete chronology lives in the project management timeline.

The Overseers' Logs (c. 2600 BCE-100 CE)

Ink records the work, long before anyone names the job

Picture Merer's boat, called The Uraeus of Khufu Is Its Prow, loaded with white limestone and tied up for the night. According to the London Review of Books' account of the papyri found at Wadi el-Jarf, Merer was a mid-level inspector who oversaw a team of forty men hauling stone for Giza. For at least four months of the 26th year of Khufu's reign he recorded where the crew worked, where it sailed and where it spent the night. An earlier 2014 journal article by Pierre Tallet and Gregory Marouard, as reported by Live Science, described Merer as in charge of about 200 men and placed the log in Khufu's 27th year, so the crew size depends on which reading you follow. The reviewer compares his text to a timesheet or a ship's log. The same account describes his boss, a scribe named Dedi, who supervised four such teams and recorded "rewards" of fabric given to workers, and a senior relative of the king, Ankh-haf, who held the title director of Ro-She Khufu. The round trip from quarry to pyramid was about forty kilometres.

Fast-forward to Rome. In 97 CE Sextus Julius Frontinus was appointed water commissioner, an office the Loeb edition's introduction describes as long neglected and mismanaged, with abuses and corruption of long standing. In his own report, De Aquis, he says that Emperor Nerva gave him the post and that the first and greatest task was to learn the business he had taken on. He had plans drawn of the aqueducts showing valleys, river crossings and the stretches that needed constant upkeep, so he could "have the works before one's eyes." He also told readers to compare all this with the "idle Pyramids".

These two are precursors, not inventors of the discipline. The pyramid builders and the Roman commissioner managed large, complicated work and left written records of it, but nobody called it project management, and what survives of Merer is a record of work done, not a forward plan. What they show is that the underlying problem, coordinating many people and materials toward one result, is as old as large buildings.

For teams today: the oldest project tool is the daily log. If you cannot say where your people were and what they finished yesterday, you are working less carefully than a Fourth Dynasty inspector.

The Factory Chartists (1896-1923)

Two engineers put plans and progress on one sheet of paper

The next scene is a machine shop around 1910. On Henry Gantt's chart, a heavy black line marks the period when a batch of parts should be made, and each evening a clerk fills in the actual quantity and the running total. Historian Patrick Weaver, in his study of Gantt's work, stresses how different this is from the forward-looking bar chart in modern software: Gantt's charts tended to be retrospective and diagnostic, a way to see the gap between what was promised and what was done.

Gantt (1861-1919) was an American mechanical engineer who worked in Frederick Taylor's circle. Per Weaver, he described a version of his charts in a paper printed with Taylor's Shop Management in the 1903 ASME Transactions, saying they dated from 1890 onward, and he collected the ideas in Work, Wages and Profits in 1916. In 1917 the Chief of Ordnance retained him to advise on wartime production, first at the Frankford Arsenal and then in Washington. The phrase "Gantt Chart" first appears in Wallace Clark's 1923 book, not in Gantt's own writing, because Gantt named his charts for their purpose.

Karol Adamiecki (1866-1933), a Polish engineer, has the older claim to a project-shaped chart. Weaver reports that Adamiecki developed the harmonogram in 1896. The harmonogram used paper strips, one per activity, with each activity's predecessors written above it, which makes it a distinct forerunner of the network methods that arrived roughly sixty years later. A PMI-published article agrees on 1896 but says Adamiecki first described the method and its results publicly in 1903, before the Society of Russian Engineers in Ekaterinoslaw, and quotes his own account from a 1931 Polish article. So the dates differ by what you count: development in 1896, public presentation in 1903, his full explanation in print in 1931.

Weaver argues two things that cut against the popular story. Bar charts predate Gantt by well over a century, and Gantt's own work was about factory throughput, not one-off projects. Both men matter, but neither was trying to found the discipline we now teach. If you want to use the charts in their modern form, read what a Gantt chart is. Weaver also observes that the plan-versus-actual information on Gantt's charts resembles what earned value management later formalized.

For teams today: show planned and actual side by side. A schedule that never records what really happened teaches the team nothing.

Fayol's Five Functions (1916-1949)

A French mining director turns managing into a repeatable job

In July 1916 the Bulletin of the Société de l'Industrie Minérale carried a long paper by a mining engineer two years from retirement. Henri Fayol (1841-1925) had been appointed director-general of the Comambault mining company in 1888, when the firm was close to bankruptcy, and by the time he retired in 1918 it was among the largest industrial combines in Europe. His paper, Administration industrielle et générale, split a company's work into six kinds of activity and singled out managerial activity as the thread running through the other five. He broke that managerial work into five elements: forecasting and planning, organizing, commanding, coordinating and controlling.

The paper became a book in France in 1925, and an English translation appeared in 1929. It reached wide American attention after a 1949 edition under the title General and Industrial Management. By the 1950s, as the same EBSCO account notes, management textbooks were organized around his functions. For a fuller portrait, see the father of modern management debate and the management theory timeline.

Fayol wrote about running an enterprise, not a project. His contribution to project management is indirect but real: he gave later teams the verbs, plan, organize, coordinate and control, that they would use to describe a project's life. He deserves credit for the management process, and little credit for the schedule.

For teams today: a project fails as often from skipped coordination as from a bad plan. Ask which of Fayol's five functions nobody on your team actually owns.

The Network Race (1954-1959)

A chemical company and a Navy office solve the same problem at once

In late 1956, a group at DuPont called the Integrated Engineering Control Group began to survey whether electronic computers could help manage engineering projects. According to the Kelley and Walker paper, Remington Rand UNIVAC assigned James Kelley to help as part of its customer service, and Morgan Walker represented DuPont. Their first decision mattered most: they separated planning, which states which activities must occur and in what order, from scheduling, which adds time. By May 1957 they felt the method would work, and Remington Rand and DuPont began a cooperative effort using a UNIVAC I in Newark, Delaware. A demonstration followed in September 1957.

The pilot results are specific. A test on a plant shutdown at DuPont's Louisville Works, completed by March 1959, cut the average shutdown from 125 hours to 93 hours, and the authors expected 78 hours with better expediting. They add that this single application paid for the whole development five times over.

Then a parallel effort. The same paper notes that in early 1958 the Special Projects Office of the Navy's Bureau of Ordnance, which was coordinating about 3,000 contractors and agencies on the Polaris missile program, set up a team of operations researchers from Booz, Allen & Hamilton, Lockheed Missile Systems Division and the Special Projects Office. Their system asked people for optimistic, most likely and pessimistic durations for each job. The team's own paper, by Malcolm, Roseboom, Clark and Fazar in Operations Research, was published in October 1959 with three authors at Booz Allen and Fazar at the Navy, and it calls the effort Project PERT, short for Program Evaluation Research Task. Kelley and Walker's paper, written the same year, expands the letters as Program Evaluation and Review Technique.

A different Air Force story runs underneath. In 1954 Bernard Schriever took command of the Western Development Division, which oversaw the Thor, Atlas, Titan and Minuteman missiles, and he is credited with introducing "concurrency": step-by-step design, production, testing, facilities preparation and training became a simultaneous process. That is a way of organizing a whole program, not a scheduling technique, but it belongs in any honest list of project-management pioneers.

The PERT legend deserves care. A history of Booz Allen on the INFORMS site says the Polaris program finished eighteen months early while using PERT. Political scientist Harvey Sapolsky's study concluded that PERT was as much a device to protect the program from outside interference as an effective management tool. Both can be true, and credit for the result is genuinely contested. For the techniques themselves, read about the critical path method and the PERT chart.

For teams today: list your dependencies before you schedule them, the way Kelley and Walker split planning from scheduling. And when a method gets credit for a win, ask what else was true that year.

The Founding Dinner (1967-1987)

A sales rep, an engineer and a professor start a profession

The people who turned the practice into a profession did not start with an inventor's story. PMI's own history gives two overlapping accounts. In one, three people had dinner at The Three Threes restaurant, a few blocks from Philadelphia City Hall, and continued a conversation that Jim Snyder and Gordon Davis had been having for months about the lack of places for project managers to compare notes. In the other, founder Eric Jenett recalls that E.A. "Ned" Engman, then a CPM marketing representative for McDonnell Automation, mailed an invitation on January 29, 1968 to Snyder, Davis, Jenett and two others, and a meeting followed at the Roosevelt Hotel in New Orleans on February 15 and 16, 1968, where the group proposed the name American Project Management Institute for a planned organization.

PMI's 1994 profile says articles of incorporation were filed in Pennsylvania and signed by five people it recognizes as the founders: Snyder, Jenett, Davis, Engman and Susan Gallagher. Jenett's recollection counts six original founders in 1968 and explains that Pennsylvania's residency rule for signers brought two names onto the May 1969 papers. Accounts differ on the exact roster, but not on the shape: a few practitioners, a mailing list, and a dinner. The first public gathering was held at Georgia Tech in Atlanta, and on October 9, 1969, Snyder announced the Institute to about 80 people at a dinner at the American Hotel. Twenty-six joined that night for $15 each. Snyder held member number 2, Jenett number 3 and PMP number 1, and for years PMI's headquarters was the kitchen table in the Snyder home.

Two details help explain why this counts. Engman was selling CPM software to potential users, so the Institute began partly as a community around the methods in the last section. And Davis described the goal as a forum for emerging practice for a field not seen as a profession, later calling it the "accidental profession." Jenett recalls that in 1955-1965 the title "project manager" was not widely used in industry, with project engineer, project coordinator and construction manager more common. The modern name and the modern profession therefore arrived together, in the late 1960s.

By 1994 the Institute listed more than 9,700 members, 56 certification applications had arrived in 1984, and a body of knowledge was approved in 1987. For what that standard became, read the PMBOK Guide; for the full dated sequence see the project management timeline.

For teams today: a profession is a shared vocabulary plus a way to check each other's work. If your project managers cannot compare notes with anyone, start a community of practice.

The Contested Crown (1959-present)

Each claimant owns a different half of the discipline

Since 1959 the argument has run on. Different definitions of project management produce different winners, and the table sets them side by side.

Our verdict, offered as our own synthesis and not a settled fact: no individual earns the title "inventor." If you must name the people behind the discipline's technical core, Kelley and Walker, and the Navy team with Booz Allen, built the first methods designed for projects as projects. If you want the person behind the profession, it is Jim Snyder, with Gordon Davis and Eric Jenett beside him. Gantt and Adamiecki laid the visual groundwork, and Fayol supplied the management verbs. The ancient overseers prove the problem is older than any method. The rest of the story, from waterfall to Scrum, belongs to the evolution of project management methodologies.

For teams today: when someone credits one method or one founder, ask which definition they use. The same question will settle most arguments in your own company about who created your process.

Key People

Key Facts

• Merer's papyri describe a team of forty men hauling limestone for Khufu's pyramid in the 26th year of Khufu's reign, though Tallet and Marouard's 2014 reading put the crew at about 200 men in the 27th year.
• Gantt's own charts were retrospective and diagnostic, and the name "Gantt Chart" first appears in Wallace Clark's 1923 book.
• A DuPont test in Louisville cut average shutdown time from 125 hours to 93 hours using critical path scheduling.
• The Atlanta dinner meeting where PMI was announced, on October 9, 1969, drew about 80 people, and 26 joined that night.
• Fayol's 1916 paper named five managerial functions: forecasting and planning, organizing, commanding, coordinating and controlling.

The Pattern Behind the History

Our synthesis, not published research: the "inventor" of project management keeps changing because the discipline was built in four layers, each by different people.

• Practice first, name later. Overseers managed pyramids and aqueducts for millennia before the job had a title.
• Visibility before math. Gantt and Adamiecki made work visible long before Kelley, Walker and the Navy team computed what it depended on.
• Methods are born inside organizations. CPM grew inside DuPont and PERT inside a Navy program, not in a classroom.
• A profession needs a community. The methods existed for more than a decade before a dinner turned users into an institute.

What It Teaches Teams Today

• Keep a daily record. Merer's log is the oldest ancestor of your status report. Write what happened, not only what is planned.
• Show plan against actual. Gantt's real insight was the gap between promise and performance.
• Map dependencies before dates. Kelley and Walker's habit of separating planning from scheduling still prevents a lot of rework.
• Be careful with origin stories. The PERT legend and the Gantt legend both outran the documents. Ask what a method did in the setting it came from.
• Build the community. PMI began as a few people comparing notes. A shared vocabulary and a way to learn from peers are still part of the job.

To see how the field developed after these founders, return to the history of project management.