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 Acceptance Criteria Workshop |  UX Research Contextual Inquiry |  Agile Specification by Example |
|---|---|---|---|
Purposedifferent | 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 work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise. | 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. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 20-40 min pro Story | 1-3 Wochen | 60-90 min pro Feature |
Participantsdifferent | 3-6 | 4-12 Beobachtungen | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Acceptance Criteria, Story Update | Field Notes, Workflow Insights, Pain Points | Example Table, Acceptance Tests |
Tagsno overlap | AgileRequirementsRefinementBehavior-Driven Development | UX researchObservationContext | AgileRequirementsExamplesBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
