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 |  Agile Scrum |  Knowledge Modeling Competency Questions |  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 a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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. | 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 | Medium | Low |
Timedifferent | 60-90 min pro Feature | 1-4 Wochen je Sprint, laufend | 2-4 h | 20-40 min pro Story |
Participantsdifferent | 3-6 | 3-10 (Scrum Team) | 2-8 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Acceptance Criteria, Story Update |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | AgileIterationCadence | OntologyKnowledge graphScopeRequirementsSemantic | AgileRequirementsRefinementBehavior-Driven Development |