I'm trying to work out for the Release Burndown report how the remaining hours are being calculated.
The support article says it's the total work remaining in your backlog and that the report will show data based on the estimation statistic that your board is using. For us its original time estimate. However, I can't line up what is on the backlog with what the report says the remaining hours are.
Does anyone have additional insight into this?
Thank you,
Lisa
Hi @Lisa Gleinzer,
Try also our Great Gadgets app. It offers a Release Burnup Burndown Chart gadget that is highly configurable and allows calculating by time estimates (multiple options are available). This is how it looks like:
This app offers many other gadgets that you will find useful, including Velocity Chart gadget and Sprint Burndown Chart gadget with support for time estimates.
For more details, see article on our blog: Tracking an agile project that uses time estimates with Great Gadgets for Jira
If you have questions, please don't hesitate to contact support@stonikbyte.com.
Thank you,
Danut M.
Hi @Lisa Gleinzer
According to Atlassian’s support page, the release burndown report calculates predicted sprints based on your team’s velocity (amount of work completed in the last three sprints), and the total work remaining in your backlog. Scope change is not considered when calculating the velocity, but is included in the total work remaining.
The burndown chart calculates how many points or issues have been completed, and how many points or issues remain. This makes it easy for you and your team to see how you’re tracking and if necessary, make changes
Here are some articles I found that I think they can help:
https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-release-burndown-report/
https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-burndown-chart/
I hope you find these useful. Best Regard!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for responding. I read the article previously but the issue I'm experiencing is the numbers in the report do not match what is in the backlog, hence I am trying to understand where that report is pulling it's numbers from.
Best,
Lisa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.