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 yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
Paper illustration for Change Analysis.
Operations
Change Analysis
Paper illustration of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Purposedifferent
When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound.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.When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update.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-60 min45-120 min20-40 min pro StoryPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
3-72-63-6Architecture experts and stakeholders for scenarios and weighting
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Example Map, Acceptance Criteria, Open QuestionsChange Matrix, Cause Hypotheses, Validation Questions, Action ListAcceptance Criteria, Story UpdateDomain 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
Behavior-Driven DevelopmentRequirementsExamplesRefinement
ChangeRoot causeTroubleshootingComparison
AgileRequirementsRefinementBehavior-Driven Development
ArchitectureChangeAnalysisComparisonQuality
Add more methods