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)Learning ReviewStart Stop ContinueLASR (Lightweight Approach for Software Reviews)
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Learning Review |  Agile Start Stop Continue |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
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. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. | 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. | 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. |
Complexitydifferent | High | Medium | Low | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 h | 30-60 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-10 | 3-12 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Learning Review Notes, System Factors, Improvement Actions | Start Stop Continue Board, 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 |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | LearningRetrospectiveIncidentOperations | RetrospectiveImprovementTeamReflection | ArchitectureQualityRiskAssessmentLean |