View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Scrum |  Business Strategy Strategy Execution Loop |  Architecture Request for Comments |  Decision Making Decision Rights Mapping |
|---|---|---|---|---|
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. | The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | Initial 3-6 h, then monthly or quarterly reviews | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min |
Participantsdifferent | 3-10 (Scrum Team) | 5-12 | 3-20 Reviewer | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Execution Loop, Review Cadence, Strategic Learning Log | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Decision Rights Matrix, Agreement |
Tagsno overlap | AgileIterationCadence | ExecutionCadenceLearningGovernance | ArchitectureDecisionAsyncGovernance | DecisionGovernanceAlignmentResponsibility |