2.0.0.1 Burndown Chart Questions
Here's some text from a user concerning the burndown chart. I was
wondering if anyone from the reports team could share some insight into
the current workings of the chart.
Questions from user:
I've pasted the burdown for my current iteration. As you can see, the
red line goes from the most recent blue dot to 0. This conveys the
message that the remaining work must travel the red line to be on track.
However, I believe the red line (expected complete) should go from the
Y-axis to 0. The starting point on the Y-axis would be the total hours
defined for the tasks in the iteration (just above 1100 here). The
starting point might change as the total hours change (altering the
slope), but at least it reflects the "expected complete" line across the
full iteration. Essentialy, this red line would be the same as the red
line in the burnup report, just going in a different direction. Note
also (as I suggested at the tail end of my original writeup) that the
red line perhaps should not automatically adjust, but be up to the
product owner to "reset" should a new baseline expected complete be
desired.
The burndown chart referenced in the questions above has been attached.
Thank you,
-Garrett Rolfs
wondering if anyone from the reports team could share some insight into
the current workings of the chart.
Questions from user:
I've pasted the burdown for my current iteration. As you can see, the
red line goes from the most recent blue dot to 0. This conveys the
message that the remaining work must travel the red line to be on track.
However, I believe the red line (expected complete) should go from the
Y-axis to 0. The starting point on the Y-axis would be the total hours
defined for the tasks in the iteration (just above 1100 here). The
starting point might change as the total hours change (altering the
slope), but at least it reflects the "expected complete" line across the
full iteration. Essentialy, this red line would be the same as the red
line in the burnup report, just going in a different direction. Note
also (as I suggested at the tail end of my original writeup) that the
red line perhaps should not automatically adjust, but be up to the
product owner to "reset" should a new baseline expected complete be
desired.
The burndown chart referenced in the questions above has been attached.
Thank you,
-Garrett Rolfs
12 answers
Hello All,
I am trying to understand the calculations of the ideal line in the burndown chart in rtc 3.x. If I create the chart, but have no work items created at the beginning of the sprint, the ideal line starts at zero at time zero and ends at zero at sprint end, then after the first day, we add in 30 work items for the sprint, but the ideal line does recalculate. The planned work and the actual work show the new work items. I understand that the ideal line is just a straight slope from beginning to end, but it has to take into account the added work items, not just start from the initial value, in this case zero, so the report is flatline for the entire sprint, not very useful. If I add, 50 work items in day three of the sprint and it never recalculates the ideal line, then again not very useful. Maybe I am misreading the intent of this chart.
thank you,
Brad
Hello,
We are experiencing the same ideal line issue as in the last post. The ideal line does not recalculate if we add additional work items after the first day of the iteration. We are currently on RTC 3.0 iFix1.
Is there a fix for this?
thank you, Angelo
By a mistake we have assigned over two years of 'estimated time' to a workitem. This was easy to edit in the workitem when we spotted that. The problem is with the burndown chart. It picked up this value and now on the chart is impossible to read since that estimated time scales the Y-axis to 2 years. Any remaining work is almost close to zero on that chart.
Is there a way to correct/erase historical data on the burndown chart?
I've already tried setting the sprint to start beyond the point where 2 years estimation was still in the DB, but the chart does not react to that.
Is there a way to correct/erase historical data on the burndown chart?
I've already tried setting the sprint to start beyond the point where 2 years estimation was still in the DB, but the chart does not react to that.
page 2of 1 pagesof 2 pages