Team Foundation Server 2010 scheduled for release in mid-April will include several new TFS reporting options. The main improvements are a set of Excel-based SharePoint dashboards, improved SQL Reporting Services, and Excel Reports based on Work Item Queries. With more possibilities for bug, build, and test control, as well as more place for customization, software development projects, I believe, may become now more transparent.

Why I’m so fond of TFS customization and transparency?

Well, there are no two absolutely similar projects. The goals are different, as well as the requirements. Metrics that a customer needs to track are also different, depending on the goals a customer aims to achieve. TFS reporting allow for getting more metrics needed, which can make the project more transparent and improve the control over it.

What project transparency may lead to?

Improved TFS reporting allows for more comprehensive information on bugs, builds, and tests, which provides clearer picture of the project in progress and gives the possibility to find out the points where the project may stick.

By virtue of the improved TFS reporting, software development projects may get more transparency, with more places for improvement becoming evident. So, the decision on necessary changes may be taken earlier, which is an obvious benefit, since implementing changes and bug fixing on the early stages of the project prevents unwanted expenses.