Agile coaches teach teams to develop a  business value that is delivered at the end of the sprint.

But should be a value an indicator of the priority? Yes, but not the only one. There are many other attributes we often forget to consider.

We suggest applying a different approach. We would like to have a possibility to calculate priority according to business value but considering risk and effort as well. This way we can have the priority more precise, not just guess.

scrumdesk agile prioritization priority risk effort business value scrum agile product owner

Product owners often see the only positive business value. It is a value a company will gain if the story is delivered. But there is the negative value that drags your revenue down. An example of such negative value is nonlogical login during pages transitions.

Risk should be not forgotten.  You can see risk management done in different ways. From High->Low or as numbered risk level. The more risky story, the higher priority.

Dependencies is a number of relationships to other stories. The more dependencies the higher priority as the problem seems to be more complex.

Effort makes priority non-linear. What is smaller it can be done sooner as it is much more precisely estimable. Big stories are typically epics that must be detailed hence they are not good for the implementation.

scrumdesk windows user story Priority, Risk, Effort, Business Value, Dependencies

ScrumDesk uses this approach after consultations with our top customers. We learned to apply this way in our backlog. It provides us validation of our priority feeling comparing to the calculation.

It is very easy to accept proposed priority by clicking  Set to importance.