View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile T-Shirt Sizing |  Delivery Value Stream Mapping |  Engineering Kanban |
|---|---|---|---|
Purposedifferent | When effort only needs to be classified roughly, it makes comparability more important than false precision. It helps sort work quickly into manageable sizes. | 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 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 |
Timedifferent | 15-45 min | 1-3 h | Ongoing |
Participantsdifferent | 2-12 | 4-10 | 2-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Size Buckets, Rough Backlog Map, Split Candidates | Current-state map, Future-state map, Bottleneck list | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | EstimationAgileRoadmap | LeanFlowWasteDelivery | FlowVisual managementDelivery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
