methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of a MoSCoW board with four columns and a visible release boundary.
Delivery
MoSCoW
A paper-based illustration representing WSJF with its core stages and visible working result.
Agile
WSJF
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
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.When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together.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.When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.
Complexitydifferent
LowHighLowLow
Timedifferent
30-90 min45-90 min20–45 min30-90 min
Participantsdifferent
3-123-10Small cross-functional group2-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Prioritized Backlog, Release Scope, Tradeoff NotesRanked Backlog, Cost-of-Delay AssumptionsRisk list, Mitigation plan, Assumption logConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
PrioritizationScopeDecision
LeanEconomicsSequencePrioritization
RiskDecisionFailurePlanning
ConstraintsDecisionPlanningOptions
Add more methods