What's behind report calculations
I'm continually asked to explain how RTC arrives at the data displayed on reports. I need more infomation than what's available in "What does this report tell me". Does anyone know of an article that would help explain.
|
4 answers
I'm continually asked to explain how RTC arrives at the data displayed on reports. I need more infomation than what's available in "What does this report tell me". Does anyone know of an article that would help explain. Hi Linda, We're currently working on improving this information for our 2012 release. Right now, the information we have is in our wiki here: https://jazz.net/wiki/bin/view/Main/CALMReportingOOTBReports We're working on adding information about where the report gets its data, and specifically what kind of process dependencies there are (i.e. what kind of artifacts you need to have to see data in the report, and how it's affected by process customizations). In parallel, we're working on pulling this data into the InfoCenter - it will be there in upcoming releases. In the mean time, if you have any specific questions about reports in RTC, please feel free to post them here, or to open work items in RTC/Reports with your questions. james RTC Reports Team Lead |
James,
Please can you let me know the calculations behind the release burndown report. For some reason I can't seem to get this to work. I have a release plan and am able to report sprint burndowns OK. Thanks Steve |
James, I've a question about the Ehanced/Advance Release Burndowns: Customer thinks that because Release + its iterations doesn't show bar at the last few iterations (e.g. most recently finished and following) that it's broken due to recent upgrade. The report gives the last snapshot date as today.
E.g. Sprint 10 onwards don't have Actual Velocity and Points Remaining. Other reports e.g. Story Points do pick up the points for Sprints 10-14. This data is almost identical between Enhanced and Advanced Burndown reports. I seem to recall having observed this in RTC 2. Is this the proper result ? I do see one troubling item in the reports: In the Burndown using similar selection for iterations, Planned work is steadily increasing since May 2011 and gets to about 20,000, then after Nov 2 tick a straight up jump to 58,225 ! Kevin |
James, I've a question about the Ehanced/Advance Release Burndowns: Customer thinks that because Release + its iterations doesn't show bar at the last few iterations (e.g. most recently finished and following) that it's broken due to recent upgrade. The report gives the last snapshot date as today.
E.g. Sprint 10 onwards don't have Actual Velocity and Points Remaining. Other reports e.g. Story Points do pick up the points for Sprints 10-14. This data is almost identical between Enhanced and Advanced Burndown reports. I seem to recall having observed this in RTC 2. Is this the proper result ? I do see one troubling item in the reports: In the Burndown using similar selection for iterations, Planned work is steadily increasing since May 2011 and gets to about 20,000, then after Nov 2 tick a straight up jump to 58,225 ! Kevin As a follow-up I looked at the report design file and saw many for loops that test for 'currentIteration' and break when that condition is found. Coincidentally, the Sprint 10 above is set as the current iteration. I returned the issue as "working as designed" with the suggestion of updating the current iteration in the process configuration. |
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.