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 Example Mapping |  Delivery Value Stream Mapping |  Agile Specification by Example |  Product Discovery Dual-Track Agile |
|---|---|---|---|---|
Purposedifferent | 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 delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | 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 uncertainty and delivery run in parallel, it separates learning work from implementation while keeping both connected. It prevents unvalidated ideas from falling directly into the delivery stream. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 30-60 min | 1-3 h | 60-90 min pro Feature | Laufend, Wochen bis Monate |
Participantsdifferent | 3-7 | 4-10 | 3-6 | 4-10 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Current-state map, Future-state map, Bottleneck list | Example Table, Acceptance Tests | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | LeanFlowWasteDelivery | AgileRequirementsExamplesBehavior-Driven Development | AgileDiscoveryDelivery |