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 Sprint Retrospective |  Agile 4Ls Retrospective |  Agile Mad Sad Glad |
|---|---|---|---|---|
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 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. | 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's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 1-2 h | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45–75 min | 30-60 min |
Participantsdifferent | 2-8 | Scrum Team | Team members involved | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Improvement actions, Team agreements | 4Ls Board, Learning Themes, Improvement Actions | Emotion Board, Themes, Action Items |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | RetrospectiveImprovementLearning | RetrospectiveLearningReflectionTeam | RetrospectiveTeamReflection |