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 Knowledge Mapping.
Knowledge Modeling
Knowledge 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.Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.
Complexitydifferent
LowMedium
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter1-3 h
Participantsdifferent
Scrum Team3-12
Formatsame
WorkshopWorkshop
Outputdifferent
Improvement actions, Team agreementsKnowledge Map, Critical Knowledge Areas, Transfer Plan
Tagsno overlap
RetrospectiveImprovementLearning
KnowledgeMappingRisk
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 of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
Paper illustration for Feynman Technique.
Knowledge Modeling
Feynman Technique