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 Double Diamond with its method-specific working model.
Innovation
Double Diamond
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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 of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
Purposedifferent
For complex problems with a fuzzy situation, the method cleanly separates search space and decision. It first creates breadth in understanding and then focus in elaboration. This brings open questions, problem definition, and solution path into a traceable movement.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 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 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
MediumHighLowLow
Timedifferent
Wochen bis MonateSeveral meetings plus preparation and analysis; total effort depends on scope30-60 min20-40 min pro Story
Participantsdifferent
3-12Evaluation team, architects, and relevant stakeholders3-73-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Problem Statement, Solution Options, Prototypes, Deliverables per PhasePrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsExample Map, Acceptance Criteria, Open QuestionsAcceptance Criteria, Story Update
Tagsno overlap
ProcessDivergenceInnovation
ArchitectureQualityRiskTradeoffsStakeholders
Behavior-Driven DevelopmentRequirementsExamplesRefinement
AgileRequirementsRefinementBehavior-Driven Development
Add more methods