In 30 seconds
- Waste is anything the customer wouldn't pay for.
- Lean lists seven classic wastes, often extended to eight.
- Software has its own versions: partial work, extra features, handoffs.
Seven classic wastes
Transport, inventory, motion, waiting, overproduction, over-processing and defects. Many add an eighth: unused talent. Taiichi Ohno described the original seven in the Toyota Production System.
Software equivalents
| Manufacturing | Software |
|---|---|
| Inventory | Partially done work |
| Overproduction | Extra features |
| Transport | Handoffs |
| Motion | Task switching |
| Waiting | Delays for approvals, reviews |
| Over-processing | Relearning, unneeded process |
| Defects | Bugs |
This mapping follows Mary and Tom Poppendieck's lean software development.
Muda, mura, muri
Lean pairs muda with mura (unevenness) and muri (overburden). Levelling work with heijunka reduces all three.
Myth vs reality
Myth · All non-coding work is waste.
Reality · Planning and testing add value when done well.
Myth · Eliminating waste means cutting staff.
Reality · It means freeing people for valuable work.
Myth · Waste is easy to see.
Reality · Much of it hides in queues and handoffs.
FAQ
Which waste is biggest in software?
Often partially done work and waiting.
How do we spot waste?
Value stream mapping and watching where work waits.
Is some waste necessary?
Yes, some supports value, like compliance work; minimize it.