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 |  Decision Making Three-Point Estimation |  Architecture arc42 |  Delivery Monte Carlo Forecasting |
|---|---|---|---|---|
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. | A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption Notes. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 1-3 h | 10-30 min je Item | 1-2 Tage | 30-90 min Setup, danach laufend |
Participantsdifferent | 4-10 | 1-8 | 1-4 | 1-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Three-Point Estimate, Risk Range, Assumption Notes | Architecture Document, Context View, Runtime View, Deployment View | Forecast Percentiles, Throughput Dataset, Risk Communication |
Tagsno overlap | LeanFlowWasteDelivery | EstimationUncertaintyForecasting | ArchitectureDocumentationCommunication | ForecastingFlowDelivery |