What kind of impacts affect the sprint burn-down diagram?

[kevin_thomas]

or simply asked: why does our diagram look the way it does?

what could be the reason we are so far from the guideline?

[Marc - Devoteam · Accepted solution]

Hi @kevin_thomas 

This means most of the issues in the sprint are not "done" and so the estimates set on the issues are not considered burned.

The re line is the total sum of all estimations of all issues, this line will go down if items in the sprint are burned. 

The green line is the opposite, this will get higher when issues inthe sprint are burned.

[Mikael Sandberg · Accepted solution]

The reason why you have a big gap between the guideline and the remaining values is that remaining values are not decreased until the work item reaches the far most column on your board. That column tells Jira that the work item is considered done. 

[kevin_thomas]

thx, to be honest, the graphic makes little sense as soon as you work with several statuses and processes are regularly not completed in one sprint and therefore have to move to the next sprint