Classify request based on cost, benefit and risk

[Christian Gertsch]

Hi Community

We are setting up Jira Service Desk for collecting requests for our products. Mainly, these are change requests, for example, change a material or add a feature.

All these requests are collected within Jira Service Desk. Every other week four persons from the core team are sitting together and estimate the importancy of the request. The estimation is based on cost, benefit and risk of implementing the request. 

My question: Does anybody has experience in implementing such an estimation? How are you doing that?

I wonder if there is maybe a better solution than just add custom fields with free text. (Maybe a scroll bar, graphics, calculator?)

Thanks for your inputs!

Christian

[Simon H]

You might like to consider the Marketplace App Prioritizr. We have used it do what you are describing and it has good dashboard/visualisation of issues.

They also support two prioritisation frameworks, with more to come, or you can customise it yourself.

• Design Thinking: Desirability, Viability and Feasibility  
• Product: Reach, Impact, Confidence, Effort (RICE)

[Christian Gertsch]

Thanks for your input! Unfortunately, we are using JSD Server, thus we are not able to install it.