The Agile software development movement is part of Deming's downstream intellectual lineage — a transmission path that runs from his statistical quality work through the toyota-production-system, lean-manufacturing, and lean software development into the practices and values articulated in the Agile Manifesto of 2001. Deming did not influence Agile directly (he died in 1993, eight years before the Manifesto), but his ideas are visible throughout the movement, carried by the lean tradition that connects them.
The transmission path has identifiable links. Deming's juse-lectures-1950 shaped taiichi-ohno's development of TPS. james-womack and Daniel Jones codified TPS as lean manufacturing. mary-poppendieck and Tom Poppendieck translated lean manufacturing principles into software engineering in "Lean Software Development: An Agile Toolkit" (2003), explicitly connecting the emerging Agile movement to the lean tradition and, through it, to Deming. Their seven lean software development principles — eliminate waste, amplify learning, decide as late as possible, deliver as fast as possible, empower the team, build integrity in, see the whole — are recognizably Deming's ideas adapted for software.
The four values of the Agile Manifesto echo Deming's philosophy at multiple points. "Individuals and interactions over processes and tools" resonates with Deming's emphasis on psychology as a component of the system-of-profound-knowledge and his insistence that management must drive out fear (Point 8 of the the-14-points-for-management) so that people can do their best work. "Working software over comprehensive documentation" reflects Deming's pragmatic empiricism — his insistence that theory must be tested against reality, not elaborated in isolation. "Customer collaboration over contract negotiation" aligns with Deming's focus on understanding the customer as part of the system. "Responding to change over following a plan" is the pdsa-cycle-plan-do-study-act in principle: learning from iteration rather than executing a predetermined plan.
Specific Agile methodologies carry particular Deming echoes. Scrum's sprint retrospectives are formalized PDSA cycles applied to the development process itself. Kanban in software development is a direct borrowing from the Toyota/lean tradition, carrying with it the pull-based flow management that Ohno developed from Deming's foundations. Extreme Programming's emphasis on continuous integration, test-driven development, and pair programming operationalizes Deming's insight that quality must be built into the process, not inspected in after the fact — the same principle that distinguishes statistical-process-control-and-variation-theory from end-of-line inspection.
The Agile Manifesto's emphasis on self-organizing teams connects to Deming's critique of management-by-objectives-deming-s-critique and his argument that intrinsic motivation, not extrinsic incentives, drives quality work. Deming's Point 12 — "remove barriers that rob the hourly worker of his right to pride of workmanship" — anticipates the Agile emphasis on team autonomy and the removal of managerial interference from technical decisions. The the-red-bead-experiment demonstrates why micro-managing workers in a system they did not design produces frustration rather than improvement, a lesson that Agile teams rediscover when organizations impose velocity targets or story-point quotas.
There are important differences. The Agile movement developed its own intellectual traditions independent of Deming — the iterative development practices of the 1990s, the object-oriented design community, the open-source movement — and not all Agile practitioners are aware of or interested in the lean lineage. Some Agile implementations have devolved into exactly the kind of ritualized process compliance that Deming criticized in American management: stand-ups without substance, retrospectives without action, "agile transformations" imposed from above without genuine understanding. Deming would recognize this pattern from the TQM movement, which similarly reduced his philosophy to tools and slogans.
For a full account of this transmission path, see deming-s-place-in-the-lean-lineage. The lean-agile synthesis, represented by frameworks like SAFe (Scaled Agile Framework), Lean Software Development, and the DevOps movement, has made the Deming connection more explicit in recent years. The DevOps emphasis on reducing batch sizes, shortening feedback loops, and treating the entire delivery pipeline as a system to be optimized is appreciation-for-a-system applied to software delivery. The connection is real, traceable, and ongoing.