View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Kano Model |  Agile Acceptance Criteria Workshop |  Agile Example Mapping |  Agile Three Amigos |
|---|---|---|---|---|
Purposedifferent | When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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 | Low | Low | Low |
Timedifferent | 1-2 Tage | 20-40 min pro Story | 30-60 min | 15-30 min |
Participantsdifferent | 10-50 | 3-6 | 3-7 | 3 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Acceptance Criteria, Story Update | Example Map, Acceptance Criteria, Open Questions | Clarified Story, Test Examples, Open Questions |
Tagsno overlap | SatisfactionPrioritizationCustomer | AgileRequirementsRefinementBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement | CollaborationBehavior-Driven DevelopmentQualityRefinement |