Delivery Progress - Not Based on Story Points?!

[Matt Richards]

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? 

[Rohan Swami · Accepted solution]

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!

[Matt Richards]

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

[Matt Richards]

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

[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.

[Valentina Migliore]

@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.

[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!

[Matt Richards]

venvee.atlassian.net

[John Karas]

knack.atlassian.net

[jack_saxton]

hudl-jira.atlassian.net

[Rohan Swami]

We've turned it on for you @Matt Richards @John Karas @jack_saxton ! Please share your feedback and any bugs you find.

[jack_saxton]

@Rohan Swami I've cleared my cache and I'm still not seeing it available like you've posted in the image. Is it somewhere else or am I missing something? 😅

[Claudia Fox]

@Rohan Swami please can you add us too?

midnightco.atlassian.net

[Rohan Swami]

@jack_saxton You'll need to hover here to switch from Issue Count to Story Points. If that doesn't work for you please ping me at rswami @ atlassian dot com

[jack_saxton]

This confirms that I was at least in the right place, but I don't have the same option that you're showing in that image. 😅 This is what I see in that area.

[Rohan Swami]

@jack_saxton could you try again please? We had a minor issue turning the feature flag on for your site.

[Claudia Fox]

@Rohan Swami I'm also not seeing the change on our site? Thanks

[Rohan Swami]

@Claudia Fox @jack_saxton we had an issue with the feature flags. It should be working for everyone now.

[Alon Gvili]

https://akeyless.atlassian.net/

[Marina Rambo]

Can we please be included!  So exciting and just what we were looking for. https://servicecore.atlassian.net/

[Ruby Gonzales]

cloudcfo.atlassian.net

[Sybren van Putten]

@Rohan Swami please add us: marvia.atlassian.net

[Rohan Swami]

@Sybren van Putten we've turned this on for everyone now!

[Kim Alders]

I read somewhere that "Currently story point estimates are only supported in company-managed projects. " Is this still the case?

[Bill Sheboy]

Hi @Kim Alders 

Unfortunately, there are two story point fields in Jira Cloud, which may be displayed by their specific name or generically as "story points" in the UX:

• For company-manage projects, the field is "Story points"
• For team-managed projects, the field is "Story point estimate"

Kind regards,
Bill

[Kim Alders]

Thank you @Bill Sheboy 

I think that means that for team-managed projects this option 'story points' is not available, bcs teammanaged projects use story points estimate instead of story points?

Best wishes, Kim

[Bill Sheboy]

Correct: I tested and this appears not to work for linked, team-managed project (TMP) ideas.  I recommend submitting a defect (or feedback) for it to the Atlassian team:

GIVEN a JPD idea exists
AND it has linked delivery issues in a team-managed project
AND the delivery issues have values for the "Story point estimate" field
WHEN the delivery progress calculation is configured to use "Story Points"
THEN the delivery progress uses the "Story point estimate" field

The progress feature could dynamically select the correct field value based on the project type of the linked issues.

A possible workaround is using a global (or multiple-project) scope automation rule to set a custom field in the JPD project for the percentage complete, based on the linked issues and regardless of project type.

[Kim Alders]

Thank you, I will do both :D

Submit a defect and try to get to the workaround.

[Huỳnh Thiên Phước]

Hi @Rohan Swami, I already enable in Project discovery project -> delivery session -> configure delivery progress > switch to Story point 

try to link story points but dont have any display. Can you help?

[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! 

[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]

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. 

[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?