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 of an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
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.
Complexitydifferent
LowMedium
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter1-3 h
Participantsdifferent
Scrum Team2-8
Formatdifferent
WorkshopWorkshop + async
Outputdifferent
Improvement actions, Team agreementsIssue Map, Positions, Argument Notes
Tagsno overlap
RetrospectiveImprovementLearning
RationaleKnowledgeDecision
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration for Feynman Technique.
Knowledge Modeling
Feynman Technique