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 WSJF |  Delivery Value Stream Mapping |  Product Strategy ICE Scoring |  Engineering Kanban |
|---|---|---|---|---|
Purposedifferent | When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | 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 ideas need sorting quickly, it condenses impact, confidence, and effort into one compact score. It connects customer value, product logic, and decision priorities. The result is captured as an ICE table and top-ideas list. | 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 | High | Medium | Low | Medium |
Timedifferent | 45-90 min | 1-3 h | 30-60 min | Ongoing |
Participantsdifferent | 3-10 | 4-10 | 2-8 | 2-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Ranked Backlog, Cost-of-Delay Assumptions | Current-state map, Future-state map, Bottleneck list | ICE Table, Top Idea List | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | LeanEconomicsSequencePrioritization | LeanFlowWasteDelivery | PrioritizationScoringGrowthDecision | FlowVisual managementDelivery |