Skip to content

History of project management

Project management grew from practical ways of organizing complex work into a distinct management approach during the twentieth century. Its history is not a single invention story: work-study methods, visual schedules, network analysis, and new forms of team coordination developed in different settings and gradually came together.1

At the turn of the twentieth century, Frederick Winslow Taylor argued that work should be studied systematically rather than managed only through custom and informal judgment. His 1911 book set out the principles of what became known as scientific management. In the same period, Henry Gantt developed visual methods for planning and tracking production. Gantt’s 1919 book documents this work, while later scholarship cautions that the familiar modern Gantt chart is the result of a longer evolution—not simply a finished format invented at one moment.2

These approaches made work and time easier to discuss by putting activities into a visual plan that managers could inspect and revise.

In the 1950s, network methods offered another way to reason about interdependent activities. The Critical Path Method (CPM) emerged from a DuPont and Remington Rand collaboration beginning in 1956, with its developers publishing a foundational scheduling paper in 1959. Around the same period, the U.S. Navy developed PERT in connection with the Polaris program. PERT used networks and multiple time estimates to help assess uncertain durations and the likelihood of meeting program dates.3

CPM and PERT had different development settings and emphases, but their histories overlap in people and ideas. Their significance was broader than a new way to draw a schedule: network analysis helped managers reason about how delays in connected work could affect a larger undertaking.

Project management becomes an organizational approach

Section titled “Project management becomes an organizational approach”

As aerospace, defense, and computing programs grew in scale and complexity, organizations needed more than a schedule: they had to coordinate specialized teams, control work over time, and monitor resources across connected efforts. By the early 1960s, project literature was giving increasing attention to project teams and resource coordination alongside planning and schedule control. This helped establish project management as an organizational model, not just a collection of charting techniques.4

The history continues to evolve, but this transition is a useful dividing line: early methods helped make work visible; mid-century methods connected activities and uncertainty; project management brought those tools into a broader system for coordinating people and work.

There is no single answer to “what was the first project-management software?” The earliest documented successful use of a computer to schedule a project was a 1959 PERT application for the U.S. Navy’s Polaris program. That was computer-aided scheduling, not a packaged desktop app. If the question means a dedicated project-management system, Metier’s Apollo is an early candidate: its programmer James Miller recalls starting development and making first deliveries in 1975. The Centre for Computing History dates Apollo’s launch to 1977 and the Artemis Project Management System to 1978; Miller says the Apollo name later changed to Artemis in the United States. These dates describe different milestones, so Apollo/Artemis is best called one of the earliest dedicated systems rather than an uncontested first.5

Project tools then moved from mainframes and specialist computer systems onto personal computers, making schedule calculations and project data more accessible to individual managers. Networking, client/server and browser-based services brought shared information and collaboration back into focus; cloud-based tools now support teams working across locations. Modern solutions range from detailed schedule and resource planning to shared task and portfolio coordination, with AI features increasingly assisting analysis and drafting. Research still treats AI in project management as a developing field and as support for human decisions, rather than a substitute for project responsibility; see AI-Assisted Project Planning: Capabilities and Limits.6

Today’s project-management software includes desktop scheduling tools such as Microsoft Project, Project Plan 365, and ProjectLibre, alongside many other solutions. For an overview of Microsoft Project’s role and main concepts, see What Is Microsoft Project?.

  1. A history of project management models: from pre-models to the standard models
  2. The Principles of Scientific Management; Organizing for Work; Gantt Charts: A Centenary Appreciation
  3. The Origins of CPM: A Personal History; Critical-Path Planning and Scheduling; PERT, CPM and the Tangled History of Network Scheduling
  4. They Wrote the Book: The Early Literature of Modern Project Management; A History of Project Management Models
  5. Early computer scheduling and PERT; Metier and Artemis: a cofounder’s account; Project software in industry by 1990; Metier Artemis historical record
  6. The shift from mainframes to PCs and networked project systems; Project management software on personal computers; Cloud-based project-management software adoption; AI’s developing role in project management