Burndown and Burn Rate Report (CMMI)
After a team has worked on one or more iterations, also known as sprints, you can determine the rate of team progress by reviewing the Burndown and Burn Rate report. Burndown shows the trend of completed and remaining work over a specified time period. Burn rate provides calculations of the completed and required rate of work based on the specified time period. In addition, a chart shows the amount of completed and remaining work that is assigned to team members. You can view the Burndown and Burn Rate report based on hours worked or number of work items that have been resolved and closed.
For information about how to access, refresh, or manage reports, see Reports (CMMI).
Note
This report requires that the team project collection that contains your team project was provisioned 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.
In this topic
|
You can use this report to answer the following questions:
|
Required Permissions
To view the report, you must be assigned or belong to a group that has been assigned the Browser role in SQL Server Reporting Services. For more information, see Add Users to Team Projects or Managing Permissions.
Data in the Report
The Burndown and Burn Rate report summarizes the data that was captured during the time interval that you specify for each task, requirement, or bug based on the filters that you specify. The data is derived from the data warehouse.
You can filter the report in the following ways:
Change the start and end dates for the report.
Filter the tasks that are counted in the report by specifying iteration and area paths and work item states. You can also filter the report to show requirements and bugs.
For more information, see Filtering the Report and Changing the Display later in this topic.
You can use the Burndown and Burn Rate report to understand how well the team is progressing and whether the team or a team member is over-allocated. The upper section of the report displays a version of the Remaining Work report, as the following illustration shows.
.png "Example Burndown and Velocity report - bottom")
In addition, you can display trend lines that predict when work will be completed. 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 that you define for the report. The actual trend line is calculated based on the team's actual progress in completing work and closing work items.
The lower section of the report presents a calculation of the team's burn rate, both actual and required, and a breakdown of work assignments to each team member, as the following illustration shows:
.png "Example Burndown and Velocity report - top")
Burndown
Burndown shows the trend of how much work has been completed and how much work remains across time in an iteration or a release. The source of the raw data is either work hours or work remaining, which is tracked on the vertical axis, and the time period (days), which is tracked on the horizontal axis.
Hours |
Number of Work Items |
|---|---|
Trend lines:
|
|
Burn Rate
The Burn Rate section of the report shows an estimate of how much work a team can complete during an iteration. Burn rate is one of the key elements for estimation. This calculation shows how quickly the team is actually completing planned work and how much the rate varies from day to day, or iteration to iteration. You can use this data to plan the next iteration, together with the quality measures. Similar to the Remaining Work report, this strategy is most useful when you look at days within an iteration or several iterations within a project. For more information, see Remaining Work Report.
The following table describes how the burn rate is calculated.
Team Burn Rate (Hours Completed/Day) |
Team Burn Rate (Work Items Completed/Day) |
|---|---|
|
|
Assignment of Work
The Assignment of Work section of the report provides insight into how well work has been allocated across the team, in addition to the work that the team completed and that remains for each team member. The following table describes the information that this view provides.
Assignment of Work (Hours) |
Assignment of Work (Number of Work Items) |
|---|---|
For each team member:
|
For each team member:
|
Required Activities for Tracking Work Items
For the Burndown and Burn Rate report to be useful and accurate, the team must perform the following activities for tracking work items:
Define tasks, requirements, and bugs, and specify the Iteration and Area paths for each.
Specify and update the Completed and Remaining fields for each task or subtask as it is worked on.
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 requirement. For more information, see Address Inaccuracies Published for Summary Values.
Update the State of each task, requirement, and bug as it progresses from active to closed.
Setting the Duration of the Iteration
To understand the progress that the team has made for your current iteration, the start and end dates for the report must match your current iteration cycle. Results for the actual trend and team burn rate will vary significantly based on the duration that you set for the iteration.
To change the duration of the iteration
For the Iteration Start (Date) and Iteration End (Date), click the calendar icon, and then click the date that corresponds to the start or end of the iteration.
Click View Report.
Interpreting the Report
You can filter the report in the following ways:
Change the start and end dates for the report.
Filter the tasks, stories, and bugs that are counted in the report by specifying iteration and area paths, work item types, and work item states.
For more information, see Filtering of the Report and Changing the Display later in this topic.
Questions That the Report Answers
You can review the report to determine the progress that the team made within an iteration or over time. For example, you can find answers to the following questions:
Burndown
How fast is the team completing remaining work?
Is the team adding work during the iteration? Is there scope creep?
How much work can the team complete in the available time?
When can the team finish the work?
When can the team finish the current iteration?
Burn Rate
- Is the team working quickly enough to finish the remaining work on time?
Work Assignment
How is the work distributed across the team?
Should the team balance the remaining work load?
Healthy Versions of the Report
A healthy Burndown and Burn Rate report shows that the team is making steady progress toward finishing the work. The actual and ideal trend lines are close together.
.png "Healthy version of Burndown report")
Unhealthy Versions of the Report
An unhealthy Burndown and Burn Rate report will show one or more of the following indications:
Actual and ideal trend lines are diverging or are far apart.
When the team burn rate does not meet the planned burn rate, the burndown report will show an Actual Trend line that is far above the Ideal Trend line. The Actual Trend line will intersect the x-axis significantly later than the planned end date. These characteristics indicate that the team will not complete all of the requirements that were planned for this iteration before it ends. When actual progress is less than planned progress, the required effort is larger than the team estimated, the tasks are more difficult, or the team underestimated or did not consider other factors.
The total number of hours is increasing.
Scope creep occurs when team members add features to an iteration after it is planned. The following illustration shows an iteration in which a team is taking on more work over time and making minimal progress on the work that had already been assigned.
.png "Burndown showing scope creep")
Filtering the Report and Changing the Display
You can filter the Burndown and Burn Rate report or change its display in the following ways:
Filter the requirements, bugs, and tasks that the report represents by specifying iteration and area paths, work item types, and work item states.
Change the view.
Specify the type of trend line to display.
The following illustration shows the available filters and display options:
.png "Filters for the Burndown and Velocity report")
To filter the set of work items that are counted in the report
Perform one or both of the following actions:
In the Iteration or Area list, select the check box of each iteration or product area to include.
In the Work Item Type or State list, select the check box of each work item type or state to include.
Click View Report.
To switch between work hours and number of work items displayed in the report
In the Measure list, click 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.
Click View Report.
To display trend lines
In the Trend Line list, click 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.
Click View Report.
See Also
Concepts
Requirements Progress Report (CMMI)