Why is magnitude of progress (burndown) out of line with plan estimates ?
This is rather like :
https://jazz.net/forum/questions/84195/difference-between-planned-work-at-rtc-progress-bar-and-burndown-graph
Burndown graph runs up values in the 2-3K range, but the estimates on the same team's sprint plan are in the 300 of 600 hours kind of magnitude. I did find:
https://jazz.net/forum/questions/96755/burndown-report-in-rtc-is-not-getting-properly
whose last entry says watch for possibility of change in work item type with vestigial estimate attributes.
Using the Iteration report in RRDI looks to be spot-on, but we've not given RRDI over to the community just yet.
https://jazz.net/forum/questions/84195/difference-between-planned-work-at-rtc-progress-bar-and-burndown-graph
Burndown graph runs up values in the 2-3K range, but the estimates on the same team's sprint plan are in the 300 of 600 hours kind of magnitude. I did find:
https://jazz.net/forum/questions/96755/burndown-report-in-rtc-is-not-getting-properly
whose last entry says watch for possibility of change in work item type with vestigial estimate attributes.
Using the Iteration report in RRDI looks to be spot-on, but we've not given RRDI over to the community just yet.