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 Visual Management |  Agile Story Points |  Engineering Kanban |  Operations Bottleneck Analysis |
|---|---|---|---|---|
Purposedifferent | With high tempo and many parallel topics, the method makes status, deviations, and priorities visible at a glance. It reduces search effort and prevents what matters from getting lost in daily work. | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | Ongoing | laufend, 1-5 min je Item | Ongoing | 1-3 h |
Participantsdifferent | 1-20 | 3-9 | 2-12 | 3-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Visual Board, Status Indicators, Exception Cues | Point Estimates, Reference Stories, Velocity Data | Kanban board, WIP policies, Flow metrics | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures |
Tagsno overlap | SignalsOperationsVisual management | EstimationAgileMeasurement | FlowVisual managementDelivery | FlowMeasurementConstraints |