Is it necessary to use a special hieraki in iterations, for burn down chart to work? Right now, I've defined a single child node named 'Sprint 1' and assigned a bunch of PBO, PSI, but the burndown chart is empty. So is the burndown chart generated by SSRS. Do I need to have some kind of predetermined hieraki to make this work?
Current:
ProjectName
- Sprint 1
Is it necessary to build it like this?:
ProjectName
- Release 1
-- Sprint 1
Help get this topic noticed by sharing it on
Twitter,
Facebook, or email.
Twitter,
Facebook, or email.
-
The burndown chart in Urban Turtle only requires that you have set start and end dates on the Sprint work item that is associated with the currently selected iteration. You can quickly access this work item by clicking on the "i" icon at the right of the iteration in the iteration side-panel.
The burndown calculates the sum of work remaining for each date contained within the start and end dates. For the Scrum 1.0 process template, this corresponds to the Remaining Work field of the Task work item type. -
-
I suspect it might be due to slow sampling rate - how often is the value calculated?
-
-
The burndown in Urban Turtle is real-time. It is calculated each time you open it. It must not be confused with the reports generated through SSRS. These are not real-time.
-
-
-
Loading Profile...




