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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
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.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.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.
Complexitydifferent
LowHighLowLow
Timedifferent
30-60 minSeveral meetings plus preparation and analysis; total effort depends on scope30-60 min20-40 min pro Story
Participantsdifferent
3-7Evaluation team, architects, and relevant stakeholders2-83-6
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Example Map, Acceptance Criteria, Open QuestionsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsFishbone Diagram, Cause Categories, Investigation BacklogAcceptance Criteria, Story Update
Tagsno overlap
Behavior-Driven DevelopmentRequirementsExamplesRefinement
ArchitectureQualityRiskTradeoffsStakeholders
Root causeQualityOperations
AgileRequirementsRefinementBehavior-Driven Development
Add more methods