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 | ![]() Knowledge Modeling IBIS | ![]() Operations 8D Problem Solving | ![]() Agile Specification by Example |
|---|---|---|---|---|
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. | 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. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. | 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 | High | Medium |
Timedifferent | 30-60 min | 1-3 h | 1-6 Wochen | 60-90 min pro Feature |
Participantsdifferent | 3-7 | 2-8 | 4-10 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Issue Map, Positions, Argument Notes | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Example Table, Acceptance Tests |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RationaleKnowledgeDecision | QualityProblem solvingRoot cause | AgileRequirementsExamplesBehavior-Driven Development |



