Sprint Insights Calculation
Asked by John Viall:

Google failed me in my search. but here goes.

When I look at the sprint insights to a particular sprint, it provides the following screen. When I hover over it, it gives me a list of tickets. These tickets were never removed or added to the sprint, after the start of the sprint. They were planned work.

So my question would be, what are these numbers trying to inform me of? One ticket did decrease points by 1. But that still doesn't account for the other 3. And the tickets listed under Added are the same tickets listed under Removed.

And just because I'm here, what would Modified be calculating?

As of now, I don't understand how to interpret this data to help the team make improvements.

Thanks,

John

![JIRA Insights.png](https://community.atlassian.com/t5/image/serverpage/image-id/337976i80D022B2366F7FAF/image-size/large?v=v2&px=999 "JIRA Insights.png")


Answers:
author: Valerie Knapp
body: Hi [@John Viall](/t5/user/viewprofilepage/user-id/5548032) , welcome to the Atlassian Community and thanks for your question.

Generally, in the Sprint context, the points being referred to here would be Story Points, which are used to estimate the effort required to complete individual pieces of work.

I agree in the report you are seeing that it is confusing because you could have a situation where you keep the same number of issues, but just the estimate or the Story Points values have been modified.

Are you using an app for this report? I wasn't able to reproduce this screen. Please let us know how you obtained this view and I can try to understand what is going on.

Cheers

comments: author: John Viall
body: On a sprint board, there is an Insights button. See attached screenshot. Click on that, and in our current environment, we have to select the Sprint (we have multiple teams working out of a single backlog). and then you can scroll down to get the screenshot I sent earlier.![Sprint Insights.png](https://community.atlassian.com/t5/image/serverpage/image-id/337981i00D1E32829F7C61A/image-size/large?v=v2&px=999 "Sprint Insights.png")


author: Valerie Knapp
body: Hi [@John Viall](/t5/user/viewprofilepage/user-id/5548032) , thanks for your help.

Ok, I have done some tests in my demo instance and produced this result -

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/337988i34AD048A7986763C/image-size/large?v=v2&px=999 "image.png")

Added was achieved by adding a Story to the current Sprint with 1 Story Point

Removed was achieved by removing a Story from the current Sprint with 2 Story Points

Modified was achieved by modifying the Story Point values in Stories already in this Sprint

Does that help you at all? You can also click through to see the issues being counted.

I guess this is not such a new feature (whoops) - <https://community.atlassian.com/t5/Jira-articles/Introducing-the-burndown-insight-for-Jira-Software-Cloud/ba-p/1977540>

but you could also try commenting in that article or mentioning the author at Atlassian for more context or help.

Good luck!


author: John Viall
body: Thank you, and that is what I would have expected. However, that is what I'm seeing.

The tickets listed as added, were added at Sprint Planning, before starting the Sprint.

The tickets listed as removed, were never removed from the Sprint.

One ticket did get a point adjustment, and that isn't even captured.

That is what started me down questioning how it is being calculated?? I don't know what or which event is triggering the counts to change.

Thank you for trying to figure this out. I just know at some point, someone is going to question it, and I would like to have an answer.


Tags: cloud

jira-cloud