View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:4Ls RetrospectiveArchitecture Decision RecordArchitecture Communication CanvasStart Stop Continue
| Criterion | ![]() Agile 4Ls Retrospective | ![]() Architecture Architecture Decision Record | ![]() Architecture Architecture Communication Canvas | ![]() Agile Start Stop Continue |
|---|---|---|---|---|
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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 45–75 min | 15-45 min | 60-120 min | 30-60 min |
Participantsdifferent | Team members involved | 1-3 | 2-8 | 3-12 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | ADR File, Decision Log, Rationale | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | RetrospectiveLearningReflectionTeam | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationStakeholdersCanvas | RetrospectiveImprovementTeamReflection |



