View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling IBIS | ![]() Agile Acceptance Criteria Workshop | ![]() Agile Three Amigos | ![]() Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | When story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 20-40 min pro Story | 15-30 min | 30-60 min |
Participantsdifferent | 2-8 | 3-6 | 3 | 3-7 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Issue Map, Positions, Argument Notes | Acceptance Criteria, Story Update | Clarified Story, Test Examples, Open Questions | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | RationaleKnowledgeDecision | AgileRequirementsRefinementBehavior-Driven Development | CollaborationBehavior-Driven DevelopmentQualityRefinement | Behavior-Driven DevelopmentRequirementsExamplesRefinement |



