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 RetrospectiveATAM (Architecture Tradeoff Analysis Method)RAID LogArchitecture Communication Canvas
| Criterion | ![]() Agile 4Ls Retrospective | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Delivery RAID Log | ![]() 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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 | High | Low | Medium |
Timedifferent | 45–75 min | Several meetings plus preparation and analysis; total effort depends on scope | 30 min Setup, dann laufend | 60-120 min |
Participantsdifferent | Team members involved | Evaluation team, architects, and relevant stakeholders | 1-3 maintaining, briefing for everyone | 2-8 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | RAID Log, Status Report Source | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | RetrospectiveLearningReflectionTeam | ArchitectureQualityRiskTradeoffsStakeholders | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationStakeholdersCanvas |



