![]() Actual: The total number of work items that the team completed during the time interval that you specify and divided by the number of days in the interval. Required: The total number of hours that the team estimated for the time interval that you specify and divided by the number of days in the interval. Actual: The total number of hours that the team completed during the time interval that you specify and divided by the number of days in the interval. Team Burn Rate (Work Items Completed/Day) The following table describes how the burn rate is calculated. For more information, see Remaining Work. 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. You can use this data to plan the next iteration, together with the quality measures. It also shows how much the rate varies from day to day, or iteration to iteration. This calculation shows how quickly the team is actually completing planned work. Burn rate is one of the key elements for estimation. The Burn Rate section of the report shows an estimate of how much work a team can complete during an iteration. Closed: The cumulative total of all tasks, user stories, or bugs in the Closed (green) state. Resolved: The cumulative total of all user stories or bugs and that are in the Resolved (gold) state. Active: The cumulative total of all tasks, user stories, or bugs that are in the Active (blue) state. Ideal: The line is drawn from the remaining work on the start date to intersect the x-axis on the end date. Actual: The line intersects the x-axis when the iteration is expected to complete based on the actual rate of hours being completed and hours remaining. Hours Completed: The cumulative value of all completed hours for all tasks. Hours Remaining: The cumulative value of all remaining hours for all tasks. The source of the raw data is either work hours or work remaining, which the report tracks on the vertical axis, and the time period (days), which the report tracks on the horizontal axis. 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:īurndown shows the trend of how much work has been completed and how much work remains across time in an iteration or a release. The actual trend line is calculated based on the team's actual progress in completing work and closing work items. 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. You can also display trend lines that predict when work will be completed. ![]() The upper section of the report displays a version of the Remaining Work report, as the following illustration shows. Also, assess whether the team or a team member is over-allocated. You can use the Burndown and Burn Rate report to understand how well the team is progressing. You can also filter the report to show user stories and bugs.įor more information, see Filtering the Report and Changing the Display later in this article. You can filter the report in the following ways:Ĭhange the start and end dates for the report.įilter the tasks that are counted in the report by specifying iteration and area paths and work item states. The data is derived from the data warehouse. The Burndown and Burn Rate report summarizes the data that was captured during the time interval that you specify for each task, user story, or bug based on the filters that you specify. ![]() For more information, see Add users to team projects. 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. How much work does each team member have? Prerequisites Will the team complete the required work, based on the current burn rate? Is the team likely to finish the iteration on time? You can use this report to answer the following questions: This report is not available if Reports does not appear when you open Team Explorer and expand your team project node. This report requires that the team project collection that contains your team project was provisioned with SQL Server Reporting Services. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |