View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Request for CommentsCommunication PlanATAM (Architecture Tradeoff Analysis Method)Pre-Mortem
| Criterion |  Architecture Request for Comments |  Delivery Communication Plan |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Decision Making Pre-Mortem |
|---|---|---|---|---|
Purposedifferent | 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 many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | 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. | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 20–45 min |
Participantsdifferent | 3-20 Reviewer | 2-6 | Evaluation team, architects, and relevant stakeholders | Small cross-functional group |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Communication Plan, Channel Matrix, Message Cadence | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | CommunicationStakeholdersDeliveryPlanning | ArchitectureQualityRiskTradeoffsStakeholders | RiskDecisionFailurePlanning |