View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Evaporating Cloud |  Delivery Monte Carlo Forecasting |  Engineering Kanban |  Agile NoEstimates |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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 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 estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 60-120 min | 30-90 min Setup, danach laufend | Ongoing | laufend |
Participantsdifferent | 2-8 | 1-8 | 2-12 | 2-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Forecast Percentiles, Throughput Dataset, Risk Communication | Kanban board, WIP policies, Flow metrics | Throughput Data, Flow Forecast, Slicing Rules |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | ForecastingFlowDelivery | FlowVisual managementDelivery | EstimationForecastingFlow |