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 Waste Analysis |  Agile Specification by Example |  Engineering Kanban |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | For a process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. | 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 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 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 | Low | Medium | Medium | Low |
Timedifferent | 45-120 min | 60-90 min pro Feature | Ongoing | 30-60 min |
Participantsdifferent | 2-8 | 3-6 | 2-12 | 3-7 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Waste Map, Prioritized Waste, Improvement Backlog | Example Table, Acceptance Tests | Kanban board, WIP policies, Flow metrics | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | WasteLeanProcess improvement | AgileRequirementsExamplesBehavior-Driven Development | FlowVisual managementDelivery | Behavior-Driven DevelopmentRequirementsExamplesRefinement |