View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordSprint RetrospectiveStrategic, Tactical and Operational Planningarc42
| Criterion |  Architecture Architecture Decision Record |  Agile Sprint Retrospective |  Business Strategy Strategic, Tactical and Operational Planning |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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. | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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. | 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 | Low | Low | Medium | Low |
Timedifferent | 15-45 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 90-180 min | 1-2 Tage |
Participantsdifferent | 1-3 | Scrum Team | 4-12 | 1-4 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Improvement actions, Team agreements | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RetrospectiveImprovementLearning | CadenceGovernanceExecution | ArchitectureDocumentationCommunication |