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 Specification by Example | ![]() Agile Planning Poker | ![]() Decision Making Argument 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 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. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 60-90 min pro Feature | 2-5 min je Item | 1-3 h |
Participantsdifferent | 2-8 | 3-6 | 3-9 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Issue Map, Positions, Argument Notes | Example Table, Acceptance Tests | Relative Estimates, Assumption Notes, Split Candidates | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | RationaleKnowledgeDecision | AgileRequirementsExamplesBehavior-Driven Development | EstimationAgileRelative sizingTeam | SensemakingDecisionRationale |



