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 |  Decision Making Pre-Mortem |  Architecture Request for Comments |  Decision Making Risk Matrix |
|---|---|---|---|---|
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. | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. | 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. | When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 30-90 min | 20–45 min | 1-3 Wochen vom Draft bis zur Entscheidung | 30-60 min |
Participantsdifferent | 3-12 | Small cross-functional group | 3-20 Reviewer | 3-10 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Prioritized Backlog, Release Scope, Tradeoff Notes | Risk list, Mitigation plan, Assumption log | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Risk Matrix, Top Risk List |
Tags1 shared | PrioritizationScopeDecision | RiskDecisionFailurePlanning | ArchitectureDecisionAsyncGovernance | RiskDecisionPrioritizationAssessment |