View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Bottleneck Analysis | ![]() Delivery Value Stream Mapping | ![]() Agile Story Points | ![]() Delivery Monte Carlo Forecasting |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-3 h | 1-3 h | laufend, 1-5 min je Item | 30-90 min Setup, danach laufend |
Participantsdifferent | 3-8 | 4-10 | 3-9 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Current-state map, Future-state map, Bottleneck list | Point Estimates, Reference Stories, Velocity Data | Forecast Percentiles, Throughput Dataset, Risk Communication |
Tagsno overlap | FlowMeasurementConstraints | LeanFlowWasteDelivery | EstimationAgileMeasurement | ForecastingFlowDelivery |



