View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Expectation MappingRequest for CommentsROAM BoardATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Facilitation Expectation Mapping |  Architecture Request for Comments |  Agile ROAM Board |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | 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. |
Complexitydifferent | Low | Medium | Low | High |
Timedifferent | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 20-40 min initial, dann laufend | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-12 | 3-20 Reviewer | 3-15 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | ROAM Board, Owner List | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | AlignmentStakeholdersTeam | ArchitectureDecisionAsyncGovernance | RiskAgileTrackingAlignment | ArchitectureQualityRiskTradeoffsStakeholders |