View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Teach-back |  Domain Modeling Context Map |  Agile Sailboat Retrospective |  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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 5-20 min | 1-3 h | 45-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 2-8 | 2-8 | 4-12 | Scrum Team |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Understanding Check, Clarification Notes, Learning Gaps | Context Map, Integration Patterns, Boundary Notes | Sailboat Board, Risks, Improvement Actions | Improvement actions, Team agreements |
Tagsno overlap | LearningUnderstandingCommunication | Domain-Driven DesignBoundariesStrategy | RetrospectiveTeamImprovement | RetrospectiveImprovementLearning |