Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Team Foundation Server 2012 Reporting

An overview of the reporting capabilities in Team Foundation Server 2012. Includes explanation of Data warehouse architecture, included reports (SSRS and Excel), and customization.

  • Login to see the comments

Team Foundation Server 2012 Reporting

  1. 1. Monitor Operate Working software in production Value realization
  2. 2. Monitor Operate Working software in production Value realization
  3. 3. Monitor Operate Working software in production Value realization
  4. 4. Operational Stores
  5. 5. Warehouse Adapters
  6. 6. Warehouse RelationalDatabase
  7. 7. Analysis Services Cube
  8. 8. Report Designer Reports
  9. 9. Excel Reports
  10. 10. Excel Reports Excel ReportProject Management GenerationBug Backlog Management Create reports in Excel from work item queriesBuild ManagementTest Management
  11. 11. Quickly find important information about team projectsShow project data, support investigation, & help teams perform common tasks more quickly.
  12. 12. Windows SharePoint SharePoint Server SharePoint Server Services 3.0 Standard EnterpriseMy X X XProject X XProgress XQuality XTest XBugs XBuild X
  13. 13. What is the next set of Tasks, Bugs, or Test Cases that I should act on?What is the status of the teams most recent builds?
  14. 14. Is the team likely to finish the iteration on time?Will the team complete the planned work based on the currentburn rate?What were the most recent check-ins? Burn Rate Work Item Breakdown Burndown
  15. 15. Is the team likely to finish the iteration on time?Will the team complete the planned work based on the currentburndown?How much progress has the team made on implementing userstories in the past four weeks?How quickly is the team identifying and closing Issues?What were the most recent check-ins?
  16. 16. Is the test effort on track?Is the team testing the appropriate functionality?Are the teams bug fixes of high quality?Are tests stale?Does the team have sufficient tests?Are any bottlenecks occurring?
  17. 17. Is the authoring of Test Cases on track?Has the team defined Test Cases for all User Stories?What are the proportions of Test Cases that are passing, failing, and blocked?Do test failure metrics indicate a problem that requires further investigation?What is the status of last nights build?What are the most recent check-ins?
  18. 18. How quickly is the team resolving and closing bugs?Is the team fixing bugs quickly enough to finish on time?How many bugs is the team reporting, resolving, and closing per day?Is the team resolving priority 1 bugs before priority 2 and 3 bugs?Does any team member have a backlog of priority 1 bugs that warrantredistribution?
  19. 19. How volatile is the code base?How much of the code is the team testing?How high is the quality of the builds?Is the quality increasing, decreasing, or stayingconstant?Which builds succeeded?Which builds have a significant number of changesto the code?
  20. 20. # Hours of Items of Work Work
  21. 21. Fact/Fact Table
  22. 22. Attribute
  23. 23. Dimension
  24. 24. KPIs
  25. 25. Measure
  26. 26. Measure Group
  27. 27. Perspective
  28. 28. Relational DB OLAP Cube Work item query resultsExcelProject or Project ServerReport BuilderReport Designer
  29. 29. Use Familiar Tools Get the Visibility YouExcel WantSharePoint Many included reportsReporting Services Customize or create your ownOthers
  30. 30. Thank You
  31. 31. Steve Langesr. developer technology specialiststevenl@microsoft.com@stevelange | http://slange.me
  32. 32. Figure 1:MagicQuadrant forApplicationLifecycleManagement

×