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 of Lean Startup with its method-specific working model.
Innovation
Lean Startup
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration for Change Analysis.
Operations
Change Analysis
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Purposedifferent
For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.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.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
Wochen bis Monate je Lernzyklus2–4 h review as a planning range; preparation and evaluation additional45-120 minPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
2-8Designers, developers as users, and facilitation2-6Architecture experts and stakeholders for scenarios and weighting
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Hypothesis list, MVPs, Learning reports, Pivot or persevere decisionPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsChange Matrix, Cause Hypotheses, Validation Questions, Action ListDomain 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
Tagsno overlap
LeanStartupValidationMVP
ArchitectureEngineeringFeedbackValidationTasks
ChangeRoot causeTroubleshootingComparison
ArchitectureChangeAnalysisComparisonQuality
Add more methods