Dashboard / Release Burdown
3 answers
On 11/26/2009 11:37 PM, scharffc wrote:
You may have to deploy this report template manually before it appears
in the dashboard.
To do this, open the rich client, go to the Team Artifacts view, and
expand your project area and the Reports node. Right-click on Report
Templates, select Deploy New Templates... and follow the wizard. Be sure
to deploy both "Release Burndown" and "Micro Release Burndown" - the
micro report is the one used in the dashboard.
james
RTC Reports Team Lead
Hi,
There is nothing appearing in my Release Burndown in the dashboard.
Is it normal? With what is it linked?
I however have the Burndown in the Dashboard.
Thanks
Christelle
You may have to deploy this report template manually before it appears
in the dashboard.
To do this, open the rich client, go to the Team Artifacts view, and
expand your project area and the Reports node. Right-click on Report
Templates, select Deploy New Templates... and follow the wizard. Be sure
to deploy both "Release Burndown" and "Micro Release Burndown" - the
micro report is the one used in the dashboard.
james
RTC Reports Team Lead
On 11/26/2009 11:37 PM, scharffc wrote:
Hi,
There is nothing appearing in my Release Burndown in the dashboard.
Is it normal? With what is it linked?
I however have the Burndown in the Dashboard.
Thanks
Christelle
You may have to deploy this report template manually before it appears
in the dashboard.
To do this, open the rich client, go to the Team Artifacts view, and
expand your project area and the Reports node. Right-click on Report
Templates, select Deploy New Templates... and follow the wizard. Be sure
to deploy both "Release Burndown" and "Micro Release Burndown" - the
micro report is the one used in the dashboard.
james
RTC Reports Team Lead
I think that it is already deployed. In fact the release burndown says that planning is excellent but in reality it was far from being excellent. What didn't we do to have the chart below?
Thanks
Christelle
Here is the description of the Release Burndown report:
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
Could it be that at the beginning of your sprints, you had zero remaining story points?
Can you please show us the chart output by the "Story Points Remaining" report for the same set of iterations?
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
Could it be that at the beginning of your sprints, you had zero remaining story points?
Can you please show us the chart output by the "Story Points Remaining" report for the same set of iterations?