Project Management

Project management is the practice of planning, coordinating, and controlling a temporary effort—one with a defined goal, a start and an end—to deliver something on time, within budget, and to an agreed standard.

12 frameworks, from 1900 to today · Operations · Business, Management & Finance

still a working view ended · each leads to its entry below

Overview

Project management is the practice of planning, coordinating, and controlling a temporary effort—one with a defined goal, a start and an end—to deliver something on time, within budget, and to an agreed standard1. What makes it a distinct discipline rather than just "getting things done" is the specific problem it keeps returning to: a project is a one-off, so the people doing it cannot simply repeat a proven routine. Every project is, in some measure, an experiment. The field's history is a long search for tools that make a one-off effort predictable—schedules, cost controls, risk estimates—and, more recently, a reckoning with the limits of that ambition.

Building the Pyramids and the Railroads: Projects Before Project Management

Large projects are ancient. The Egyptian pyramids, the Roman aqueducts, the Great Wall of China, and medieval cathedrals were all managed by somebody, using plans, labor forces, and supply chains. What these efforts lacked was an abstract, transferable method: knowledge lived in master builders and guilds and died with them.

The modern discipline begins with the enormous industrial projects of the nineteenth century. Railroad construction, canal building, and later shipbuilding demanded coordination of thousands of workers, materials arriving from distant suppliers, and schedules tied to finance. In the United States, the engineer and manager Henry Gantt developed around 1910–1915 a bar chart that plotted tasks against calendar time, making it possible to see at a glance what was scheduled and what had slipped. The Gantt chart remains one of the most widely used tools in the field2.

Gantt worked in the orbit of Frederick Winslow Taylor, whose scientific management (published most fully in The Principles of Scientific Management, 1911) argued that work should be studied, measured, and broken into standardized tasks. Applied to projects, this meant treating a large undertaking as a set of definable activities that could be planned and controlled rather than left to craft judgment. The same era saw Frank and Lillian Gilbreth use motion study to eliminate wasted effort in tasks—the kind of micro-level analysis that would eventually feed into work-breakdown thinking.

Operations Research and the Scheduling Revolution

The decisive shift came during and after the Second World War. The war mobilized operations research—the application of mathematics to military and industrial problems—and out of that mathematical culture came the network scheduling techniques that still define classical project management.

The Critical Path Method (CPM) was developed around 1957 by Morgan Walker of DuPont and James Kelley of Remington Rand, for planning the construction and maintenance of chemical plants. The idea was to draw a project as a network of activities with dependencies: some tasks must finish before others can start. By tracing the longest chain of dependent tasks through the network—the critical path—you find the sequence that determines the total project duration13. Shortening the project means shortening that path; other tasks have "float" or slack. This was a genuine conceptual advance: it turned a schedule from a wish into a calculable structure.

Independently and almost simultaneously, the U.S. Navy's Special Projects Office developed PERT (Program Evaluation and Review Technique) for the Polaris missile program, first applied around 1958. PERT's contribution was probabilistic: instead of a single duration estimate, each activity got optimistic, most-likely, and pessimistic estimates, combined into an expected duration and a measure of uncertainty. This let planners reason about the probability of finishing by a date rather than just a deterministic schedule. CPM and PERT are often lumped together as "network scheduling," and later tools merged their features; the distinction is that CPM is deterministic and cost-oriented, PERT probabilistic and time-oriented.

Controlling Cost: Earned Value

Schedules tell you whether you are late. They do not tell you whether you are overspending relative to what you have actually accomplished. Earned Value Management (EVM) addressed this14. Developed in U.S. government and defense contracting in the 1960s (the Department of Defense formalized cost/schedule control criteria in 1967), EVM compares three numbers: the budgeted cost of work planned by now, the budgeted cost of work actually performed ("earned value"), and the actual cost incurred. The ratios between them—cost performance and schedule performance indices—give an early warning of trouble. EVM's appeal is that it measures progress against budget rather than against elapsed time, exposing the common failure of a project that looks on schedule because work is being done at rising cost.

Simulating Uncertainty: Monte Carlo

Where PERT approximated uncertainty with three-point estimates, Monte Carlo simulation attacked it more generally5. Practitioners run a project's schedule or cost model thousands of times, each time drawing task durations or costs at random from probability distributions, and observe the spread of outcomes. This yields a distribution of possible completion dates and costs rather than a single number. The method's mathematics is old—named for the casino at Monte Carlo and developed seriously in the 1940s at Los Alamos by Stanislaw Ulam and John von Neumann—and it entered project scheduling as computing power became cheap enough in the later twentieth century. Its lesson: in a project with many uncertain tasks, the expected duration of the whole is often longer than the sum of expected task durations, because delays do not cancel out the way early finishes do.

Codifying the Profession: The PMBOK

Through the mid-twentieth century, project management was a set of techniques used by engineers and defense contractors. The 1960s saw the founding of professional associations—the Project Management Institute (PMI) in 1969 in the United States, and the International Project Management Association in Europe in 1965. PMI's great contribution was standardization: the Project Management Body of Knowledge (PMBOK), first published as a guide in the 1980s and revised repeatedly since, organized the field into knowledge areas (scope, time, cost, quality, risk, procurement, human resources, communications, and so on) and process groups (initiating, planning, executing, monitoring and controlling, closing). The PMBOK gave the profession a shared vocabulary and a body of examinable knowledge, and became the reference for certification. It also, critics later charged, encoded a "predictive" or "waterfall" worldview: plan thoroughly up front, then execute the plan.

The Iterative Turn: Agile, Scrum, and Extreme Programming

By the 1990s, software development exposed the weaknesses of predictive planning. Requirements changed faster than plans could be written; a specification frozen at the start was obsolete by the time the code was delivered. Several responses converged into what became known as agile.

Scrum, developed in the early 1990s by Jeff Sutherland and Ken Schwaber (drawing on earlier work by Hirotaka Takeuchi and Ikujiro Nonaka on "new product development games" in Japanese firms), organized work into short fixed-length sprints of a few weeks, each producing a working increment, with a cross-functional team self-organizing around a prioritized backlog. Extreme Programming (XP), associated with Kent Beck in the late 1990s, pushed engineering practices—pair programming, test-driven development, continuous integration, short release cycles—as the way to keep quality high under change. In 2001 a group of practitioners published the Agile Manifesto, prioritizing individuals and interactions, working software, customer collaboration, and responding to change over their documented counterparts6. Agile was less a single method than a family of iterative, incremental approaches, and it spread well beyond software into product development generally.

Constraints and the Critical Chain

A parallel strand attacked projects through the lens of the theory of constraints, the idea associated with Eliyahu Goldratt (developed in his 1984 book The Goal) that a system's throughput is limited by its bottleneck7. Goldratt applied this to projects in Critical Chain (1997)78. His critical chain method identified the project's constraining sequence of tasks and, crucially, argued that safety buffers hidden inside individual task estimates should be pooled into shared buffers at the end of the chain. It also attacked multitasking and student-syndrome behavior—work expanding to fill available time—that erode schedules. The method remains a recognized alternative to classical network scheduling, especially in environments with severe resource contention.

Hybrids and the Present

The mature field today is not a contest between "waterfall" and "agile" but a practice of hybrid predictive-adaptive governance: using predictive planning and earned value where requirements are stable or regulatory oversight demands it (large construction, defense, regulated industries), and iterative delivery where they are not, often within the same organization. Portfolio and program management, risk registers, Monte Carlo cost estimating, and agile scaling frameworks coexist.

Several questions remain genuinely open. How do you govern agile delivery without reintroducing the heavyweight controls it rejected? How do you estimate and control cost in iterative work where scope is deliberately fluid? How do distributed and increasingly automated teams change coordination? And how much of a project's outcome is determined by method at all, versus by the people and the organizational context around it? The discipline's history suggests that its tools—Gantt charts, critical paths, earned value, sprints, buffers—each solved a real problem and each left new ones, which is why the field keeps generating methods rather than settling on one.

References

  1. Project management (introduction, Types, Critical path method, Earned value management), Wikipedia
  2. Gantt chart (History), Wikipedia
  3. Critical path method, Wikipedia
  4. Earned value management, Wikipedia
  5. Project team builder, Wikipedia
  6. Agile software development (introduction, History), Wikipedia
  7. Theory of constraints (introduction, History), Wikipedia
  8. Critical chain project management (Origins), Wikipedia

The frameworks of Project Management

Each framework is a way of working the field has used: when it held, and the question it answers.

  1. 1900-1930

    Scientific Management

    How can work be measured and standardized for efficiency?

    Fly to its tower in Nousfarer

  2. 1910-Present

    Gantt chart

    How can tasks be shown against calendar time?

    Fly to its tower in Nousfarer

  3. 1957-Present

    Critical path method

    Which sequence of tasks sets the project duration?

    Fly to its tower in Nousfarer

  4. 1958-Present
  5. 1960-Present

    Monte Carlo Project Simulation

    What range of outcomes could a project produce?

    Fly to its tower in Nousfarer

  6. 1967-Present

    Earned Value Management

    Are we overspending for the work actually done?

    Fly to its tower in Nousfarer

  7. 1987-Present

    Project Management Body of Knowledge

    What shared knowledge areas define the profession?

    Fly to its tower in Nousfarer

  8. 1990-Present

    Agile Software Development

    How can teams deliver value under changing requirements?

    Fly to its tower in Nousfarer

  9. 1995-Present

    Scrum

    How can a team self-organize in short increments?

    Fly to its tower in Nousfarer

  10. 1997-Present

    Critical Chain Project Management

    Where should safety buffers be placed in a schedule?

    Fly to its tower in Nousfarer

  11. 1999-Present

    Extreme Programming

    Which engineering practices keep quality high under change?

    Fly to its tower in Nousfarer

  12. 2010-Present

    Hybrid Predictive-Adaptive Governance

    When should planning be predictive and when adaptive?

    Fly to its tower in Nousfarer

How the ideas connect

Each arrow runs from an earlier idea to the later one it shaped. The list below says what passed between them.

Scientific ManagementGantt chartCritical path methodPERT and Probabilistic Network Schedu…Monte Carlo Project SimulationEarned Value ManagementProject Management Body of KnowledgeAgile Software DevelopmentScrumCritical Chain Project ManagementExtreme ProgrammingHybrid Predictive-Adaptive Governance

Beyond the field

Where Project Management's ideas came from in other fields, and what they led to there: the strongest 12 of 39 links.

A city in Nousfarer: a red-carpeted stair climbing terraces to a crowned tower on an acropolis, more towers round it, forest and snowy mountains beyond.
A city in Nousfarer, the game played in the browser.

Project Management is a planet in Nousfarer

Its city has a tower for each of these 12 frameworks. Land, walk in, and climb one concept at a time.

Land on Project Management

Related fields

Fields its ideas are linked to

More in Operations

See where Project Management sits on the Map of Human Knowledge