Project Dashboard (CMMI)
You can use the Project dashboard to track team progress toward completing an iteration. This dashboard displays data that helps you monitor task burndown, burn rate, and the product backlog.
Note
You access dashboards through your team project portal. You can access the Project dashboard only if that portal has been enabled and is configured to use SharePoint Foundation. Also, for the Task Burndown and Burn Rate charts to be available, the team project collection that contains your team project must be configured with SQL Server Reporting Services. This report is not available if .png "Report"){kind=icon}
Reports does not appear when you open Team Explorer and expand your team project node. For more information, see Dashboards (CMMI).
In this topic
|
You can use this dashboard to answer the following questions:
|
Required permissions
To view the dashboard, you must be assigned or belong to a group that has been assigned the Read permissions in SharePoint Products for the team project. To modify, copy, or customize a dashboard, you must be assigned or belong to a group that has been assigned the Members permissions in SharePoint Products for the team project. For more information, see Add users to team projects.
To modify a report in this dashboard, you must be a member of the TfsWarehouseDataReaders security role in the SQL Server Analysis Services database for Team Foundation. You must also have read access to the warehouse database for Team Foundation. For more information, see Grant permissions to view or create reports in TFS.
To view a work item, you must be a member of the Readers group or your View work items in this node permission must be set to Allow. To create or modify a work item, you must be a member of the Contributors group or your Edit work items in this node permission must be set to Allow.
Data displayed in the dashboard
You can use the Project dashboard to understand how much progress the team is making toward completing tasks. Specifically, this dashboard displays the Web parts that the following illustration shows and that the following table describes.
.png "Project dashboard (Agile)")
Note
Burndown and burn rate charts, reports .png "Step 1")
and .png "Step 2")
, do not appear when the server that hosts Analysis Services for the team project is not available.
For more information about how to interpret, update, or customize the charts that appear in the Project dashboard, see the topics that are listed in the following table:
Web part |
Data displayed |
Related topic |
|---|---|---|
|
A visual representation of the cumulative count of all hours that the team spent on all task work items for the past four weeks. .png "Burndown chart")
The Ideal Trend line calculates a slope or trajectory for when work will be completed based on the amount of work remaining and the end date of the report. The line is drawn from the remaining work on the start date to intersect the x-axis on the end date. |
|
|
Bar chart that shows the actual and required burn rate of the team. The burn rate shows how quickly the team is actually completing planned work and what the rate must be to complete the currently active tasks on schedule. .png "Burn Rate Excel Report") |
|
.png "Step 3") |
Team Web Access list of active requirements. |
Product Requirements team query. For more information, see Shared queries (CMMI) |
.png "Step 4") |
List of upcoming events. The list is derived from a SharePoint Web part. .png "Import Events Web part") |
Not applicable |
.png "Step 5") |
Count of active, resolved, and closed work items. You can open the list of work items by selecting each number. This list is derived from a Team Web Access Web part. .png "Project work items") |
|
.png "Step 6") |
List of recent builds and their status. You can view more details about a specific build by selecting it. This list is derived from a Team Web Access Web part. .png "Recent Builds Web part")
Legend:
|
|
.png "Step 7") |
List of the most recent check-ins. You can view more details about a specific check-in by choosing it. This list is derived from a Team Web Access Web part. .png "Recent Checkins Web part") |
.gif "Build in Progress"){kind=icon}
: Build not started.gif "Build Not Started"){kind=icon}
: Build in progress.gif "Build Succeeded"){kind=icon}
: Build succeeded.gif "Build Failed"){kind=icon}
: Build failed.gif "Build Stopped"){kind=icon}
: Build stopped.gif "Build Partially Succeeded"){kind=icon}
: Build partially succeededRequired activities for tracking task burndown and burn rate
For the reports that appear in the Project dashboard to be useful and accurate, the team must perform the following activities:
Define tasks.
Specify and update the Completed and Remaining fields for each task as the team works on it.
Important
If you subdivide a task into subtasks, specify hours only for the subtasks. These hours are rolled up as summary values for the parent task and the requirement.
Update the State of each task as it progresses from Active to Closed.
(optional) Specify the Iteration and Area paths for each work item if you want to filter by those fields.
Tracking an iteration
By using the Project dashboard, product owners and the team can view the team's progress and determine whether the team is making sufficient progress.
For more information about how to customize the Project Dashboard and the types of questions to ask based on the indicators that appear within the dashboard, see the following sections:
Modify the Task Burndown Report for an Iteration
Monitoring Progress
Modify the Task Burndown report for an iteration
To track an iteration by using the Project Dashboard, you must modify the parameters for the Task Burndown and Burn Rate reports in Report Manager to reflect the start and end dates for your iteration. By default, the start date is five days before the current date.
To modify the Task Burndown and Burn Rate reports to correspond to a specific iteration
In the dashboard navigation panel, choose Reports.
In Report Manager, choose Dashboards, and then choose Burndown.
Choose Properties and then choose Parameters.
For the StartDateParam parameter, choose Override Default, and type the iteration start date in the text box with the format mm/dd/yyyy.
For the EndDateParam parameter, choose Override Default, and type the iteration end date in the text box with the format mm/dd/yyyy.
Choose Apply.
At the top of Report Manager, choose the Dashboards navigation link, and then choose Burn Rate.
Repeat steps 3 through 6.
Return to the Project Dashboard and refresh the browser.
Verify that the Task Burndown chart now shows the new start and end dates.
To switch between displaying work hours and number of work items in the Task Burndown or Burn Rate reports
In the dashboard navigation panel, choose Reports.
In Report Manager, choose Dashboards, and then choose Burndown or Burn Rate.
Choose Properties, and then choose Parameters.
In the YAxis list, choose one of the following options:
Hours of Work displays the cumulative number of work hours for all tasks that are defined for the iteration.
Number of Work Items displays the cumulative number of work items, grouped by state, that are defined for the iteration.
Choose Apply.
To display different trend lines in the Task Burndown report
In the dashboard navigation panel, choose Reports.
In Report Manager, choose Dashboards, and then choose Burndown.
Choose Properties, and then choose Parameters.
In the TrendLineParameter list, choose one of the following options:
Display Actual displays a band that is based on the actual burndown. The band intersects the x-axis when the iteration is expected to finish.
Display Ideal displays a straight line from the remaining work at the start date to the x-axis on the end date.
Display Both displays both the actual and ideal trend lines.
None does not display a trend line.
Choose Apply.
Return to the Project Dashboard, and refresh the browser.
Monitoring Progress
To monitor team progress, you can review the Task Burndown (hours report for the following types of indicators:
Has Completed Work stopped increasing in the Task Burndown (hours) report?
One or more issues might be blocking progress or the team might not be resolving and closing work items that it has completed, fixed, and verified.
Is the team adding or expanding the scope of work during the iteration?
Significant increases over time to the amount of Remaining Work may indicate poor estimations or scope creep. That is, either the team did not accurately estimate the work at the start of the iteration or the team added features after the iteration started. When required effort is larger than estimated effort, team members might be underestimating the difficulty, time, or other factors. You should investigate the root causes. For example, you might want to determine how granular the tasks are.
Do changes in the reports match your expectations?
Dashboard reports reflect work that the team is tracking. You should expect the reports to change according to the decisions and changes that the team makes about the work. If the team reallocates work to another iteration or decides to add work for an iteration, those one or more reports on the Project dashboard should reflect those decisions.
If the slope of the Remaining Work is progressing near or under the Ideal Trend line, the team is executing well against the iteration plan. However, if the Remaining Work slope is higher than the Ideal Trend line, the team will probably not complete all planned Tasks before the end of the iteration.