View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Waste Analysis |  Delivery Value Stream Mapping |  Agile Specification by Example |  Engineering Kanban |
|---|---|---|---|---|
Purposedifferent | For a process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. | When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 45-120 min | 1-3 h | 60-90 min pro Feature | Ongoing |
Participantsdifferent | 2-8 | 4-10 | 3-6 | 2-12 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Waste Map, Prioritized Waste, Improvement Backlog | Current-state map, Future-state map, Bottleneck list | Example Table, Acceptance Tests | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | WasteLeanProcess improvement | LeanFlowWasteDelivery | AgileRequirementsExamplesBehavior-Driven Development | FlowVisual managementDelivery |