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 fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of Specification by Example with a method-specific labelled workspace.
Agile
Specification by Example
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.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.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 business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests.
Complexitydifferent
LowLowHighMedium
Timedifferent
30-60 min30-60 minSeveral meetings plus preparation and analysis; total effort depends on scope60-90 min pro Feature
Participantsdifferent
3-72-8Evaluation team, architects, and relevant stakeholders3-6
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Example Map, Acceptance Criteria, Open QuestionsFishbone Diagram, Cause Categories, Investigation BacklogPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsExample Table, Acceptance Tests
Tagsno overlap
Behavior-Driven DevelopmentRequirementsExamplesRefinement
Root causeQualityOperations
ArchitectureQualityRiskTradeoffsStakeholders
AgileRequirementsExamplesBehavior-Driven Development
Add more methods