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 CATWOE Analysis.
Systems Thinking
CATWOE Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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.CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way.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 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
LowMediumHighLow
Timedifferent
30-60 min45-90 minSeveral meetings plus preparation and analysis; total effort depends on scope20-40 min pro Story
Participantsdifferent
3-73-8Evaluation team, architects, and relevant stakeholders3-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Example Map, Acceptance Criteria, Open QuestionsCATWOE Canvas, Root Definition, Stakeholder Perspectives, ConstraintsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsAcceptance Criteria, Story Update
Tagsno overlap
Behavior-Driven DevelopmentRequirementsExamplesRefinement
Systems thinkingFramingStakeholders
ArchitectureQualityRiskTradeoffsStakeholders
AgileRequirementsRefinementBehavior-Driven Development
Add more methods