Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Original Time Estimate not correct on Burndown chart

Douglas LaPointe
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 23, 2019

We add stories to our sprint, add tasks for every story and add a time estimate for every task. When we start the sprint the burndown chart does not show the correct total of estimated hours.

In this example we had 108 hours of estimated time across all of the tasks and the burndown chart started us at about 25 hours. 

image.png

If, and only if, we go into every task and in Time Tracking enter remaining hours equal to the estimate of hours does it seem to update the burndown chart. That is what we did to produce the chart above.

Why doesn't Time Remaining start off being equal to the Time Estimate?

Is there a better way to get the burndown chart to be accurate?

Here is how we are configured for time estimation.

image.png

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events