The intellectual foundation under continuous delivery, Trunk-Based Development, and modern DevOps practice. Originating in the Toyota Production System and formalized by Donald Reinertsen’s application of queuing theory to product development, the central insight is that batch size is the dominant determinant of cycle time, and fast feedback is the mechanism by which quality improves.
The lineage runs Toyota Production System (1950s) to Lean Manufacturing (Womack and Jones, 1996) to Lean Product Development Flow (Reinertsen, 2009) to Continuous Delivery (Humble and Farley, 2010) to Accelerate / DORA (Forsgren, Humble, and Kim, 2018). Knowing the lineage gives you the theoretical vocabulary to explain why practices like trunk-based development work, not just that they do. The argument is mathematical, not just empirical, which makes it portable across contexts.
Three principles from Reinertsen’s queuing-theoretic frame carry the weight. First, smaller batches flow faster through any pipeline with less variability, generating feedback sooner. Second, large batches create queues, and queues are invisible inventory with carrying costs; in software the queues are open branches, pending merges, staging environments, and triage backlogs. Third, fast feedback reduces uncertainty: the sooner you learn a change is broken, the cheaper it is to fix. That last claim is information-theoretic, not just operational.
The Poppendiecks added vocabulary that travels well into software: waste (anything that doesn’t deliver value), flow (smooth movement of work through a system), pull (downstream demand drives upstream work), and amplify-learning (short feedback cycles). Practices that increase batch size (long-lived feature branches, release trains, staging gates) degrade both speed and quality. Practices that decrease batch size (small batches, feature flags, continuous deployment) improve both. See Frequent Deployments Improve Stability for the empirical follow-on, and DORA Capabilities and Metrics for the measurement framework that makes the argument concrete.