View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Cost of DelayRequest for CommentsSoftware Architecture CanvasArchitecture Communication Canvas
| Criterion |  Delivery Cost of Delay |  Architecture Request for Comments |  Architecture Software Architecture Canvas |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. | 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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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 | High | Medium | Low | Medium |
Timedifferent | 90-180 min | 1-3 Wochen vom Draft bis zur Entscheidung | 1-2 h | 60-120 min |
Participantsdifferent | 3-8 | 3-20 Reviewer | 3-10 | 2-8 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | CoD Table, Prioritization Sequence | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Architecture Canvas, Goals, Constraints, Quality Attributes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | PrioritizationDeliveryEconomicsDecision | ArchitectureDecisionAsyncGovernance | CanvasArchitectureAlignmentWorkshop | ArchitectureCommunicationStakeholdersCanvas |