MoSCoW prioritization and WSJF explained for the CAPM
MoSCoW sorts backlog and roadmap items into must haves, should haves, could haves and will not haves, and GOV.UK recommends it for building consensus in a team. Other methods suit other needs: a prioritisation quadrant balances different types of work, and SAFe's Weighted Shortest Job First ranks work by cost of delay divided by duration.
The four MoSCoW categories
Must haves are essential things the product cannot function without.
Should haves can greatly improve the product but are not crucial to making it function.
Could haves can improve the service but will not have too negative an impact if left out at this stage.
Will not haves are low priority things the team has agreed not to do.
How GOV.UK says to prioritise
Prioritise regularly, for example weekly for the sprint backlog and quarterly for the service roadmap. Base decisions on performance analysis, user research and stakeholder input. The person leading the exercise uses a clear method and involves the delivery team and stakeholders.
A backlog holds more than new features: support tickets and technical debt tasks need priority too. Something like a prioritisation quadrant helps make sure enough different types of work are prioritised. Priorities also shift by phase: in beta you prioritise improvements as you test, and in live you balance support work with improvements.
Weighted Shortest Job First in SAFe
SAFe defines WSJF as a prioritization model used to sequence work for maximum economic benefit. It is estimated as the relative cost of delay divided by the relative job duration, using relative user and business value, time criticality, risk reduction or opportunity enablement, and job size.
Where the exam catches people
Believing 'should have' means essential: should haves greatly improve the product but are not crucial to making it function.
Believing 'will not have' items were rejected by the product owner alone: they are things the team has agreed not to do.
Believing MoSCoW is the right tool to balance features, support tickets and technical debt: GOV.UK points to a prioritisation quadrant for that.
Believing WSJF ranks by value alone: it divides cost of delay by job duration.