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 |  Agile Scrum |  Agile Specification by Example |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
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 a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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. | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 20-40 min pro Story | 1-4 Wochen je Sprint, laufend | 60-90 min pro Feature | 2-4 h |
Participantsdifferent | 3-6 | 3-10 (Scrum Team) | 3-6 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Acceptance Criteria, Story Update | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Example Table, Acceptance Tests | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | AgileRequirementsRefinementBehavior-Driven Development | AgileIterationCadence | AgileRequirementsExamplesBehavior-Driven Development | OntologyKnowledge graphScopeRequirementsSemantic |