View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Contextual Inquiry |  Agile Specification by Example |  Agile Acceptance Criteria Workshop |
|---|---|---|---|
Purposedifferent | 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. | 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 | 1-3 Wochen | 60-90 min pro Feature | 20-40 min pro Story |
Participantsdifferent | 4-12 Beobachtungen | 3-6 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Example Table, Acceptance Tests | Acceptance Criteria, Story Update |
Tagsno overlap | UX researchObservationContext | AgileRequirementsExamplesBehavior-Driven Development | AgileRequirementsRefinementBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
