agile3
Frameworks

Lean Software Development

Lean manufacturing ideas, like eliminating waste and optimizing flow, applied to building software.

2 min read · Practitioner

In 30 seconds

  • Lean focuses on delivering value fast by removing waste.
  • Seven principles, from eliminate waste to see the whole.
  • It shaped Kanban and much of modern DevOps thinking.

Origins

Mary and Tom Poppendieck translated lean manufacturing ideas from the Toyota Production System to software in their 2003 book Lean Software Development.

The seven principles

  1. Eliminate waste
  2. Amplify learning
  3. Decide as late as possible
  4. Deliver as fast as possible
  5. Empower the team
  6. Build integrity in
  7. See the whole

Waste in software

  • Partially done work
  • Extra features nobody uses
  • Handoffs and waiting
  • Task switching
  • Defects

Tools like value stream mapping and WIP limits help find and cut it.

Myth vs reality

Myth · Lean means doing more with fewer people.
Reality · It means removing waste so people can focus on value.
Myth · Lean and agile are rivals.
Reality · They share most values and are often used together.
Myth · Deciding late means procrastinating.
Reality · It means keeping options open until you have real information.

FAQ

How does lean relate to Kanban?

Kanban applies lean flow ideas directly to knowledge work.

What's the biggest waste in most teams?

Usually partially done work and waiting between handoffs.

Is lean only for operations?

No; it applies to product development and management too.