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 Sailboat Retrospective |  Agile 4Ls Retrospective |  Agile Starfish 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 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 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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 1-2 h | 45-90 min | 45–75 min | 45-90 min |
Participantsdifferent | 2-8 | 4-12 | Team members involved | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Sailboat Board, Risks, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | RetrospectiveTeamImprovement | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementExperimentsTeam |