Daily burn up calculation

In the agile charts, there is an targeted burned up (red line), actual burn up based on closed/resolved issues and their associated story points (green line), and a brown line that is the required daily burn up.

However, I've not had success at getting a good definition as to how the required daily burn up is calculated and am hoping the forum can answer.

Scenario 1:

This is GH's example: https://confluence.atlassian.com/display/GH/Viewing+the+Statistics+Burnup+Chart

The green line shows that all story points planned have been completed - so, the green line has achieved burning 22 UI points and the red line guideline was to burn 22 UI points. By that definition, the required daily burnup to achieve target should be 0 -- I have no more to do. However, the gadget continues to show an increased number of story points required per day such that the brown line meets the red line. I don't know why the brown line doesn't go to 0. It currently shows that 6 UI points per day are required for June 7 through June 11, or 4 days. That means that there are 4*6, or 24 UI points still needed to be complete. However, the guideline indicates only 22 are needed.

Scenario 2: I have 17 days left. I have burned 130 story points and am required to burn 167 story points at the end of 17 days. So, may daily burn rate is (167-130)/17 or 2.18 story points per day. However, may chart is showing a required daily burn of 10 and is projected to be higher.

Why does the daily burn up keep increasing, or higher than the calculation? Why does the required daily burn up, at the end of the release, have to equal the guideline - it is a daily calculation, not a cumulative.

1 answer

1 accepted

Accepted Answer
0 votes

Per Atlassian, this is a bug - it is correct. However, they have not plans to fix since it is a classic board gadget. However, they currently don't have a respective board gadget to use - consequently, am disappointed that they are not fixing issues that are clearly showing and reporting inaccurate data/information without providing any alternative.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published 2 hours ago in Jira Ops

Jira Ops Early Access Program Update #2: Let’s talk severity levels

Welcome to your weekly Jira Ops Early access program update, where we’re sharing news and updates on Jira Ops' progress as we work toward our 1.0 release. If you ever want to drop us feedback or idea...

12 views 0 0
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you