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 Monte Carlo Forecasting |  Delivery Value Stream Mapping |  Architecture C4 Model |
|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication. | 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. | 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 | High | Medium | Low |
Timedifferent | 30-90 min Setup, danach laufend | 1-3 h | 1-4 h |
Participantsdifferent | 1-8 | 4-10 | 1-5 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Forecast Percentiles, Throughput Dataset, Risk Communication | Current-state map, Future-state map, Bottleneck list | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | ForecastingFlowDelivery | LeanFlowWasteDelivery | ArchitectureCommunicationVisualization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
