It's all about the answers!

Ask a question

Advance Release Burndown and Release Burndown show different Total Points?

Lora Estey (7331920) | asked Apr 09 '13, 11:22 a.m.
I like to use these two graphs together. The Advanced Release burndown is somewhat normalized where it could be misleading to look like everything was estimated at the beginning of the release, where the Release Bundown is great at showing that work may not have been estimated, but it is hard to see the work that was done. 

However it is really annoying that their total points differ. They don't differ by that much but enough to make people not trust either widget.

Why are they different? Does one do the right thing and ignore invalid stories while another doesn't????

2 answers

permanent link
Kevin Ramer (4.5k9185201) | answered Apr 09 '13, 12:02 p.m.
We're finding several things can affect the Advanced Release burn-down here a few:

  • The failure to determine "current iteration" properly.  Cause: default identifier of Main Development time line. Fix: Change the identifier using RTC Eclipse client
  • Customization of Story Points (complexity) enumeration can introduce non-integer values into the database.  Have a look at complexity configuration (again in RTC Eclipse).  Look at the Process Configuration Source. If there are entries that look like  <literal id="complexity.literal.l10" name = "32 pts"> while others look like <literal id="12" name="12 pts"> this may be affecting your graphs
  • If priority has been customized it can elide some priorities if the number of priority entries is much more than 4 or 5

Lora Estey commented Apr 09 '13, 12:22 p.m.

Thank you Kevin

  • In the Settings for both of these, we aren't using the 'Current Iteration' option . We are manually selecting the specific Release Iteration and all of the child sprint iterations.
  • We have not customized the Story Points or Complexity at all.
  • We added 2 priorities - Medium High and Medium Low... are you saying that the Advanced Release Burndown is not including any Stories with those priorities?
I'm assuming that this has to do with the Priorities... How would we go about verifying this AND fixing it? 

Lora Estey commented Apr 09 '13, 1:34 p.m.

 I have another thought. If some of the Stories have priority as Unassigned... would this not show up in the Advanced Burndown?

Kevin Ramer commented Apr 09 '13, 1:52 p.m.

This discussion has more detail.

The long and short of it: only high, medium, low and "everything else" for advanced burndown.  The ID of priority must sort "High" > "Low".

permanent link
Alanna Zito (1.3k3) | answered Apr 09 '13, 2:50 p.m.
Hi Lora,

Another factor that could cause differences between the Advanced Release Burndown report and the Release Burndown report is that the Advanced report uses live data while the simple report uses data from the data warehouse.  The Advanced Release Burndown report determines which story points belong to which iteration based on the (current) value of the "Planned for" attribute of the story.  The Release Burndown report uses the data warehouse, so it displays story points based on the values from history.  If the planned iteration for some stories was changed at some point, that would probably cause slightly different totals in the two reports.

KrishnaKanth Naik commented Aug 18 '15, 8:50 a.m.

Hello Alanna

Has the above description for "release burndown" and "Advanced Release Burndown" changed in 6.0. I am asking this because, both the reports mention that they work on datawarehouse.

I have not yet configured DCC on this server, and just tried to look up the behavior with the Report description on what the report description would show up with no data and I see the following for both the reports:

KrishnaKanth Naik commented Aug 18 '15, 8:51 a.m.

Why did this happen?

This report presents historical data from the data warehouse. This data is collected by automated data collection jobs. It is possible that this chart is empty because these jobs have not had a chance to run yet.

Your answer

Register or to post 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.