Looking for best practices on "quantifying" the business value of a story, if there are any.
Thank you Thomas. I've been doing some research in the meantime and have found much information. As you suggest above, ESTIMATING the biz value in planning is the way to go - focusing on ensuring the estimates are relative (a "2" really is twice as valuable as a "1").
Just an idea - you can use labels for that. E.g. create some custom scoring system and add labels e.g. Business Value 1 - BS1, BS2 and so on.
We keep a simple table which lists the features to be implemented in the next release. The features are ordered by Business Value, which is 1 to n.
Features are built, according to this Business Value prioritisation.
How you determine the '1 to n' business value ordering is art, science and a bit of magic ;-)
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Apply agile practices
Transform how you manage your work with agile practices, including kanban and scrum frameworks.
Learning Path
Configure agile boards for Jira projects
Learn how to create and configure agile Jira boards so you can plan, prioritize, and estimate upcoming work.
Jira Essentials with Agile Mindset
Suitable for beginners, this live instructor-led full-day course will set up your whole team to understand how to use Jira with an agile methodology.