Scope change in Burndown vs Issues added to sprint in Sprint Report

[jodywhite]

When I look at a Sprint Report for a finished sprint it shows there are 5 "Issue added to sprint after start time."

But when I look at the Burndown chart for the same sprint, in the data table under the chart, it lists 11 changes to scope where an issue was added.

What is the difference in these and which would I want to use if I were trying to calculate variance (% change of total planned/committed at start of sprint).

[jodywhite · Accepted solution]

I found the discrepancy. On the Burndown report I was focused on looking at the column for issues added to sprint that I missed that the sprint had been accidentally closed and reopened mid sprint so the issues that were still active got "added" to the sprint.

All is well now!

[Alexey Pavlenko _App Developer_]

Hi @jodywhite ,

"Issue added to sprint after start time" - shows only issues added to a sprint after it has started.

The Burndown Chart reflects both issues added to a sprint after it has started and estimate change.

The metric to use depends on your requirements. It can be useful to track both of them.

Best regards,
Alexey

[Danut M [StonikByte]]

Hi @jodywhite,

As @Bill Sheboy  mentioned, some screenshots would be useful to better understand the problem. 

An easy way to display the % Scope Change is to use the Sprint Health Gadget of Jira.

Danut.

[Bill Sheboy]

Hi @jodywhite 

For a question like this, I recommend posting images of the two reports / charts where you have identified differences for the same sprint.  Those will provide context for the community to offer suggestions.

Next, what do you mean by "variance"?  There is a statistics definition of that term, and the equation you show does not align with that. 

Perhaps it will help to know: what symptoms is the team observing and what problem are you trying to solve?

Kind regards,
Bill