View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ICE ScoringSAAM (Software Architecture Analysis Method)Risk MatrixLASR (Lightweight Approach for Software Reviews)
| Criterion |  Product Strategy ICE Scoring |  Architecture SAAM (Software Architecture Analysis Method) |  Decision Making Risk Matrix |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | When ideas need sorting quickly, it condenses impact, confidence, and effort into one compact score. It connects customer value, product logic, and decision priorities. The result is captured as an ICE table and top-ideas list. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List. | 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 | Low | High | Low | Medium |
Timedifferent | 30-60 min | Preparation, scenario analysis, and findings review; effort depends on scope | 30-60 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 2-8 | Architecture experts and stakeholders for scenarios and weighting | 3-10 | 1 or a small team; particularly suitable for 3–4 people |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ICE Table, Top Idea List | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Risk Matrix, Top Risk List | 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 | PrioritizationScoringGrowthDecision | ArchitectureChangeAnalysisComparisonQuality | RiskDecisionPrioritizationAssessment | ArchitectureQualityRiskAssessmentLean |