View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Scrum |  Business Strategy Strategic, Tactical and Operational Planning |  Architecture Architecture Decision Record |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | It places decisions and artifacts at the right level. Strategic planning clarifies direction, tactical planning translates it into programs, and operational planning steers concrete processes. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 90-180 min | 15-45 min | 1-2 Tage |
Participantsdifferent | 3-10 (Scrum Team) | 4-12 | 1-3 | 1-4 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Planning Levels Map, Cadence Model, Planning Artifact Inventory | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | AgileIterationCadence | CadenceGovernanceExecution | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication |