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 Mad Sad Glad |  Agile Starfish Retrospective |  Agile 4Ls 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'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. | 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 1-2 h | 30-60 min | 45-90 min | 45–75 min |
Participantsdifferent | 2-8 | 3-10 | 4-12 | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Emotion Board, Themes, Action Items | Starfish Board, Practice Changes, Experiments | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | RetrospectiveTeamReflection | RetrospectiveImprovementExperimentsTeam | RetrospectiveLearningReflectionTeam |