View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Value Stream Mapping |  Domain Modeling Context Map |  Delivery Cost of Delay |  Agile WSJF |
|---|---|---|---|---|
Purposedifferent | 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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. | When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. |
Complexitydifferent | Medium | Medium | High | High |
Timedifferent | 1-3 h | 1-3 h | 90-180 min | 45-90 min |
Participantsdifferent | 4-10 | 2-8 | 3-8 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Context Map, Integration Patterns, Boundary Notes | CoD Table, Prioritization Sequence | Ranked Backlog, Cost-of-Delay Assumptions |
Tagsno overlap | LeanFlowWasteDelivery | Domain-Driven DesignBoundariesStrategy | PrioritizationDeliveryEconomicsDecision | LeanEconomicsSequencePrioritization |