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 |  Knowledge Modeling IBIS |  Architecture Architecture Decision Record |  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. | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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 | Low | Medium |
Timedifferent | 20-40 min pro Story | 1-3 h | 15-45 min | 60-90 min pro Feature |
Participantsdifferent | 3-6 | 2-8 | 1-3 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
Outputdifferent | Acceptance Criteria, Story Update | Issue Map, Positions, Argument Notes | ADR File, Decision Log, Rationale | Example Table, Acceptance Tests |
Tagsno overlap | AgileRequirementsRefinementBehavior-Driven Development | RationaleKnowledgeDecision | ArchitectureRationaleDocumentationGovernance | AgileRequirementsExamplesBehavior-Driven Development |