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 Sprint Retrospective | ![]() Knowledge Modeling IBIS | ![]() Knowledge Modeling Concept Mapping | ![]() Decision Making Argument Mapping |
|---|---|---|---|---|
Purposedifferent | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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 | Low | Medium | Medium | Medium |
Timedifferent | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 1-3 h | 1-2 h | 1-3 h |
Participantsdifferent | Scrum Team | 2-8 | 1-8 | 1-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Improvement actions, Team agreements | Issue Map, Positions, Argument Notes | Concept Map, Relationship Labels, Knowledge Gaps | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | RetrospectiveImprovementLearning | RationaleKnowledgeDecision | KnowledgeConceptsMappingSensemaking | SensemakingDecisionRationale |



