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 |  Architecture Views and Beyond |  Agile 4Ls Retrospective |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30-60 min | 1-3 Tage | 45–75 min | 15-45 min |
Participantsdifferent | 3-10 | 1-4 | Team members involved | 1-3 |
Formatdifferent | Workshop | Workshop + async | Workshop | Async |
Outputdifferent | Emotion Board, Themes, Action Items | Architecture Views, Cross-view Notes, Rationale | 4Ls Board, Learning Themes, Improvement Actions | ADR File, Decision Log, Rationale |
Tagsno overlap | RetrospectiveTeamReflection | DocumentationStakeholdersArchitecture | RetrospectiveLearningReflectionTeam | ArchitectureRationaleDocumentationGovernance |