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 ATAM (Architecture Tradeoff Analysis Method) |  Delivery RAID Log |  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. | 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. | 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 | High | Low | Low |
Timedifferent | 45–75 min | Several meetings plus preparation and analysis; total effort depends on scope | 30 min Setup, dann laufend | 30-60 min |
Participantsdifferent | Team members involved | Evaluation team, architects, and relevant stakeholders | 1-3 maintaining, briefing for everyone | 3-12 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
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 | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | RetrospectiveLearningReflectionTeam | ArchitectureQualityRiskTradeoffsStakeholders | RiskTrackingStakeholdersGovernance | RetrospectiveImprovementTeamReflection |