This article serves to provide more details to the Basic Burndown article here:  http://help.scrumdo.com/reports-and-dashboards/burndown-basics

Hours Burndown Report

Original Hours: These are the estimated hours of a card itself, so this doesn’t include estimate from its Tasks or child Cards.

Total Hours: These hours depends on the workspace’s “Time Based Estimate” settings seen above.

 so, as per this setting :

Total Hours =Card’s Estimated time + Estimated time of all Tasks in it+ Estimated time of it’s all child cards 

(again estimated time of a child card also depends on its workspace settings i.e – based on setting that can include their’s Tasks/Child cards)

Reported Hours: These include the sum of hours added by users on the card, its tasks or child cards based on the setting above.

Completed Hours: This will be count same as Total Hours above but only for Cards/Child cards/Tasks in done state.

Remaining Hours: These hours depends on the Workspace’s “Time Based Estimate” settings as shown below.

so, as per this setting:

Remaining Hours = Total Hours – Reported Hours

if second option is selected (below)

Ideal Burndown

 

Ideal Burndown shows the completion date of a specific Iteration/Sprint based on the Total Hours and Capacity allocation for that Iteration/Sprint.

How do we calculate the projected completion date for an Iteration?

Total effort = Total Hours of an Iteration

Total Capacity = Capacity allocated for that Iteration

Projected completion days = Total hours/Total capacity a day

Capacity Allocation

We can allocate capacity to an Iteration/Sprint from iteration settings.

 

So the total capacity of an iteration will be calculated based on the workspace’s “Time Based Estimate

so as per above setting 100% capacity of a team member will be counted as 8 hours a day. If 6 members are allocated with 100% capacity to an iteration then total available capacity is 6*8=48 hours/day.

Did this answer your question?