View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery MoSCoW |  Delivery RAID Log |  Architecture Request for Comments |
|---|---|---|---|
Purposedifferent | When a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 30-90 min | 30 min Setup, dann laufend | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 3-20 Reviewer |
Formatdifferent | Workshop + async | Async | Async |
Outputdifferent | Prioritized Backlog, Release Scope, Tradeoff Notes | RAID Log, Status Report Source | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | PrioritizationScopeDecision | RiskTrackingStakeholdersGovernance | ArchitectureDecisionAsyncGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
