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 - Tracking & Reporting

36,677 views

Published on

Comprehensive presentation detailing reporting and tracking capabilities of Team Foundation Server. Focuses on Excel workbooks and Reporting Services, but touches on other technologies as well.

Published in: Technology
  • if you ever have a need for time-tracking in TFS there are bunch of services. e.g. http://teamexpand.com/
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • good...gives basic idea
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Team Foundation Server - Tracking & Reporting

  1. 1. Team Foundation Server<br />Planning, Tracking, & Reporting<br />Steve Lange<br />Sr. Developer Technology Specialist | Microsoft - Denver, CO<br />stevenl@microsoft.com | slange.me<br />
  2. 2. Agenda<br />Introductions<br />Team Foundation Server<br />Project Planning & Tracking<br />Using Project or Project Server<br />Process Templates<br />Workbooks<br />TFS Reporting Experience<br />Dashboards<br />Excel Reporting<br />SQL Reporting Services Reporting<br />
  3. 3.
  4. 4. TFS Planning, Tracking & Reporting<br />Project Planning & tracking<br />
  5. 5. Project Planning & Tracking<br />Success Characteristics<br />Process Templates<br />Project Scheduling Project or Project Server<br />Planning & Tracking Workbooks<br />
  6. 6. Project Planning & Tracking<br />Success Characteristics<br />Customer need drives the project<br />High-levelplan for delivery<br />Development over several iterations<br />Refines high-level plan over time<br />Effective tools for adapting to changes<br />
  7. 7. Project Planning & Tracking – Process Templates<br />MSF = Microsoft Solutions Framework<br />CMMI = Capability Maturity Model Integration<br />
  8. 8. The process template defines artifacts, planning, and reporting capabilities<br />
  9. 9. Project Scheduling using Project<br />Directly Integrates with TFS Work Items<br />Use scheduling & planning tools in MS Project<br />Determine over-allocation<br />Manage hours, dependencies, constraints, & lead/lag time<br />Create charts showing schedule & resource usage <br />
  10. 10. Project Management using Project Server<br />Enable data to flow from TFS work items to tasks in Project Server enterprise project plans in Project Server. <br />Define requirements<br />Approve status updates<br />Review & set baselines<br />Preview updates & impact to critical paths<br />
  11. 11. TFS Planning & Tracking<br />Workbooks<br />
  12. 12. Workbooks<br />Build your product backlog <br />Plan work <br />Track issues<br />Quickly create work items<br />Set rank, priority, state, & assignments of multiple work items at the same time<br />
  13. 13. Workbooks<br />Product Planning Workbook<br />Iteration Backlog Workbook<br />Issues Workbook<br />Triage Workbook<br />
  14. 14. Workbooks – Product Planning Workbook<br />Balance workload across iterations<br />Worksheets<br />Product Backlog<br />Iteration Planning<br />Interruptions<br />
  15. 15. Workbooks – Iteration Backlog Workbook<br />Plan & track progress of work for each iteration/sprint<br />Calculate team capacity & burndownbased on estimated & remaining effort<br />Worksheets<br />Iteration Backlog<br />Settings<br />Interruptions<br />Capacity<br />Burndown<br />
  16. 16. Workbooks – Issues Workbook<br />Review & rank problems that might block team progress<br />References Issues team query<br />Finds all issues in project<br />
  17. 17. Workbooks – Triage Workbook<br />Review, rank & assign bugs to be worked on for iteration/spring<br />Triage driven by product owner or scrum master with input from team.<br />
  18. 18. TFS Reporting Experience<br />
  19. 19. TFS Reporting Experience<br />About TFS Reporting<br />Excel Reporting<br />Included Excel reports<br />Excel report generation<br />Dashboards<br />Reporting Services Reports<br />
  20. 20. About Team Foundation Server Reporting<br />Two reporting databases<br />Warehouse relational database<br />Good for current state of projects, artifacts, etc.<br />Analysis Services Cube<br />Good for trending, historical reporting, etc.<br />
  21. 21. Excel Reports<br />TFS Reporting Experience<br />
  22. 22. Excel Reporting<br />Included Excel Reports<br />Project Management<br />Bug Backlog Management<br />Build Management<br />Test Management<br />Excel Report Generation<br />
  23. 23. Excel Reports - Project Management<br />Burndown<br />Task Progress<br />User Story Progress<br />Issue Trends<br />
  24. 24. Excel Reports – Bug Backlog Management<br />Bug Progress<br />Bug Trends<br />Bugs by Priority<br />Bugs by Assignment<br />Bug Reactivations<br />
  25. 25. Excel Reports – Build Management<br />Code Coverage<br />Code Churn<br />Build Status<br />
  26. 26. Excel Reports – Test Management<br />Test Plan Progress<br />Test Case Readiness<br />User Story Test Status<br />Test Activity<br />Failure Analysis<br />
  27. 27. Excel Report Generation<br />Create directly from Work Item query<br />Generates<br />Table of contents<br />PivotTable & PivotChart reports<br />Report options<br />Current reports<br />Trend reports<br />
  28. 28. Excel Report Generation<br />Current<br />Work Item Count<br />Work item Type<br />Assigned To<br />State<br />Trend<br />Work Item Count<br />Work Item Type<br />Assigned To<br />State<br />
  29. 29. Dashboards<br />TFS Planning, Tracking, & Reporting<br />
  30. 30. Dashboards<br />Quickly find important information about team projects<br />Show project data, support investigation, & help teams perform common tasks more quickly. <br />Leverage SharePoint products through Web Parts<br />Excel Web Access<br />Team Web Access<br />
  31. 31. My Dashboard<br />What is the next set of Tasks, Bugs, or Test Cases that I should act on?<br />What is the status of the team's most recent builds?<br />
  32. 32. Project Dashboard<br />Is the team likely to finish the iteration on time?<br />Will the team complete the planned work based on the current burn rate? <br />What were the most recent check-ins?<br />Burn Rate<br />Work Item Breakdown<br />Burndown<br />
  33. 33. Progress Dashboard<br />Is the team likely to finish the iteration on time?<br />Will the team complete the planned work based on the current burndown? <br />How much progress has the team made on implementing user stories in the past four weeks? <br />How quickly is the team identifying and closing Issues?<br />What were the most recent check-ins?<br />
  34. 34. Quality Dashboard<br />Is the test effort on track?<br />Is the team testing the appropriate functionality?<br />Are the team's bug fixes of high quality?<br />Are tests stale?<br />Does the team have sufficient tests?<br />Are any bottlenecks occurring? <br />
  35. 35. Test Dashboard<br />Is the authoring of Test Cases on track?<br />Has the team defined Test Cases for all User Stories?<br />What are the proportions of Test Cases that are passing, failing, and blocked?<br />Do test failure metrics indicate a problem that requires further investigation?<br />What is the status of last night's build?<br />What are the most recent check-ins?<br />
  36. 36. Bugs Dashboard<br />How quickly is the team resolving and closing bugs? <br />Is the team fixing bugs quickly enough to finish on time? <br />How many bugs is the team reporting, resolving, and closing per day?<br />Is the team resolving priority 1 bugs before priority 2 and 3 bugs?<br />Does any team member have a backlog of priority 1 bugs that warrant redistribution?<br />
  37. 37. Build Dashboard<br />How volatile is the code base?<br />How much of the code is the team testing?<br />How high is the quality of the builds? <br />Is the quality increasing, decreasing, or staying constant? <br />Which builds succeeded? <br />Which builds have a significant number of changes to the code? <br />
  38. 38. SQL Reporting Services Reports<br />TFS Reporting Experience<br />
  39. 39. Reports Available Based on Process Template<br />
  40. 40. Bug Status Report<br />Is the team fixing bugs quickly enough to finish on time? <br />Is the team fixing high priority bugs first? <br />What is the distribution of bugs by priority and severity?<br />How many bugs are assigned to each team member? <br />
  41. 41. Bug Trends Report<br />How many bugs is the team reporting, resolving, and closing per day? <br />What is the overall trend at which the team is processing bugs? <br />Are bug activation and resolution rates declining toward the end of the iteration as expected?<br />
  42. 42. Reactivations Report<br />How many bugs are being reactivated? <br />How many user stories are being reactivated? <br />Is the team resolving and closing reactivated bugs at an acceptable rate?<br />
  43. 43. Build Quality Indicators Report<br />What is the quality of the software?<br />How often are tests passing, and how much of the code is being tested? <br />Based on the code and test metrics, is the team likely to meet target goals? <br />
  44. 44. Build Success Over Time Report<br />What parts of the project have produced software that is ready to be tested?<br />What parts of the project are having trouble with regressions or bad checkins?<br />How well is the team testing the code? <br />
  45. 45. Build Summary Report<br />What is the status of all builds over time?<br />Which builds succeeded? <br />Which builds have a significant number of changes to the code? <br />How much of the code was executed by the tests?<br />Which builds are ready to install? <br />
  46. 46. Burndown and Burn Rate Report<br />Is the team likely to finish the iteration on time? <br />Will the team complete the required work, based on the current burn rate? <br />How much work does each team member have? <br />
  47. 47. Remaining Work Report<br />What is the cumulative flow of work?<br />Is the team likely to finish the iteration on time? <br />Is the amount of work or number of work items in the iteration growing? <br />Does the team have too much work in progress? <br />How is the team doing in estimating work for the iteration?<br />Hours of Work<br /># of Work Items<br />
  48. 48. Status on All Iterations Report<br />Is steady progress being made across all iterations?<br />How many stories did the team complete for each iteration? <br />How many hours did the team work for each iteration? <br />For each iteration, how many bugs did the team find, resolve, or close? <br />
  49. 49. Stories Overview Report (Agile)<br />How much work does each story require? <br />How much work has the team completed for each story? <br />Are the tests for each story passing? <br />How many active bugs does each story have?<br />
  50. 50. Stories Progress Report (Agile)<br />How much progress has the team made toward completing the work for each story? <br />How much work must the team still perform to implement each user story? <br />How much work did the team perform in the last calendar period?<br />
  51. 51. Requirements Progress Report (CMMI)<br />How much progress has the team made toward completing the work for each requirement? <br />How much work must the team still perform to implement each requirement? <br />How much work did the team perform in the last calendar period?<br />
  52. 52. Requirements Overview Report (CMMI)<br />How much work does each Requirement require? <br />How much work has the team completed for each Requirement? <br />Are the tests for each Requirement passing? <br />How many active bugs does each Requirement have?<br />
  53. 53. Release Burndown (Scrum)<br />How much work remains in the release?<br />How quickly is your team working through the product backlog? <br />
  54. 54. Sprint Burndown (Scrum)<br />How much work remains in the sprint? <br />Is your team on track to finish all work for the sprint?<br />When will your team finish all work for the sprint?<br />How much work for the sprint is in progress?<br />
  55. 55. Unplanned Work Report<br />How much work was added after the iteration started?<br />Is too much work being added during the iteration? <br />
  56. 56. Test Case Readiness Report<br />When will all the test cases be ready to run? <br />Will all the test cases be ready to run by the end of the iteration? <br />How many test cases must the team still write and review? <br />How many test cases are ready to be run? <br />
  57. 57. Test Plan Progress Report<br />How much testing has the team completed?<br />Is the team likely to finish the testing on time?<br />How many tests are left to be run?<br />How many tests are passing?<br />How many tests are failing?<br />How many tests are blocked?<br />
  58. 58. Summary<br />
  59. 59. Summary<br />Use familiar tools for planning & tracking project status<br />Project<br />Project Server<br />Excel<br />Web<br />Reporting available to everyone<br />Visual Studio<br />Excel<br />Reporting website<br />SharePoint<br />Comprehensive, powerful, flexible reporting mechanisms<br />
  60. 60. Questions?<br />
  61. 61. Steve Lange<br />Sr. Developer Technology Specialist <br />Microsoft – Denver, CO<br />Email: stevenl@microsoft.com<br />Blog: slange.me<br />Twitter: @stevelange<br />
  62. 62.
  63. 63. Appendix<br />Links to Additional Resources<br />
  64. 64. Links<br />Project Planning & Tracking<br />Using Project or Project Server<br />Process Templates<br />MSF for Agile<br />MSF for CMMI<br />Visual Studio Scrum<br />Workbooks (Agile | CMMI)<br />TFS Reporting Experience<br />Dashboards (Agile | CMMI)<br />Excel Reporting (Agile | CMMI)<br />SQL Reporting Services Reporting (Agile | CMMI)<br />

×