WSJF? Read this short intro. How to do this with Jira, read on.
It took me 1.5 hours to get this working on a fresh Jira Cloud evaluation version. On-premise Jira has a different set of plugins, so a slightly different path is needed. It however is quite simple to get this running – provided you can bribe your Jira admin to install a new plugin 🙂
This is how it works
In the listing
This all was done with the Abacus plugin that allows you to do math based on values “fields”. All of the above is automatically calculated by the Abacus plugin. Any time you change any of the WSJF components, then the calculation is redone automatically.
The summing of Business Value, Risk Reduction/Opportunity Enablement and Time Criticality was the first calculated as the “Calculated total value” column. The WSJF result had also division by job size/duration included.
Pricing of the plugin was IMO bearable. If you need similar with on-premise Jira, then look at JIRA Misc Custom Fields.
So that’s short and sweet, hope this gets you started.
Then I spent a bit more time to visualise this. As usual, to get something you need in Jira, a plugin was again needed. This time it was the easyBI plugin, and that gave me a nice bubble chart of how the items relate to value vs size.
anttitevanlinna's blog 
How do you handle invalidation of this data as (“vanilla”) WSJF only applies relative to the set the comparison was done across?
I’ve been thinking this too, but as long as the data is not normalized (and even if it is, anything regarding time criticality for example) gets more and more out of date as the time passes and you’ll be left with invalid data that seems to be good for comparison in JIRA (no way to determine, risk of misinterpretation is there)
This suggestion has come across several times in our company as well, I thought of it too but it is not as straightforward as it sounds like. I do agree that implementing something like this is rather easy, while living with the implementation might not be so.
Hi Janne, You are indeed right about the data maintenance. IMO this is very similar to what’s happening with story points too. They get stale as time passes. People change, context changes. You forget how did you ever come up with the number. On top of that, WSJF has 4 components, which in practice is a lot to assign and maintain.
Just fyi, there is a dedicated Jira plugin for this now: https://marketplace.atlassian.com/apps/1221306
Finally 🙂 Thanks for the tip.