Kanban project management summary and detailed historical timeline by era and year

Kanban is a visual project management framework used to implement lean and agile methodologies, focusing on reducing waste, managing work-in-progress (WIP), and ensuring continuous, high-quality flow. Originating from Japanese manufacturing in the 1940s, it has evolved into a dominant, flexible system for knowledge work, software development, and everyday task management, characterized by “pulling” work only when capacity allows.

Summary of Kanban Project Management

Definition: “Kanban” is Japanese for “signboard” or “visual card”. It is a system for managing work as it moves through a process.
Core Principles: Visualize workflow, limit work-in-progress (WIP), manage flow, make process policies explicit, and improve collaboratively.
Key Components: Kanban Board (visual representation), Kanban Cards (work items), and Columns (workflow stages like To Do, Doing, Done).
Key Benefits: Increased visibility of bottlenecks, improved team focus, flexibility in priorities, and reduced waste (overproduction/excess inventory).
“Pull” System: Work is only started when a downstream team member “pulls” a new card, preventing overburdening.

Detailed Historical Timeline

Era 1: Roots & Conceptualization (1600s – 1930s)

1600s (Edo Period): The term “Kanban” originates, referring to signboards used by Japanese shops to attract customers and distinguish their services, representing the need to communicate content clearly.
1920s: Sakichi Toyoda, founder of Toyoda Automatic Loom Works, invents automatic looms that stop if a thread breaks, establishing the “jidoka” (automation with a human touch) principle.
1930s: Toyota releases its first automobiles, with manufacturing heavily influenced by American assembly line methods.

Era 2: Toyota Production System (1940s – 1990s)

Late 1940s: Taiichi Ohno, an industrial engineer at Toyota, develops the “Just-in-Time” (JIT) production system to minimize waste and inventory costs while increasing manufacturing efficiency.
1953: Toyota applies supermarket-style “pull” logic to its main plant machine shop, using cards to signal demand and replenish materials.
1956: Ohno visits American supermarkets and studies how shelf-stocking relies on customer demand to trigger replenishment.
1963: The Kanban system is officially implemented and adopted across all Toyota factories.
1973–1978: Ohno publishes the principles of the Toyota Production System, popularizing Lean Manufacturing.

Era 3: Transition to Knowledge Work (2000s)

2001: The Agile Manifesto is published, highlighting the need for faster software development, which Kanban later helps achieve.
2003: Mary and Tom Poppendieck publish “Lean Software Development: An Agile Toolkit,” mapping manufacturing principles to IT.
2004: David J. Anderson applies “pull system” principles to Microsoft’s XIT Sustaining Engineering group, creating the “Kanban Method”.
2005: David Anderson implements the first Kanban system for change request management at Corbis.
2007: Anderson introduces Kanban to the Agile community at the Agile 2007 conference. Karl Scotland introduces Kanban to Yahoo!.
2008: The “kanbandev” Yahoo! group is formed, fostering community development of virtual kanban systems.

Era 4: Modernization and Global Adoption (2009 – Present)

2009: Corey Ladas publishes “Scrumban,” exploring the mix of Scrum and Kanban. The first Lean Kanban conference is held in Miami.
2009 (Summer): Jim Benson begins developing Personal Kanban, applying the methodology to personal organization.
2010: Anderson publishes “Kanban: Successful Evolutionary Change for Your Technology Business”, cementing the framework in tech management.
2011: Jim Benson and Tonianne DeMaria Barry publish “Personal Kanban”.
2016: “Essential Kanban Condensed” is published by David Anderson and Andy Carmichael, distilling the method into five core practices.
2020s: Digital Kanban tools become industry standard for remote work, and adoption spreads to non-tech industries like marketing, human resources, and law.

Kanban project management summary and detailed historical timeline by era and year

Waterfall project management is a linear, sequential methodology

Waterfall project management is a linear, sequential methodology where progress flows steadily downward through defined phases, much like a physical waterfall. In this model, each stage—such as requirements, design, implementation, and testing—must be fully completed and approved before the next one begins.

Waterfall Project Plans, .xls and .mpp file formats respectively

Core Characteristics

Sequential Design: No overlapping phases; each “cascades” into the next.
Documentation-Driven: Extensive upfront planning and detailed records are required at every step.
Fixed Scope: Requirements are gathered at the start, making the project’s timeline and budget highly predictable but difficult to change.
Specialised Use: Best suited for regulated industries like aerospace, construction, and healthcare, where changes are costly or safety is paramount.

Historical Timeline by Era and Year

The following timeline tracks Waterfall from its origins in post-WWII engineering to its current role in hybrid project management.

Examples, Waterfall Plan On a Page POaP in MS PowerPoint format

The Pre-Formal Era (1950s – 1969)

Software development adopted structured, sequential approaches from engineering, largely driven by complex, high-risk projects.

1956: Herbert D. Benington documented a sequential process for the SAGE project, establishing the technical roots.
Late 1960s: NASA applied linear, rigid methodologies to Apollo missions, setting a precedent for high-stakes, documentation-heavy development.
1968: The NATO Software Engineering Conference highlighted the “software crisis,” prompting a push for formal, disciplined development models.

The Formalisation Era (1970 – 1979)

The model was officially, yet ironically, described and named.

1970: Dr. Winston W. Royce published his foundational paper on managing large software systems, often cited as the origin of the “Waterfall” model, though he originally presented it as a cautionary, flawed approach.
1976: T.E. Bell and T.A. Thayer likely first used the term “Waterfall” in literature.

The Institutional Era (1980 – 1999)

Waterfall became the mandatory standard for large-scale, complex projects.

1985: The U.S. DoD mandated DOD-STD-2167, cementing Waterfall as the standard for military software.
1989: The UK Government introduced PRINCE2, deeply influenced by Waterfall principles.
1994: The U.S. DoD formally abandoned strict Waterfall mandates for more flexible methods.

The Modern & Hybrid Era (2000 – Present)

Waterfall transitioned from the default standard to a specialised methodology.

2001: The Agile Manifesto marked a shift toward iterative development, reducing Waterfall’s dominance.
Present Day: It remains vital in regulated sectors (e.g., aerospace) and is often combined with Agile in hybrid approaches.

Waterfall project management is a linear, sequential methodology

Click on the link in the website banner above to purchase example, editable template project plans shown and many others.

Project Management Process Summary

Project Management Processes Summary

Waterfall Methodology in Project Management, a Timeline History

The Waterfall methodology is a linear, sequential project management approach where progress flows steadily downward through defined phases, such as requirements, design, implementation, and testing. Each stage must be completed and approved before the next begins, making it highly structured but often inflexible to changes.

Waterfall template available on this website

Historical Timeline by Era and Year

The history of the Waterfall model spans from early post-WWII engineering to its formalisation in software and eventual institutionalisation in government standards.

The Pre-Formal Era (1950s – 1969)

During this period, software development borrowed heavily from established engineering and manufacturing processes.

1956: Herbert D. Benington presents a paper on the Semi-Automatic Ground Environment (SAGE) project, describing a structured process that many consider the true technical origin of the sequential approach.
Late 1960s: Major NASA projects and government software systems for rockets (e.g., Apollo missions) utilise rigid specifications and linear development due to the high cost of changes.
1968: The NATO Software Engineering Conference identifies the “software crisis”—projects consistently running over budget and time—leading to a push for more disciplined models.

The Formalisation Era (1970 – 1979)

The methodology was formally described, ironically as a cautionary tale, and finally given its name.

1970: Dr. Winston W. Royce publishes “Managing the Development of Large Software Systems”. He presents the sequential diagram but explicitly critiques it as “risky and invites failure,” suggesting a more iterative approach instead.
1976: The term “Waterfall” is officially coined in a paper by Bell and Thayer, “Software Requirements: Are They a Problem?”.

The Institutional Era (1980 – 1999)

Waterfall becomes the global standard for large-scale and regulated industries.

1985: The U.S. Department of Defense (DoD) adopts DOD-STD-2167, which mandates the use of the Waterfall model for all software development contractors. This cements Waterfall as the “one true way” for government and aerospace projects.
1989: The UK Government creates PRINCE2, a process-based method largely rooted in Waterfall principles, still widely used in the public sector today.
1991: In response to Waterfall’s rigidity, James Martin introduces Rapid Application Development (RAD), one of the first major departures from the linear model.

The Modern & Hybrid Era (2000 – Present)

As Agile became dominant, Waterfall shifted from the default choice to a specialised or hybrid tool.

2001: The Agile Manifesto is published, marking a significant industry-wide shift away from traditional Waterfall toward iterative development.
2009: Major institutions like George Washington University and others begin documenting their Project Management Lifecycle (PMLC) to standardise Waterfall and hybrid models for better oversight.
2020s: Waterfall persists in regulated domains like healthcare, aerospace, and construction. It is increasingly integrated into hybrid methodologies that use Waterfall for high-level planning and Agile for execution.

Waterfall Methodology in Project Management, a Timeline History

Project Management LinkedIn Group

https://www.linkedin.com/groups/163300

Project Management Café, PRINCE2 Agile SCRUM Kanban MPP MSP Templates ITIL LEAN DevOps PMP Six Sigma

This is a Project Management Group Café for PM students, graduates and professionals looking to either locate, discuss or contribute ideas for PM templates for; Agile, Scrum, Kanban, PRINCE2 Waterfall projects, e.g. Plan on a Page (POaP), RACI, MPP, RAID logs, finance trackers, status reports, org charts etc. etc.

Project Management LinkedIn Group

PRINCE2 and Agile Project Management Templates Gallery

A gallery and inventory of screenshots for the Project Management Templates (both Agile and PRINCE2 waterfall projects) that are all available to be purchased as a bundle from this website link (note: upgrades to the latest template package after purchase, are totally FREE).

Agile PRINCE2 Project Management Templates Gallery

PRINCE2 & Agile PM Templates Gallery

PM templates include MS Project MPP and MS Excel detailed plans including PRINCE2 and Agile delivery, Gantt Plan on a Page examples (POaP), finance trackers, status reports, RAID logs (Risk, Issue, Assumption, Dependency log), RACI tracker (Responsible, Accountable, Consulted, Informed), agile burn down chart and burn up chart, resource tracker, benefits realization plan etc. etc.

(Download the Template Inventory PDF file – 15MB)

Join the FREE PM templates related Facebook Group (LIKE Facebook page) and LinkedIn Group.

PRINCE2 and Agile Project Management Templates Gallery examples