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 RecordStrategic, Tactical and Operational PlanningSailboat RetrospectiveStarfish Retrospective
| Criterion |  Architecture Architecture Decision Record |  Business Strategy Strategic, Tactical and Operational Planning |  Agile Sailboat Retrospective |  Agile Starfish Retrospective |
|---|---|---|---|---|
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. | 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. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 15-45 min | 90-180 min | 45-90 min | 45-90 min |
Participantsdifferent | 1-3 | 4-12 | 4-12 | 4-12 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | CadenceGovernanceExecution | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam |