nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Delivery Progress - Not Based on Story Points?!

Matt Richards_q2q9cg

I feel like this needs more visibility, as it seems like a massive oversight.

Frankly I'm shocked to learn that Delivery Progress is based on the number of issues and not the number of cumulative story points. An Idea that is connected to an Epic with two Issues, one with 1 point and another with 5, is not 50% complete after either of those Issues is Done.

It would seem to me that this should be addressed urgently, as it is a mis-representation of progress.

@Tanguy Crusson - Can you comment on a timeline for a fix here? Or perhaps I am missing something?

Accepted answers

Rohan Swami

Hey folks, what you see in product is a V1 and based on the feedback we've received we're actively working on factoring in Story Points. I'll have more to share when we release but it's not too far away. Sit tight!

All comments

hroy

Agreed-It would be great to have another column for Delivery Progress in Product Discovery to be reflected in Story points-this would be a true way to capture what we would also see in Advanced Roadmaps. Also if we can have Product Discovery Ideas available to be tagged as Parent Link- they would also show up in Advanced Roadmap and provide true connectivity between an Idea and its Delivery Roadmap- any possibility of having that?

Frederik Vantroys

Hi @Matt Richards ,

That all depends on the definition you give to "Story Points"

For me SP = a weigth, a classification (like easy, hard, impssible). When you use it like that (see estimation and planning poker in Scrum for instance) ... you can't just calculate with it. 1SP is not one hour or 1 day of work ... it's just "an easy story to do".

Matt Richards_q2q9cg

I agree that people's definition and use of Story Points varies. Neither Agile nor Scrum define Story Points explicitly, but Atlassian describes it as a "Measurement of complexity and/or size of a requirement" which I think is a fair description.

As is typical of many scrum teams, we use the Fibonacci sequence values to define Story Points (1, 2, 3, 5, 8, 13, 21). The non-linear nature of these values means that we cannot directly tie them to time. Only that a three is loosely three times as much effort as a 1. We consistently emphasize that attempting to tie sizes to time is a bad practice, and we reinforce the idea that sizing is relative.

All that being true, it is our opinion that basing Delivery Progress off of Story Points is a great deal more valuable of a view than is the number of issues. This perspective should not be controversial, as is evidenced by the widespread adoption of views like burn down charts, which use size estimates to understand progress towards completion/delivery.

Nic Brough -Adaptavist-

Story points are an estimation tool, not a progress measurement.

There is nothing to "fix" here, Jira handles story points as estimates, as it should do.

Rohan Swami

Matt Richards_q2q9cg

Thank you for the update, Rohan! AND thank you for watching the forums and engaging with users on their feedback.

John Karas

This would be very helpful to add. Our leadership team and board want to report on Engineering Investment (where is the $ being spent?), and align it to the different buckets of work we do. Epics are the key delivery-groupings, and we relate one/many Epics to one Idea (which lives in JPD)... We want to leverage the story point aspect as a proxy for actual-effort... Looking foward to when this launches!

Matt Richards_q2q9cg

@Rohan Swami - Do you have any updates on ETA here?

Rohan Swami

Hi all, we have an early access program available for calculating delivery progress based on Story Points! If you'd like us to turn it on for you, please comment here with your site URL eg. xyz.atlassian.net

If I've liked your comment, that means we've turned it on for you.

We've turned this on for everyone!

Screenshot 2023-10-30 at 12.19.54 pm.png

Matt Richards_q2q9cg

venvee.atlassian.net

John Karas

knack.atlassian.net

jack_saxton

hudl-jira.atlassian.net

Valentina Migliore_quvlhn

@Rohan Swami I am trying to enable this on my product board but when I select Story Points I end up seeing all at 0. Not sure why it's not capturing the story points at all? Any help would be amazing, thank you!

Rohan Swami

Hi @Valentina Migliore my best guess is that you're trying to connect to Jira issues in a team-managed project. Currently story point estimates are only supported in company-managed projects. You can see your project type in the bottom left corner of the left-nav in Jira Software. If that's not your issue, then please create a bug by selecting 'Give feedback' in the bottom left corner of Jira Product Discovery and we can help you with debugging.

Welcome!

It looks like you're new here. Sign in or register to get started.