View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)4Ls RetrospectiveLASR (Lightweight Approach for Software Reviews)Expectation Mapping
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Agile 4Ls Retrospective |  Architecture LASR (Lightweight Approach for Software Reviews) |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. |
Complexitydifferent | High | Low | Medium | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 45–75 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 45-90 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | Team members involved | 1 or a small team; particularly suitable for 3–4 people | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | 4Ls Board, Learning Themes, Improvement Actions | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | RetrospectiveLearningReflectionTeam | ArchitectureQualityRiskAssessmentLean | AlignmentStakeholdersTeam |