[scrum] Iteration burndown chart shows 'no work items'
I have an iteration burndown which is a bit strange, claiming no work items found for the chart.
The product backlog (iteration plan) has a number of stories. One story has several tasks, and these tasks are "planned for" the iteration in question. The tasks are complete, and the iteration plan progress bar shows completed work. I suspect that because the story (parent) is assigned to the product backlog iteration plan, and the tasks (children) are assigned to the sprint backlog iteration plan, AND that the parent story is still 'open' while the tasks are 'closed' there is some issue with determining the tasks to include in the backlog. Is this a know bug or am I doing something stupid? KB |
One answer
keithbarton wrote:
I have an iteration burndown which is a bit strange, claiming no work I don't think that the problem has to do with the iteration that the story is planned for, nor with the parent story still being open. (Both of those should be okay). The burndown report shows the sum of the remaining work (that is, the sum of the estimates of *open* work items, minus the sum of the "time spent" of those same work items). You say your tasks are complete - in this case I wouldn't expect them to show up on the burndown. Did you close them before or after you assigned estimates to them? james Jazz Reports Team Lead |