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 Strategy Execution Loop |  Architecture C4 Model |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. |
Complexitydifferent | Medium | High | Low | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | Initial 3-6 h, then monthly or quarterly reviews | 1-4 h | 15-45 min |
Participantsdifferent | 3-10 (Scrum Team) | 5-12 | 1-5 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Execution Loop, Review Cadence, Strategic Learning Log | Context Diagram, Container Diagram, Component Diagram | ADR File, Decision Log, Rationale |
Tagsno overlap | AgileIterationCadence | ExecutionCadenceLearningGovernance | ArchitectureCommunicationVisualization | ArchitectureRationaleDocumentationGovernance |