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 |  Product Discovery Problem Interview |  Agile Acceptance Criteria Workshop |
|---|---|---|---|
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 the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. | 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. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 60-90 min pro Feature | 30-60 min je Interview | 20-40 min pro Story |
Participantsdifferent | 3-6 | 5-12 Interviews | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Problem Evidence, Risk Notes, Customer Segments | Acceptance Criteria, Story Update |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | DiscoveryInterviewsValidation | AgileRequirementsRefinementBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
