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 Request for Comments |  Decision Making DACI |
|---|---|---|---|---|
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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | 30-90 min Setup, danach laufend | 1-3 h | 1-3 Wochen vom Draft bis zur Entscheidung | 30-60 min |
Participantsdifferent | 1-8 | 4-10 | 3-20 Reviewer | 2-10 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Forecast Percentiles, Throughput Dataset, Risk Communication | Current-state map, Future-state map, Bottleneck list | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | ForecastingFlowDelivery | LeanFlowWasteDelivery | ArchitectureDecisionAsyncGovernance | DecisionRolesGovernanceAlignment |