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 Cost of Delay |  Delivery MoSCoW |  Facilitation Stakeholder Mapping |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. | 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | 90-180 min | 30-90 min | 60–90 min | 60-90 min |
Participantsdifferent | 3-8 | 3-12 | 2-8 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | CoD Table, Prioritization Sequence | Prioritized Backlog, Release Scope, Tradeoff Notes | Stakeholder Map, Engagement Plan, Risk Notes | Salience Diagram, Strategy per Class |
Tagsno overlap | PrioritizationDeliveryEconomicsDecision | PrioritizationScopeDecision | StakeholdersAlignmentFacilitationChange | StakeholdersFacilitationAlignmentGovernance |