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 4Ls Retrospective | ![]() Architecture Views and Beyond | ![]() Agile Mad Sad Glad | ![]() Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45–75 min | 1-3 Tage | 30-60 min | 1-2 Tage |
Participantsdifferent | Team members involved | 1-4 | 3-10 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Architecture Views, Cross-view Notes, Rationale | Emotion Board, Themes, Action Items | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | RetrospectiveLearningReflectionTeam | DocumentationStakeholdersArchitecture | RetrospectiveTeamReflection | ArchitectureDocumentationCommunication |



