View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Story Points |  Delivery Monte Carlo Forecasting |  Operations Bottleneck Analysis |  Engineering Kanban |
|---|---|---|---|---|
Purposedifferent | When teams want to rate complexity rather than hours, it creates a shared, relative scale. It sorts work by value, risk, and delivery ability. The result is captured as Point Estimates, Reference Stories, and Velocity Data. | 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. | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. | 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. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | laufend, 1-5 min je Item | 30-90 min Setup, danach laufend | 1-3 h | Ongoing |
Participantsdifferent | 3-9 | 1-8 | 3-8 | 2-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | Forecast Percentiles, Throughput Dataset, Risk Communication | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | EstimationAgileMeasurement | ForecastingFlowDelivery | FlowMeasurementConstraints | FlowVisual managementDelivery |