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 Personas |  Agile Example Mapping |  Agile Three Amigos |
|---|---|---|---|---|
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 target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions. | 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 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 60-90 min pro Feature | 1-3 Tage | 30-60 min | 15-30 min |
Participantsdifferent | 3-6 | Internes Team | 3-7 | 3 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Persona Profiles, Needs Summary, Scenario Notes | Example Map, Acceptance Criteria, Open Questions | Clarified Story, Test Examples, Open Questions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | ResearchCustomerSynthesis | Behavior-Driven DevelopmentRequirementsExamplesRefinement | CollaborationBehavior-Driven DevelopmentQualityRefinement |