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 |  Operations Bottleneck Analysis |  Engineering Kanban |  Agile NoEstimates |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | laufend, 1-5 min je Item | 1-3 h | Ongoing | laufend |
Participantsdifferent | 3-9 | 3-8 | 2-12 | 2-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Kanban board, WIP policies, Flow metrics | Throughput Data, Flow Forecast, Slicing Rules |
Tagsno overlap | EstimationAgileMeasurement | FlowMeasurementConstraints | FlowVisual managementDelivery | EstimationForecastingFlow |