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 |  Knowledge Modeling IBIS |  Agile Acceptance Criteria Workshop |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 60-90 min pro Feature | 1-3 h | 20-40 min pro Story | 15-45 min |
Participantsdifferent | 3-6 | 2-8 | 3-6 | 1-3 |
Formatdifferent | Workshop | Workshop + async | Workshop | Async |
Outputdifferent | Example Table, Acceptance Tests | Issue Map, Positions, Argument Notes | Acceptance Criteria, Story Update | ADR File, Decision Log, Rationale |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | RationaleKnowledgeDecision | AgileRequirementsRefinementBehavior-Driven Development | ArchitectureRationaleDocumentationGovernance |