You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Please help me to understand the use of Jira field 'Story Value'. As of now, we use only 'Story Points' to estimate a particular story or task. From a long time I had question about purpose and use of field 'Story value'. I tried to find on multiple sources including here in atlassian community, but no concrete info was available. If any of you have used this field or knows its use, please share some knowledge and help me to understand this difference of terms.
@Nic Brough -Adaptavist-already gave the technically correct answer. I can only offer an educated guess. Product owners like to estimate both costs and benefits. This way they can prioritise stories / issues. Story Points are typically used to express the complexity / cost of an issue. Your Story Value field may have been added for the expected benefit of a story.
Thanks @HansCronau and @Nic Brough -Adaptavist-
I was also thinking on the same lines. If whatever we are thinking is correct, so can we conclude that Story Points are given by Developers for the cost/complexity related estimation and
Story Value is given by Product Owner for benefit from PBI related estimation.
So my next question is how product owner will decide a number for Story Value?
Have you tried any way to put a value on PBI from POs perspective?
I've seen that done in lots of different ways. It tends to work very differently in places - small places with highly focussed teams and large corporates with many interacting components, it's very differnt ways needed to score values.
All I can really tell you is to get your POs to work together so that they all understand and use Story Value in the same way. I don't know if your developers need to care about it either - again, some places might, others just say "the PO has used it to help prioritise the backlog with us, but we don't need to know how"