View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Agile Specification by Example |  Agile NoEstimates |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | 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 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 estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. | 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 | Ongoing | 60-90 min pro Feature | laufend | 30-60 min |
Participantsdifferent | 2-12 | 3-6 | 2-12 | 3-7 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Example Table, Acceptance Tests | Throughput Data, Flow Forecast, Slicing Rules | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | FlowVisual managementDelivery | AgileRequirementsExamplesBehavior-Driven Development | EstimationForecastingFlow | Behavior-Driven DevelopmentRequirementsExamplesRefinement |