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 Domain Storytelling |  Agile 4Ls Retrospective |  Agile Sailboat Retrospective |  Agile Sprint Retrospective |
|---|---|---|---|---|
Purposedifferent | Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 1-2 h | 45–75 min | 45-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 2-8 | Team members involved | 4-12 | Scrum Team |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | 4Ls Board, Learning Themes, Improvement Actions | Sailboat Board, Risks, Improvement Actions | Improvement actions, Team agreements |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | RetrospectiveLearningReflectionTeam | RetrospectiveTeamImprovement | RetrospectiveImprovementLearning |