View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Agile Example Mapping | ![]() Agile 4Ls Retrospective | ![]() Agile Start Stop Continue | ![]() Agile Mad Sad Glad |
|---|---|---|---|---|
Purposedifferent | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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 deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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 | 30-60 min | 45–75 min | 30-60 min | 30-60 min |
Participantsdifferent | 3-7 | Team members involved | 3-12 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | 4Ls Board, Learning Themes, Improvement Actions | Start Stop Continue Board, Improvement Actions | Emotion Board, Themes, Action Items |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementTeamReflection | RetrospectiveTeamReflection |



