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 |  Architecture arc42 |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | 45-90 min | 1-3 h | 1-2 Tage | 15-45 min |
Participantsdifferent | 3-10 | 4-10 | 1-4 | 1-3 |
Formatdifferent | Workshop | Workshop | Workshop + async | Async |
Outputdifferent | Ranked Backlog, Cost-of-Delay Assumptions | Current-state map, Future-state map, Bottleneck list | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale |
Tagsno overlap | LeanEconomicsSequencePrioritization | LeanFlowWasteDelivery | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance |