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 a MoSCoW board with four columns and a visible release boundary.
Delivery
MoSCoW
Paper illustration for Change Analysis.
Operations
Change Analysis
Paper illustration for Pareto Analysis
Decision Making
Pareto Analysis
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Purposedifferent
When a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved.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.In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle.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
LowMediumLowHigh
Timedifferent
30-90 min45-120 min30-60 minPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
3-122-61-6Architecture experts and stakeholders for scenarios and weighting
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized Backlog, Release Scope, Tradeoff NotesChange Matrix, Cause Hypotheses, Validation Questions, Action ListPareto Chart, Top Causes, Focus 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
PrioritizationScopeDecision
ChangeRoot causeTroubleshootingComparison
PrioritizationQualityFocusRoot cause
ArchitectureChangeAnalysisComparisonQuality
Add more methods