Lean software development
Lean software development takes the ideas of Lean manufacturing (the Toyota Production System) and applies them to building software: deliver the most value with the least waste, and improve the whole flow rather than any one part. It’s less a step-by-step framework than a mindset of seven principles, popularized by Mary and Tom Poppendieck in their 2003 book.
Where Scrum gives you roles and events, Lean gives you a lens: look at the end-to-end path from idea to delivered value, find what slows it down or adds no value, and remove it. That lens is where Kanban came from, and it underlies much of “flow-based” agile.
Also known as
Lean · Lean development · (the factory origin) the Toyota Production System applied to software
Don't confuse with
- Lean software development vs Lean Startup. Lean Startup (Eric Ries) is a product/business method: build-measure-learn, validated learning, and a minimum viable product to find what customers want (it’s where the Lean canvas comes from). Lean software development is about the delivery process: applying factory-floor lean thinking to how software gets built. Same “lean” lineage, different target.
- Lean vs Agile. Lean is a set of principles that predates and feeds agile; agile is the broader software movement. In practice Lean is treated as one of the agile methodologies, and it pairs naturally with Kanban.
The seven principles
Lean software development is usually stated as seven principles:
- Eliminate waste: remove anything that doesn’t add value for the customer (see the wastes below).
- Amplify learning: software is a learning process; use short cycles and fast feedback.
- Decide as late as possible: keep options open; commit when you have the most information.
- Deliver as fast as possible: short cycle times expose problems and shorten feedback.
- Empower the team: let the people doing the work make the decisions; respect their expertise.
- Build integrity in: quality is built in continuously, not tested in at the end.
- Optimize the whole: improve the entire value stream, not one team or stage, so local wins don’t create global bottlenecks.
The seven wastes
Lean manufacturing targets muda (waste). The Poppendiecks mapped Toyota’s seven wastes onto software:
| Software waste | What it means |
|---|---|
| Partially done work | Code written but not integrated, tested, or shipped; it ages and hides risk. |
| Extra features | Building what nobody asked for (gold-plating). |
| Relearning | Rediscovering knowledge the team already had. |
| Handoffs | Passing work between people loses context each time. |
| Delays / waiting | Work sitting idle in a queue. |
| Task switching | Splitting attention across many things finishes none of them. |
| Defects | Bugs, and the rework they cause. |
In plain English
Look at the whole path from “idea” to “in the user’s hands,” find every place work sits, gets redone, or gets built that nobody needed, and cut it. Trust the team to do that, and keep quality baked in the whole way.
Where it sits
Lean is a mindset more than a ceremony set, so teams usually combine it with something concrete. Kanban is the most direct descendant (visualize the flow, limit work-in-progress, pull); many “modern agile” teams are really running lean principles through Kanban or Scrum. Core lean vocabulary you’ll meet: the value stream (the end-to-end path work takes), flow, pull, and kaizen (continuous, incremental improvement).
See also
- Kanban: the flow-based method that grew out of Lean/TPS
- Agile software development: the family Lean is counted among
- Lean canvas: from the separate Lean Startup lineage (don’t conflate)
- Software development process: where Lean sits among the approaches
References
- M. Poppendieck & T. Poppendieck, Lean Software Development: An Agile Toolkit, Addison-Wesley (2003). The book that named the discipline and mapped Toyota’s wastes onto software. https://dl.acm.org/doi/10.5555/829556
- Lean Enterprise Institute, “Lean Thinking and Practice.” The lean vocabulary (value, value stream, flow, pull, perfection/kaizen) that Lean software development builds on. https://www.lean.org/lexicon-terms/lean-thinking-and-practice/
- E. Ries, The Lean Startup, Crown Business (2011). Cited only for the disambiguation: this is the separate product/business methodology, not Lean software development. https://www.penguinrandomhouse.com/books/168752/the-lean-startup-by-eric-ries/