Prioritise work with MoSCoW and RICE using a service-app example, complete score calculations, sensitivity analysis and practical decision checks.
The lab separates timebox necessity from estimated comparative opportunity. It uses consistent units, a worked three-candidate ranking and a confidence change that alters the order, then checks dependencies and capacity.
Prioritise against an objective
A method helps structure a decision, while the project still needs evidence and authority. An uneven list makes a tidy ranking misleading. A priority applies to a specified commitment or planning period. A Must needs a defensible reason under the agreed objective.
A customer must select a valid available slot for the booking service to work. A preferred screen colour is unlikely to have the same necessity.
Separate Should, Could and Won’t
Useful distinctions make the scope trade-off discussable. Categories do not make the required work fit automatically. Use one consistent basis before multiplying estimates. The arithmetic is simple; the estimates require judgement.
Use the same impact scale across candidates. Intercom’s familiar scale includes 3, 2, 1, 0.5 and 0.25 for successively smaller estimated effects.
Work candidate A
Make each factor understandable before accepting its score. Use a common period, unit and impact scale for the set. A ranking can be fragile when an estimate has weak support. Scores do not automatically provide an executable sequence.
Cancellation needs a shared identity change outside the three scored options. Include that work and its timing before promising the cancellation release.
Use the methods together
Necessity and comparative opportunity can support different parts of the decision. A useful record explains why the team is committing to the work. An agreed order should remain useful as the project learns. Good prioritisation makes a feasible, explainable commitment.
Are dependencies, capacity, risks, overlap and authority addressed? Can the team explain why the selected work best serves the intended result?
Contents
- Prioritise against an objective
- Prepare comparable options
- Set the MoSCoW timebox
- Identify genuine Must Haves
- Separate Should, Could and Won’t
- Check MoSCoW against capacity
- Understand the RICE factors
- Calculate the RICE score
- Work candidate A
- Compare three candidates
- Test confidence and sensitivity
- Account for dependencies and overlap
- Use the methods together
- Record the chosen priority
- Review priorities from new evidence
- Your prioritisation desk check
Using the PDF
Each numbered page contains an explanation, an original worked situation and a practical action. The bookmarks navigate the learning pages. A templates advertisement follows content page 5 and a Coursera Plus advertisement follows content page 15. The entire advertisement image is linked. Promotional links may earn Coursya a commission. A purchase is optional.
Frequently asked questions
Who is this guide for?
Prioritise work with MoSCoW and RICE using a service-app example, complete score calculations, sensitivity analysis and practical decision checks.
How can I practise the ideas?
Follow the running case, work through the page actions and use the PDF bookmarks to revisit a topic. The final learning pages help you apply the decisions to your own project.
What does the download contain?
The PDF contains 19 pages, including 16 numbered learning pages, a cover and two linked advertisements. The book is written in English.


