Practice knowledge base
Prioritization methods (WSJF, MoSCoW)
WSJF and MoSCoW help the team choose tasks based on value, urgency, risk, and constraints, rather than on who has the loudest voice in the discussion.
Documentation sections
What it is
Prioritization methods set shared rules for deciding what to do sooner, later, or not do for now. WSJF compares initiatives by value, urgency, risk reduction, and effort size. MoSCoW divides tasks into must-have, important, desirable, and deferred. This practice is useful when the team has more ideas than time, and debates about priorities become emotional.
When it helps
- The team regularly argues about which tasks matter more, but does not use shared selection criteria.
- Too many initiatives make it into the work, and important tasks compete with urgent requests.
- The manager or stakeholders change priorities without explaining the logic behind the decision.
- The team cannot see which tasks have a stronger impact on customers, risks, or company goals.
- The backlog keeps growing, but old ideas are rarely removed or deliberately deferred.
How to start
- 1 Choose one list of initiatives or tasks where there is currently the most disagreement about priorities.
- 2 For each task, describe the value, urgency, risk, and approximate effort size using simple categories.
- 3 Sort the tasks using MoSCoW so you clearly identify what is must-have, important, desirable, and deferred.
- 4 Compare the top tasks using WSJF and discuss only major differences in the evaluations.
- 5 Record the final order and the reason for the choice next to the tasks so you do not have to return to the same argument again.
Expected effect
The team gets a shared language for choosing tasks and can more quickly explain why some initiatives come before others. It becomes easier for the manager to say no to work or postpone it, because the decision is based on agreed criteria rather than personal preferences.
Common pitfalls
- The team turns evaluation into heavy math and spends more time on scores than on making the decision.
- Almost everything ends up on the must-have list, so MoSCoW stops helping with prioritization.
- One person assigns the evaluations without discussing them with the people who understand customers, risks, and the complexity of the work.
- Priorities are set once and not reviewed when goals, deadlines, or constraints change.
- The method is used instead of strategy: it helps choose the order, but it does not answer which goals matter most for the business.
Further reading
- Book: Don Reinertsen, The Principles of Product Development Flow
- Documentation: Scaled Agile Framework, Weighted Shortest Job First section
- Documentation: DSDM Agile Project Framework, MoSCoW Prioritisation section
FAQ
Who should own this practice?
Usually, this practice is started by the team manager, the product owner, or the backlog owner. It is important that the discussion includes people who understand customer value, risks, and the real complexity of delivery.
Can you start without a consultant?
Yes. To get started, it is enough to take one disputed task list, agree on simple criteria, and run a short evaluation session. It is better to add complex formulas only when the team already understands what the criteria mean.
How can you tell whether the method is working?
After the discussion, the team can explain the task order using the same language. There are fewer repeated arguments about old decisions, and new urgent requests are compared against the priorities already chosen.
What should you do if participants disagree with the evaluations?
Focus only on major differences: where people see value, risk, urgency, or effort size differently. The goal is not precise scores, but to surface different assumptions and make a clear decision.