View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery Shape Up | ![]() Architecture Architecture Decision Record | ![]() Delivery RAID Log | ![]() Delivery Communication Plan |
|---|---|---|---|---|
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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 6 Wochen Cycle + 2 Wochen Cool-Down | 15-45 min | 30 min Setup, dann laufend | 45-90 min |
Participantsdifferent | 2-4 pro Pitch | 1-3 | 1-3 maintaining, briefing for everyone | 2-6 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | ADR File, Decision Log, Rationale | RAID Log, Status Report Source | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | PlanningDeliveryAutonomy | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance | CommunicationStakeholdersDeliveryPlanning |



