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
Paper illustration for Teach-back.
Knowledge Modeling
Teach-back
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
Purposedifferent
Teach-back checks whether an explanation actually got through to the other person. The method makes misunderstandings visible early and strengthens shared understanding in advisory and learning situations.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.
Complexitysame
LowLow
Timedifferent
5-20 minUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter
Participantsdifferent
2-8Scrum Team
Formatdifferent
Workshop + asyncWorkshop
Outputdifferent
Understanding Check, Clarification Notes, Learning GapsImprovement actions, Team agreements
Tags1 shared
LearningUnderstandingCommunication
RetrospectiveImprovementLearning
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 Feynman Technique.
Knowledge Modeling
Feynman Technique
Paper illustration for Learning Review.
Operations
Learning Review