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 | ![]() UX Design Lean UX Canvas | ![]() 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. | The Lean UX Canvas helps clarify user behavior, touchpoints, and concept decisions. It makes assumptions and desired outcomes visible and captures the result as a completed canvas, hypothesis list, and first experiment. | 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 | 2-3 h | 60-90 min pro Feature | Laufend, Wochen bis Monate |
Participantsdifferent | 3-7 | 3-8 | 3-6 | 4-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Completed Lean UX Canvas, Hypothesis list, First experiment | Example Table, Acceptance Tests | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | CanvasHypothesisOutcomesDiscovery | AgileRequirementsExamplesBehavior-Driven Development | AgileDiscoveryDelivery |



