Lean-Agile SoftwareBetter flow for software and knowledge work

Lean vs agile

Lean comes from manufacturing and focuses on flow and removing waste across the whole value stream. Agile comes from software and focuses on short iterations, working product and close collaboration with customers.

The two overlap. Kanban is where they meet most directly: a lean pull system used by agile teams. Lean-agile tools take that combination beyond one team to flow metrics and portfolio decisions.

The four flow metrics

The Kanban Guide names four flow metrics as the minimum for a kanban system. They are work in progress, throughput, work item age and cycle time.

Work in progress is the number of items started but not finished. Throughput is how many finish per unit of time. Work item age shows how long open items have been in progress.

Cycle time is the elapsed time from start to finish. Little's Law links average work in progress, throughput and cycle time. The Little's Law calculator shows the effect of cutting work in progress.

Flow efficiency

Flow efficiency is the share of an item's cycle time spent actively working on it. The rest is waiting in queues or for approvals.

Low flow efficiency usually means the delay sits between steps, not inside them. Flow metrics tools and value stream management software help find those queues.

Value stream management and lean portfolio management

Value stream management software measures flow across the whole path from idea to delivery, often across several teams and tools. It is different from drawing a value stream map, although it serves the same purpose.

Lean portfolio management applies lean thinking to funding and strategy. The Scaled Agile Framework describes it as aligning strategy and execution through lean budgets and governance. See lean portfolio management software.

Strategy itself sits one level higher, in strategy deployment software.

Kanban software or a general project tool?

General project tools manage tasks and dates. Kanban software manages flow: WIP limits, explicit policies and the history needed for flow metrics.

If your team mainly needs a shared task list, a general tool may be enough. If you want to limit WIP and forecast delivery from data, check for kanban features. The digital kanban guide lists what to look for.