Prioritisation
Paste your backlog or pull it from Jira and get it ranked, with the scoring method chosen to suit what you actually have, every number explained, and the written argument for the order. One pass over the whole list rather than a scoring session per item.
- Asks for
- Your tickets — pasted, or from a connected Jira project
- What you are optimising for this quarter
- Any numbers you have: reach, revenue, effort estimates
- Gives back
- The method chosen for what you have, and why that one
- The whole list ranked in one consistent pass
- Every score with the reasoning behind it
- The argument for the order, written, and what a better method would need
- Plan
- Free
- Use next
- Roadmap, Capacity planner, Feedback synthesis, OKRs
What it gives you
Method: RICE. You have reach figures for 9 of 12 items and effort for all 12. For the 3 without reach, value-vs-effort is used and they are marked. 1 CSV import R 1,400 I 2 C 80% E 3 = 747 Reach: trials that stalled at an empty backlog, Sep–Oct. 2 Rank on import R 1,400 I 1.5 C 80% E 1 = 1,680 … held at 2 Scores higher but depends on #1. Order forced by the dependency. To use WSJF instead: job sizes for all 12, which you do not have.
How it works
Prioritisation frameworks are not the hard part; picking the wrong one is. RICE needs reach numbers you may not have, WSJF needs a shared sense of job size, MoSCoW is for a fixed deadline, value against effort is for when you have neither. Teams usually pick whichever one they have heard of, then invent the inputs it demands.
So this picks the method from what your items actually contain, says why, and tells you what it would need to use a stronger one. Then it scores the whole list in one pass — which matters because scoring consistency is the thing humans are worst at: an item scored on Tuesday and one scored on Thursday are not comparable, and a backlog scored over two weeks is noise.
Every number comes with the sentence behind it, and the order comes with its argument. That is what survives contact with a stakeholder: nobody argues with a rank, they argue with the reach estimate, and a tool that shows the estimate lets you have that argument in one minute.
Who it is for
A PM with more backlog than quarter who has to defend an order to people who did not score it.
Where it stops
A score is an argument, not an answer: the inputs are estimates and the ranking is only as good as they are. It will also not override a dependency or a commitment — where a lower-scoring item has to come first, it says so and keeps the order rather than pretending the arithmetic decides everything.
Questions people ask
Which prioritisation method should I use?
Whichever one your data can actually support. RICE wants reach numbers; if you are guessing them, the score is a guess with four decimal places. WSJF needs a shared sense of job size across the team. MoSCoW suits a fixed deadline and a scope you can cut. Value against effort is the honest choice when you have neither numbers nor a deadline. This picks from what your items contain and tells you what a stronger method would require.
Why score the whole backlog at once?
Because consistency is the thing people are worst at. An item scored in Tuesday’s refinement and one scored a fortnight later were judged by different moods against different context, and comparing their scores is comparing noise. A single pass over the whole list applies the same standard throughout, which is the only way the resulting order means anything.
Can I override the ranking?
Yes, and you often should. A score does not know about a dependency, a contractual date or the fact that one item is the thing the whole quarter was agreed on. Where a dependency forces an order the ranking already respects it and says so. Beyond that, change it: the value of the output is the explained numbers underneath, which make your override an argument rather than a preference.
Free, and no account needed
These do the arithmetic in your browser. Worth doing first if you want a number before you want a document.
Run it on your own work
Prioritisation needs an account, because it writes against what you give it and remembers what you have told it before. It runs on the Free plan. Or see what the plans cost first.