Advanced Release Burndown showing empty future iterations as though they are full..
I have a release that has 7 sprints under it.
We are in in the 3rd sprint with 4 future sprints... however there are 4 future sprints that are the same height as the one that we are currently working on rather than at the zero point. So it doesn't look like a burn down, since all future sprints have the bars at the exact same height as the current sprint.
- NONE of these iterations are marked 'Current Iteration'.
- There are zero work items planned for any of these future sprints.
- We have created plans for all of the future sprint iterations and they are each of type "Sprint"
|
One answer
Hi Lora,
The description for the Advanced Release Burndown is the following:
This report visualized the remaining story points at the beginning of each iteration in a release. Each dot represents the start of one iteration, and the height of the line represents the total of all story points in open story work items. It is important to note that each dot includes work items planned for any of the iterations, not just the iteration that is beginning - thus the value represents the amount of work remaining in the release, not just one iteration.
An ideal line is plotted to indicate how much work 'should' be done in each iteration to complete all complexity points by the end of the release - as identified by the end date of the 'release' iteration.
The prediction lines are plotted for the current and all future iterations by calculating the optimistic (average of best three iteration velocities from last six iterations), best guess (average of most recent three velocities) and pessimistic (average of worst three iteration velocities from last six iterations).
My guess is that you have work items that aren't planned for any of your iterations, so you are seeing that work displayed in all of your iterations including the future ones. Comments We have other Release iteration in the same timeline (this would be the release that has a sprint marked as the 'current iteration) that does not look like this or behave like this.
This is where things are confusing, why does it look one way for one release and another way for another release....
Hi Lora,
@loraestey Have you worked this out yet? Is there someway we can still help? |
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.