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 Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
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
Purposedifferent
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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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.
Complexitydifferent
LowMediumHighLow
Timedifferent
20-40 min pro Story60-120 minSeveral meetings plus preparation and analysis; total effort depends on scope30-60 min
Participantsdifferent
3-62-8Evaluation team, architects, and relevant stakeholders3-7
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Acceptance Criteria, Story UpdateCommunication Canvas, Stakeholder Messages, Architecture Communication PlanPrioritized 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 Questions
Tagsno overlap
AgileRequirementsRefinementBehavior-Driven Development
ArchitectureCommunicationStakeholdersCanvas
ArchitectureQualityRiskTradeoffsStakeholders
Behavior-Driven DevelopmentRequirementsExamplesRefinement
Add more methods