View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Example MappingATAM (Architecture Tradeoff Analysis Method)Acceptance Criteria WorkshopArchitecture Communication Canvas
| Criterion |  Agile Example Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Agile Acceptance Criteria Workshop |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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 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. |
Complexitydifferent | Low | High | Low | Medium |
Timedifferent | 30-60 min | Several meetings plus preparation and analysis; total effort depends on scope | 20-40 min pro Story | 60-120 min |
Participantsdifferent | 3-7 | Evaluation team, architects, and relevant stakeholders | 3-6 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Acceptance Criteria, Story Update | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ArchitectureQualityRiskTradeoffsStakeholders | AgileRequirementsRefinementBehavior-Driven Development | ArchitectureCommunicationStakeholdersCanvas |