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 |  Decision Making Decision Rights Mapping |  Architecture Request for Comments |
|---|---|---|---|
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. | 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. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 90-180 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 3-10 (Scrum Team) | 4-12 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop | Async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Decision Rights Matrix, Agreement | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | AgileIterationCadence | DecisionGovernanceAlignmentResponsibility | ArchitectureDecisionAsyncGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
