View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Delivery Value Stream Mapping |  Architecture Architecture Decision Record |  Delivery Monte Carlo Forecasting |
|---|---|---|---|---|
Purposedifferent | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | 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 ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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 | Ongoing | 1-3 h | 15-45 min | 30-90 min Setup, danach laufend |
Participantsdifferent | 2-12 | 4-10 | 1-3 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Current-state map, Future-state map, Bottleneck list | ADR File, Decision Log, Rationale | Forecast Percentiles, Throughput Dataset, Risk Communication |
Tagsno overlap | FlowVisual managementDelivery | LeanFlowWasteDelivery | ArchitectureRationaleDocumentationGovernance | ForecastingFlowDelivery |