Free BA tool
MoSCoW prioritisation tool
List your requirements, sort them into Must, Should, Could and Won't have, and check whether your Must list is realistic.
MoSCoW is a prioritisation technique from the DSDM agile framework. Each requirement is placed in one of four groups: Must have (the release fails without it), Should have (important, but there is a workaround), Could have (nice to have if time allows) and Won't have this time (agreed to be out of scope for now).
The most common mistake is marking almost everything as Must. DSDM suggests keeping Must Haves to no more than about 60% of the effort, so the Should and Could items leave room to absorb problems without missing the deadline. This tool counts your priorities and warns you when Must goes above that level.
How to use it
- Paste or type your requirements, one per line, and press Add to the list.
- Choose a priority for each requirement. Optionally add an effort estimate in any unit your team uses, such as story points or days.
- Read the summary. If Must is above about 60% of the planned work, challenge each Must: would you really cancel the release without it?
- Download the result as Markdown or CSV for a spreadsheet, or copy it into your notes.
MoSCoW prioritisation tool
Private by design. What you type stays in your browser. Nothing is sent to BA Mentorship. Nothing is saved either: copy or download your work before you close the tab.
| Requirement | Priority | Effort (optional) | Remove |
|---|---|---|---|
| No requirements yet. Add some above. | |||
Summary
- 0Must have
- 0Should have
- 0Could have
- 0Won't have (this time)
Questions and explanations
How do I decide between Must and Should?
Ask what happens if the requirement is missing on release day. If the release would be illegal, unsafe or pointless without it, it is a Must. If it would be painful but there is a workaround, such as a manual process for a few weeks, it is a Should.
Why does the tool warn above 60%?
The 60% level follows guidance from DSDM, the framework MoSCoW comes from. When Must Haves take up most of the effort, any surprise puts the whole release at risk because there is nothing lower-priority to drop. The tool counts items unless you give every planned item an effort estimate, so treat the percentage as a rough signal, not a rule.
What is the point of Won't have?
Writing down what is out of scope for this release stops the same ideas returning in every meeting and makes expectations clear. "Won't have this time" is not "never": these items are often the first candidates for the next release.
Is MoSCoW the only way to prioritise?
No. Teams also use value versus effort, weighted scoring, Kano analysis or simple ranking. MoSCoW works well when you have a fixed deadline and need agreement on what can move. Whatever method you use, record the reason for each priority so it can be revisited.
Is my list stored?
No. The list exists only in this browser tab. It is gone when you close or reload the page, so export it first.
These tools are free practice aids from BA Mentorship. They use simple, transparent rules, not AI, and they do not assess or certify your work. BA Mentorship is not affiliated with IIBA, PMI or IREB.