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 Process Mapping |  Agile Example Mapping |  Agile Specification by Example |  Operations Theory of Constraints |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 1-3 h | 30-60 min | 60-90 min pro Feature | 2-4 h Analyse, laufend |
Participantsdifferent | 3-10 | 3-7 | 3-6 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Example Map, Acceptance Criteria, Open Questions | Example Table, Acceptance Tests | Constraint Map, Improvement Plan, Flow Metrics |
Tagsno overlap | ProcessOperationsImprovement | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development | OperationsConstraintsFlowImprovement |