View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:LASR (Lightweight Approach for Software Reviews)ATAM (Architecture Tradeoff Analysis Method)Kanban
| Criterion |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Engineering Kanban |
|---|---|---|---|
Purposedifferent | 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. | 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 work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 3–4 h for initial assessment; preparation and deeper analysis additional | Several meetings plus preparation and analysis; total effort depends on scope | Ongoing |
Participantsdifferent | 1 or a small team; particularly suitable for 3–4 people | Evaluation team, architects, and relevant stakeholders | 2-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | 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 | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | ArchitectureQualityRiskAssessmentLean | ArchitectureQualityRiskTradeoffsStakeholders | FlowVisual managementDelivery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
