View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Value Stream Mapping |  Agile Three Amigos |  Agile Specification by Example |  Product Discovery Dual-Track Agile |
|---|---|---|---|---|
Purposedifferent | 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 story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | 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 | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h | 15-30 min | 60-90 min pro Feature | Laufend, Wochen bis Monate |
Participantsdifferent | 4-10 | 3 | 3-6 | 4-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Clarified Story, Test Examples, Open Questions | Example Table, Acceptance Tests | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories |
Tagsno overlap | LeanFlowWasteDelivery | CollaborationBehavior-Driven DevelopmentQualityRefinement | AgileRequirementsExamplesBehavior-Driven Development | AgileDiscoveryDelivery |