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 for Cynefin Workshop.
Decision Making
Cynefin Workshop
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
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.When problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic.After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.
Complexitydifferent
LowMediumMediumLow
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter1-3 h60-180 min20-45 min
Participantsdifferent
Scrum Team1-84-203-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Improvement actions, Team agreementsArgument Map, Evidence Gaps, Decision RationaleCynefin Map, Domain-specific Actions, Sensemaking NotesLessons learned, Action items, Event summary
Tagsno overlap
RetrospectiveImprovementLearning
SensemakingDecisionRationale
ComplexitySensemakingDecision
LearningOperationsImprovement
Add more methods