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 |  Agile Specification by Example |  Agile Story Points |  Agile Example Mapping |
|---|---|---|---|---|
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 business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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 a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | 60-90 min pro Feature | laufend, 1-5 min je Item | 30-60 min |
Participantsdifferent | 3-8 | 3-6 | 3-9 | 3-7 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Example Table, Acceptance Tests | Point Estimates, Reference Stories, Velocity Data | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | FlowMeasurementConstraints | AgileRequirementsExamplesBehavior-Driven Development | EstimationAgileMeasurement | Behavior-Driven DevelopmentRequirementsExamplesRefinement |