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 Specification by Example |  Operations Process Mapping |  Operations Theory of Constraints |  Operations Bottleneck Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | For a system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput. | 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 | Medium | Medium | High | Medium |
Timedifferent | 60-90 min pro Feature | 1-3 h | 2-4 h Analyse, laufend | 1-3 h |
Participantsdifferent | 3-6 | 3-10 | 3-12 | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Process Map, Handoff List, Improvement Backlog | Constraint Map, Improvement Plan, Flow Metrics | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | ProcessOperationsImprovement | OperationsConstraintsFlowImprovement | FlowMeasurementConstraints |