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 arc42 |  Delivery Communication Plan |
|---|---|---|---|---|
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. | 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. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | 30-90 min Setup, danach laufend | 1-3 h | 1-2 Tage | 45-90 min |
Participantsdifferent | 1-8 | 4-10 | 1-4 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Forecast Percentiles, Throughput Dataset, Risk Communication | Current-state map, Future-state map, Bottleneck list | Architecture Document, Context View, Runtime View, Deployment View | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | ForecastingFlowDelivery | LeanFlowWasteDelivery | ArchitectureDocumentationCommunication | CommunicationStakeholdersDeliveryPlanning |