View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture arc42 | ![]() Business Strategy Strategic, Tactical and Operational Planning | ![]() Agile Sailboat Retrospective | ![]() Agile Start Stop Continue |
|---|---|---|---|---|
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 a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 1-2 Tage | 90-180 min | 45-90 min | 30-60 min |
Participantsdifferent | 1-4 | 4-12 | 4-12 | 3-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 | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | ArchitectureDocumentationCommunication | CadenceGovernanceExecution | RetrospectiveTeamImprovement | RetrospectiveImprovementTeamReflection |



