View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Golden Path |  Knowledge Modeling Teach-back |  Agile Sailboat Retrospective |  Agile Sprint Retrospective |
|---|---|---|---|---|
Purposedifferent | When teams need a reliable default path for frequent use, sprawl quickly emerges without any guiding logic. Golden Path bundles the preferred path so good practice becomes easy and deviation becomes deliberate. | 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 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 | Medium | Low | Low | Low |
Timedifferent | 1-3 Tage Setup, laufend | 5-20 min | 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 | Golden Path Guide, Templates, Quality Checks | Understanding Check, Clarification Notes, Learning Gaps | Sailboat Board, Risks, Improvement Actions | Improvement actions, Team agreements |
Tagsno overlap | EngineeringProductivityGovernance | LearningUnderstandingCommunication | RetrospectiveTeamImprovement | RetrospectiveImprovementLearning |