methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration of an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
Paper illustration of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept 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.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.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.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter1-3 h1-3 h1-2 h
Participantsdifferent
Scrum Team1-82-81-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Improvement actions, Team agreementsArgument Map, Evidence Gaps, Decision RationaleIssue Map, Positions, Argument NotesConcept Map, Relationship Labels, Knowledge Gaps
Tagsno overlap
RetrospectiveImprovementLearning
SensemakingDecisionRationale
RationaleKnowledgeDecision
KnowledgeConceptsMappingSensemaking
Add more methods