Blog Post: TFS 2010 Code Churn Report – Getting Additional Detail

Yazan: SyncEXPERT | 06 July 2010 | No Comments
Categories: Microsoft Sync Framework


Warning: mt_rand(): max(-1) is smaller than min(0) in /home/syncexp/public_html/wp/wp-content/plugins/thumbnails_anywhere/ta_homepage.php on line 51
Blog Post: TFS 2010 Code Churn Report – Getting Additional Detail

It’s great to see more TFS users use a tool they know, Excel, in conjunction with a tool they may not know so well, Analysis Services to answer questions about their software project.? The default TFS reports provide a great first level of detail but you will frequently need to get to the next (and next-next) levels of detail to answer questions about your project.? No matter what your role in the project the more you can visit the “self serve business intelligence counter” via Excel connected to the TFS data warehouse the more productive conversations you can have with your team.? Turning “hmmm… we had a bunch of code churn yesterday” to “I see most of the code churn yesterday were added class files in our queuing component… is that related to the bug fix we approved yesterday?? I wouldn’t expect new files to be added for a bug fix”? Now that is real world and just one example how data can turn a conversation productive! I’ll use the code churn as an example on how the default TFS reports are a great starting point for project information and how you will need to get some additional detail. On a project I’m involved with they use the TFS 2010 Build Quality Indicators Report , a default report in the Agile process template, to make sure most tests are passing and increasing in number, code coverage is at the target level and code churn is trending down as we close an iteration. They hit a couple builds with high code coverage (see to the right, circled) and wanted to confirm if this was expected or not.? Here is how you can get more detail on code churn