View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy Strategy Execution Loop |  Agile Scrum |  Architecture arc42 |  Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 1-4 Wochen je Sprint, laufend | 1-2 Tage | 1-4 h |
Participantsdifferent | 5-12 | 3-10 (Scrum Team) | 1-4 | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Architecture Document, Context View, Runtime View, Deployment View | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | ExecutionCadenceLearningGovernance | AgileIterationCadence | ArchitectureDocumentationCommunication | ArchitectureCommunicationVisualization |