methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for Eat the Frog
Operations
Eat the Frog
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration for Ivy Lee Method
Operations
Ivy Lee Method
Purposedifferent
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.The method protects energy and attention for the task that creates the largest progress and is often postponed.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.With a restless workday full of too many open items, the method creates radical simplicity. It directs attention to a short sequence instead of a broad, still-open field.
Complexitydifferent
HighLowMediumLow
Timedifferent
Preparation, scenario analysis, and findings review; effort depends on scope15-90 min daily3–4 h for initial assessment; preparation and deeper analysis additional5-10 min daily
Participantsdifferent
Architecture experts and stakeholders for scenarios and weighting11 or a small team; particularly suitable for 3–4 people1
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncAsync
Outputdifferent
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 alternativesPriority Task, Completion Note, Daily FocusLean 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 checksDaily Priority List, Completion Notes
Tagsno overlap
ArchitectureChangeAnalysisComparisonQuality
PrioritizationProductivityFocusExecution
ArchitectureQualityRiskAssessmentLean
PrioritizationProductivityExecution
Add more methods