View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Shape UpARID (Active Reviews for Intermediate Designs)Communication PlanATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Delivery Shape Up |  Architecture ARID (Active Reviews for Intermediate Designs) |  Delivery Communication Plan |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | 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. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 6 Wochen Cycle + 2 Wochen Cool-Down | 2–4 h review as a planning range; preparation and evaluation additional | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 2-4 pro Pitch | Designers, developers as users, and facilitation | 2-6 | Evaluation team, architects, and relevant stakeholders |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | 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 |
Tagsno overlap | PlanningDeliveryAutonomy | ArchitectureEngineeringFeedbackValidationTasks | CommunicationStakeholdersDeliveryPlanning | ArchitectureQualityRiskTradeoffsStakeholders |