"Lean Programming" is mary-poppendieck's earliest published articulation of lean principles applied to software, appearing in Software Development Magazine in May and June 2001 as a two-part article. This predates lean-software-development-agile-toolkit-2003 by two years and represents the first public formulation of what would become Lean Software Development.
Origins
The article emerged from Mary's reflection on why software development at 3m-company felt so different from the lean manufacturing environment she had worked alongside. After retiring from 3M in 1998, she recognized that the engineering-inspired discipline of the factory floor — rooted in taiichi-ohno's Toyota Production System and shaped by w-edwards-deming's quality science — was largely absent from typical IT project management. The Software Development Magazine article was her first attempt to articulate what lean manufacturing could offer to software practitioners.
Content and Significance
The article applied eliminate-waste and other lean manufacturing principles to software contexts. It introduced the core translation argument that would define the Poppendiecks' subsequent work: software development, like manufacturing, generates waste through overproduction, waiting, unnecessary handoffs, and defects — and disciplined attention to eliminating that waste produces better outcomes than adding process overhead.
The two-part format allowed Mary to establish the manufacturing lineage in the first installment and work through software-specific applications in the second. The seven-lean-principles framework that the 2003 book would systematize was here in embryonic form: the waste identification logic, the pull-versus-push argument, and the attention to learning and feedback loops all appear in this early treatment.
Role in the Poppendiecks' Intellectual Development
"Lean Programming" is the bridge between Mary's practitioner knowledge and the Poppendiecks' published framework. Writing the article clarified which manufacturing concepts translated cleanly to software, which required adaptation, and which were specific enough to manufacturing that analogues needed to be constructed rather than borrowed. The article circulated in the early Agile community and contributed to the Poppendiecks' visibility in the years immediately before lean-software-development-agile-toolkit-2003 was published and the agile-manifesto-2001 was signed.
The existence of this 2001 article demonstrates that the lean software development framework was not simply a response to the Agile Manifesto but was developing in parallel from a different intellectual lineage — which is part of why the 2003 book was received as a complement to Agile rather than a derivative of it.