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 Example Mapping |  Agile Acceptance Criteria Workshop |  Knowledge Modeling IBIS |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 30-60 min | 20-40 min pro Story | 1-3 h | 15-45 min |
Participantsdifferent | 3-7 | 3-6 | 2-8 | 1-3 |
Formatdifferent | Workshop | Workshop | Workshop + async | Async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Acceptance Criteria, Story Update | Issue Map, Positions, Argument Notes | ADR File, Decision Log, Rationale |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsRefinementBehavior-Driven Development | RationaleKnowledgeDecision | ArchitectureRationaleDocumentationGovernance |