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 |  Engineering Kanban |  Architecture arc42 |  Delivery Value Stream Mapping |
|---|---|---|---|---|
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 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. |
Complexitydifferent | High | Medium | Low | Medium |
Timedifferent | 45-90 min | Ongoing | 1-2 Tage | 1-3 h |
Participantsdifferent | 3-10 | 2-12 | 1-4 | 4-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Ranked Backlog, Cost-of-Delay Assumptions | Kanban board, WIP policies, Flow metrics | Architecture Document, Context View, Runtime View, Deployment View | Current-state map, Future-state map, Bottleneck list |
Tagsno overlap | LeanEconomicsSequencePrioritization | FlowVisual managementDelivery | ArchitectureDocumentationCommunication | LeanFlowWasteDelivery |