Advance Release Burndown and Release Burndown show different Total Points?
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
Lora,
We're finding several things can affect the Advanced Release burn-down here a few:
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
Comments
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.
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.
Comments
