View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy Strategic, Tactical and Operational Planning |  Agile Sprint Retrospective |  Agile Sailboat Retrospective |
|---|---|---|---|
Purposedifferent | 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 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. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 90-180 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45-90 min |
Participantsdifferent | 4-12 | Scrum Team | 4-12 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Improvement actions, Team agreements | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | CadenceGovernanceExecution | RetrospectiveImprovementLearning | RetrospectiveTeamImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
