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 |  Agile NoEstimates |  Architecture C4 Model |
|---|---|---|---|
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 estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-3 h | laufend | 1-4 h |
Participantsdifferent | 4-10 | 2-12 | 1-5 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Throughput Data, Flow Forecast, Slicing Rules | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | LeanFlowWasteDelivery | EstimationForecastingFlow | ArchitectureCommunicationVisualization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
