TFS 2017 | TFS 2015 | TFS 2013
Excel reports, Reporting Services reports, and SharePoint dashboards are only supported for on-premises TFS. For information on what is supported for VSTS, see Dashboards, charts, & widgets.
TFS 2018 and later versions no longer support native integration with SharePoint products. If you're planning to upgrade to TFS 2018, read About SharePoint integration to learn about the options available to you.
You can use the Requirements Excel report to track the rate at which the team is implementing requirements. This report shows the distribution of active, resolved, and closed requirements over time. For information about how to access this report, see Excel reports.
You can view the Requirements report from the Burndown dashboard. You can access this dashboard only if your team project portal has been enabled and is provisioned to use Microsoft Office SharePoint Server 2007. For more information, see Configure or redirect process guidance.
To view the report, 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 or customize the report, you must be a member of the TfsWarehouseDataReaders security role in SQL Server Analysis Services. You must also 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 Grant Access to the Databases of the Data Warehouse for Team System.
Data in the Report
You can use the Requirements report to understand how well the team is completing the requirements that it defined for an iteration or release. This report is based on a PivotChart report that shows the last four weeks of data that was captured for requirements and that is stored in the data warehouse.
Required Activities for Tracking Requirements
For the Requirements report to be useful and accurate, the team must perform the following activities:
Update the State of each requirement as it transitions from Active to Resolved to Closed.
(optional) Specify the Iteration path, Area path, or both of each requirement if you want to filter by those fields.
Interpreting the Report
You should expect the Requirements report to vary based on where you are in your product development cycle. Early iterations should show a gradual increase in the number of active requirements. Iterations that are near the end of a product cycle should show a wide band of resolved and closed Requirements.
You can review the chart to determine the team's progress over time or during an iteration. Specifically, you can determine how much progress the team is making toward resolving and closing user stories.
Updating and Customizing the Report
You can update the Requirements report by opening the report in Office Excel and changing the filter options for the PivotTable report. You can customize this report to support other views as the following table describes.
|Burndown of requirements for an iteration||Change the filter for Iteration (default=All)|
|Burndown of requirements for a product area||Change the filter for Area (default=All)|
|Burndown of requirements for the last six, eight, or more weeks||In the Columns PivotTable Field List, replace @@Last 4 weeks@@ with a different Set|
For more information about how to work with and customize PivotTable and PivotChart reports, see the following pages on the Microsoft Web site: