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 PlanningAfter-Action Review
| Criterion |  Architecture Architecture Decision Record |  Agile Sprint Retrospective |  Business Strategy Strategic, Tactical and Operational Planning |  Operations After-Action Review |
|---|---|---|---|---|
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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
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 | 20-45 min |
Participantsdifferent | 1-3 | Scrum Team | 4-12 | 3-12 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Improvement actions, Team agreements | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Lessons learned, Action items, Event summary |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RetrospectiveImprovementLearning | CadenceGovernanceExecution | LearningOperationsImprovement |