Agile vs Lean
What is Agile vs Lean?
Agile vs lean compares two overlapping approaches. Agile, from software, centers on short iterations, feedback and adapting to change; lean, from Toyota manufacturing, centers on customer value, removing waste and improving flow.
Updated November 2026 · 3 min read
Agile and lean are related approaches to improving how work gets done, and the difference is mostly one of emphasis. Agile focuses on delivering working results in short iterations, getting feedback and adapting to change. Lean focuses on maximizing customer value by removing waste and improving the flow of work through the whole system. In practice they overlap heavily, and most modern teams use ideas from both.
They have different origins. Lean comes from manufacturing, especially the Toyota Production System developed by Taiichi Ohno and colleagues in the decades after World War II. The word "lean" was popularized by MIT researchers, notably in The Machine That Changed the World (1990), and James Womack and Daniel Jones set out five lean principles in Lean Thinking (1996). Agile comes from software, and its reference point is the Agile Manifesto of 2001. Mary and Tom Poppendieck's Lean Software Development (2003) bridged the two by translating lean ideas into software terms.
Agile vs. lean at a glance
| Aspect | Agile | Lean |
|---|---|---|
| Origin | Software development, 1990s to 2001 | Manufacturing, Toyota, from the mid-20th century |
| Main goal | Deliver value early and adapt to change | Deliver value with the least waste and best flow |
| Unit of focus | The team and its iterations | The end-to-end value stream |
| Rhythm | Fixed iterations, such as two-week sprints | Continuous flow and pull |
| Key practices | Sprints, backlogs, reviews, retrospectives | Value stream mapping, WIP limits, kaizen, root cause analysis |
| Typical measures | Velocity, sprint goal completion, customer feedback | Lead time, cycle time, throughput, waste |
| Common frameworks | Scrum, XP | Kanban, Lean Six Sigma, Lean Startup |
What they share
- Customer value defines what is worth doing.
- Small batches beat large ones, because they reduce risk and speed feedback.
- The people doing the work are best placed to improve it.
- Continuous improvement is part of the job, not a separate project.
Lean principles and wastes
Womack and Jones's five principles are: identify value from the customer's view, map the value stream, create flow, establish pull and pursue perfection. Lean thinking also names categories of waste. In software, the Poppendiecks translated these into examples such as partially done work, extra features, handoffs, task switching, delays and defects. Spotting these is often the quickest way to speed up delivery without adding people. See lean management and value stream mapping.
Choosing between Agile and lean
- Lean ideas fit best where work arrives continuously and unpredictably, such as support, operations or maintenance, or where the problem is the whole system's speed, including approvals and handoffs outside the team.
- Agile frameworks fit best where a team builds a product with uncertain requirements and benefits from a regular planning and review rhythm.
- Combining them is the norm. A Scrum team can use WIP limits and cycle time; a Kanban team can hold regular reviews and retrospectives.
An example
Consider a hypothetical product team that adopted Scrum and now completes most sprint commitments, yet customers still wait an average of 45 days from request to release. A lean look at the whole value stream shows that the team's own work, from sprint start to done, takes about 8 days. The other 37 days are spent waiting: 12 in an intake queue, 10 for a security review and 15, on average, for a monthly release window.
The team was agile, but the system was not lean. Working with security and operations, the organization adds automated security checks to the pipeline, which cuts review waits to 2 days, and moves to weekly releases, which cuts that wait to an average of about 3.5 days. Average lead time falls to about 25.5 days (12 + 8 + 2 + 3.5). Shrinking the intake queue is the next target.
Common pitfalls
- Optimizing the team, not the system. A fast team inside slow approvals still produces slow delivery.
- Treating lean as cost cutting. Lean aims to remove waste to deliver more value, not to remove people.
- Treating agile as speed alone. Agile's main benefit is learning early; speed without feedback misses the point.
- Arguing over labels. The useful question is which practices solve the current problem.
The comparison connects to Kanban vs. Scrum, lean software development and flow metrics, which measure the lean side of delivery.
Frequently asked questions
Can agile and lean be used together?
Yes, and most modern teams do. A Scrum team can add lean practices such as work-in-progress limits and cycle-time tracking, and a Kanban team can hold regular reviews and retrospectives. Both share a focus on customer value, small batches, improvement by the people doing the work and continuous improvement, so the useful question is which practices fix the current problem.
Where did lean thinking come from compared with agile?
Lean comes from manufacturing, especially the Toyota Production System developed by Taiichi Ohno and colleagues after World War II, and was popularized by MIT researchers and by Womack and Jones's Lean Thinking in 1996. Agile comes from software and the 2001 Agile Manifesto. Mary and Tom Poppendieck's Lean Software Development (2003) translated lean ideas into software terms.
What are the wastes in lean software development?
Mary and Tom Poppendieck translated lean's categories of waste into software examples such as partially done work, extra features, handoffs, task switching, delays and defects. Spotting these is often the quickest way to speed up delivery without adding people. For instance, much of a request's lead time may be spent waiting in queues and approvals rather than being worked on.
Related terms
Agile Manifesto
The 2001 founding statement of agile's four values and twelve principles.
Value Stream Mapping
Drawing every step and delay in a process to find where time is lost.
Kanban vs Scrum
Fixed Sprints with set roles versus continuous flow with WIP limits.
Flow Metrics
Measures of how much work flows, how fast and where it gets stuck.