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 Specification by Example |  UX Research User Interviews |  Agile Example Mapping |  Product Discovery Dual-Track Agile |
|---|---|---|---|---|
Purposedifferent | 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 teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | 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 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 | Low | Medium |
Timedifferent | 60-90 min pro Feature | 30–60 min per interview | 30-60 min | Laufend, Wochen bis Monate |
Participantsdifferent | 3-6 | 1 participant per interview | 3-7 | 4-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Interview Notes, Themes, Insight Summary | Example Map, Acceptance Criteria, Open Questions | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | QualitativeResearchCustomerDiscovery | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileDiscoveryDelivery |