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 Mad Sad Glad |  Agile Sailboat Retrospective |  Architecture Risk Storming |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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 | 30-60 min | 45-90 min | 60-90 min | 45–75 min |
Participantsdifferent | 3-10 | 4-12 | 4-12 | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Emotion Board, Themes, Action Items | Sailboat Board, Risks, Improvement Actions | Annotated Diagram, Prioritized Risk List, Action Backlog | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | RetrospectiveTeamReflection | RetrospectiveTeamImprovement | RiskArchitectureWorkshopValidation | RetrospectiveLearningReflectionTeam |