View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ScrumStrategic, Tactical and Operational PlanningSpecification by ExampleArchitecture Decision Record
| Criterion |  Agile Scrum |  Business Strategy Strategic, Tactical and Operational Planning |  Agile Specification by Example |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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 business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 90-180 min | 60-90 min pro Feature | 15-45 min |
Participantsdifferent | 3-10 (Scrum Team) | 4-12 | 3-6 | 1-3 |
Formatdifferent | Workshop + async | Workshop | Workshop | Async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Example Table, Acceptance Tests | ADR File, Decision Log, Rationale |
Tagsno overlap | AgileIterationCadence | CadenceGovernanceExecution | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureRationaleDocumentationGovernance |