Burndown for past iterations
We have one month sprints and at the beginning of the sprint the user stories were added to Sprint Backlog. However, there are two problems, not all stories were tasked out and estimate of hours provided. Since the users in our company are new to RTC, they have not been updating the time remaining field on the tasks regularly.
We are at the end of the Sorint and if we mark the tasks complete now, the burndown chart looks wierd - the line graph shoots straight down instead of a smooth sloping line. I understand this is expected behaviour but I was to know if there is any way I can update the data warehouse history fields to show that the "time remaining" field on the tasks was changed on a regular basis rather than one day.....so in short I want to update the modified date....can anyone tell me how I can do that? Also, is there any Wiki page that describes exactly how the burndown is being calculated. There are other burndowns that look wierd too. Thanks --Sheetal |
5 answers
On 2/12/2010 8:08 AM, sheetal.desai wrote:
We have one month sprints and at the beginning of the sprint the user Sorry, you can't change the data warehouse history after the fact. A work item can have an estimate, and optionally a corrected estimate as well. The burndown report shows the sum of all of the estimates or corrected estimates (corrected is used if supplied, otherwise estimate is used) for all work items which are in an open state, and which are planned for one of the selected iterations. Story points are not included in a burndown report. The "What does this report tell me" text at the bottom might help as well. james RTC Reports Team Lead |
|
Thank you for your response!
Can you also explain how RTC calculate the work remaining each day? Does the state of the record have anything to do with the calculation? No able to change historic information is going to be an issue. Can we change it through API or changing the values in the underlying tables? |
Geoffrey Clemm (30.1k●3●30●35)
| answered Feb 12 '10, 12:23 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
WRT the state of the record and the remaining work, work item 103407
requests that the work remaining automatically go to zero when the work item is marked as done. Please feel free to add your comments/support to that work item if that functionality is important to you. Cheers, Geoff sheetal.desai wrote: Thank you for your response! |
|
Thanks Geoff! I am fine with the fact that the time remaining is marked 0 on completion of the record.
I still want some explanation to understand how the burndown charts are being calculated. Can anyone point me in the right direction where this is explained in detail. There seems to be some corelation of when the snapshot is run. |
A Work Item has Time Estimate and a Time Spent values, The Time remaining is Time Estimate minus Time spent.
The Corrected Estimate value will replace the Time Estimate value if specified. The Work Remaining is the summation of all Time remaining values for the still open work items. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.