View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:arc42Strategic, Tactical and Operational PlanningSailboat RetrospectiveStarfish Retrospective
| Criterion |  Architecture arc42 |  Business Strategy Strategic, Tactical and Operational Planning |  Agile Sailboat Retrospective |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | 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 | 1-2 Tage | 90-180 min | 45-90 min | 45-90 min |
Participantsdifferent | 1-4 | 4-12 | 4-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | ArchitectureDocumentationCommunication | CadenceGovernanceExecution | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam |