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 Architecture Communication Canvas |
|---|---|---|---|---|
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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 45–75 min | 1-3 Tage | 30-60 min | 60-120 min |
Participantsdifferent | Team members involved | 1-4 | 3-10 | 2-8 |
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 | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | RetrospectiveLearningReflectionTeam | DocumentationStakeholdersArchitecture | RetrospectiveTeamReflection | ArchitectureCommunicationStakeholdersCanvas |



