1 / 47

Team Foundation Server Overview

Team Foundation Server Overview. Randy Pagels Developer Technology Specialist Developer Platform & Evangelism | Heartland District Microsoft Corporation | Detroit, MI. Project Visibility. Streamline the Process. Reporting capabilities. Reporting Structure. Configuration DB.

frisco
Download Presentation

Team Foundation Server Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Team Foundation Server Overview Randy Pagels Developer Technology Specialist Developer Platform & Evangelism | Heartland District Microsoft Corporation | Detroit, MI

  2. Project Visibility

  3. Streamline the Process Reporting capabilities

  4. Reporting Structure Configuration DB Collection 1 Team Project X Team Project Y Collection 2 Team Project X Team Project Y Data Warehouse Relational Warehouse Collection 3 Team Project X Team Project Y Analysis Services Cube

  5. Visualizing the Cube User Story 12 Work Items Task 5 Test Case 8 16 Bug 4 6 45 24 3/1/2011 3/10/2011 3/12/2011 3/22/2011 Closed Ready Resolved Active Time State

  6. Streamline the Process Excel Reports

  7. Simplified Reporting • Reports using SQL Server Reporting Services • Detailed and thorough • Workbook queries with Microsoft Office Excel • Fast and flexible

  8. Excel Reporting • Included Excel Reports • Project Management • Bug Backlog Management • Build Management • Test Management • Excel Report Generation

  9. Excel Reports - Project Management • Burndown • Task Progress • User Story Progress • Issue Trends

  10. Excel Reports – Bug Backlog Management • Bug Progress • Bug Trends • Bugs by Priority • Bugs by Assignment • Bug Reactivations

  11. Excel Reports – Build Management • Code Coverage • Code Churn • Build Status

  12. Excel Reports – Test Management • Test Plan Progress • Test Case Readiness • User Story Test Status • Test Activity • Failure Analysis

  13. Excel Report Generation • Create directly from Work Item query • Generates • Table of contents • PivotTable & PivotChart reports • Report options • Current reports • Trend reports

  14. Excel Report Generation • Current • Work Item Count • Work item Type • Assigned To • State • Trend • Work Item Count • Work Item Type • Assigned To • State

  15. Streamline the Process SQL Server Reporting services

  16. TFS Reporting Experience SQL Reporting Services Reports

  17. Reports Available Based on Process Template

  18. Bug Status Report • Is the team fixing bugs quickly enough to finish on time? • Is the team fixing high priority bugs first? • What is the distribution of bugs by priority and severity? • How many bugs are assigned to each team member?

  19. Bug Trends Report • How many bugs is the team reporting, resolving, and closing per day? • What is the overall trend at which the team is processing bugs? • Are bug activation and resolution rates declining toward the end of the iteration as expected?

  20. Reactivations Report • How many bugs are being reactivated? • How many user stories are being reactivated? • Is the team resolving and closing reactivated bugs at an acceptable rate?

  21. Build Quality Indicators Report • What is the quality of the software? • How often are tests passing, and how much of the code is being tested? • Based on the code and test metrics, is the team likely to meet target goals?

  22. Build Success Over Time Report • What parts of the project have produced software that is ready to be tested? • What parts of the project are having trouble with regressions or bad checkins? • How well is the team testing the code?

  23. Build Summary Report • What is the status of all builds over time? • Which builds succeeded? • Which builds have a significant number of changes to the code? • How much of the code was executed by the tests? • Which builds are ready to install?

  24. Burndown and Burn Rate Report • Is the team likely to finish the iteration on time? • Will the team complete the required work, based on the current burn rate? • How much work does each team member have?

  25. Remaining Work Report • What is the cumulative flow of work? • Is the team likely to finish the iteration on time? • Is the amount of work or number of work items in the iteration growing? • Does the team have too much work in progress? • How is the team doing in estimating work for the iteration? Hours of Work # of Work Items

  26. Status on All Iterations Report • Is steady progress being made across all iterations? • How many stories did the team complete for each iteration? • How many hours did the team work for each iteration? • For each iteration, how many bugs did the team find, resolve, or close?

  27. Stories Overview Report (Agile) • How much work does each story require? • How much work has the team completed for each story? • Are the tests for each story passing? • How many active bugs does each story have?

  28. Stories Progress Report (Agile) • How much progress has the team made toward completing the work for each story? • How much work must the team still perform to implement each user story? • How much work did the team perform in the last calendar period?

  29. Requirements Progress Report (CMMI) • How much progress has the team made toward completing the work for each requirement? • How much work must the team still perform to implement each requirement? • How much work did the team perform in the last calendar period?

  30. Requirements Overview Report (CMMI) • How much work does each Requirement require? • How much work has the team completed for each Requirement? • Are the tests for each Requirement passing? • How many active bugs does each Requirement have?

  31. Release Burndown (Scrum) • How much work remains in the release? • How quickly is your team working through the product backlog?

  32. Sprint Burndown (Scrum) • How much work remains in the sprint? • Is your team on track to finish all work for the sprint? • When will your team finish all work for the sprint? • How much work for the sprint is in progress?

  33. Unplanned Work Report • How much work was added after the iteration started? • Is too much work being added during the iteration?

  34. Test Case Readiness Report • When will all the test cases be ready to run? • Will all the test cases be ready to run by the end of the iteration? • How many test cases must the team still write and review? • How many test cases are ready to be run?

  35. Test Plan Progress Report • How much testing has the team completed? • Is the team likely to finish the testing on time? • How many tests are left to be run? • How many tests are passing? • How many tests are failing? • How many tests are blocked?

  36. Streamline the Process Dashboards

  37. Dashboards • Quickly find important information about team projects • Show project data, support investigation, & help teams perform common tasks more quickly. • Leverage SharePoint products through Web Parts • Excel Web Access • Team Web Access

  38. My Dashboard • What is the next set of Tasks, Bugs, or Test Cases that I should act on? • What is the status of the team's most recent builds?

  39. Project Dashboard • Is the team likely to finish the iteration on time? • Will the team complete the planned work based on the current burn rate? • What were the most recent check-ins? Burn Rate Work Item Breakdown Burndown

  40. Progress Dashboard • Is the team likely to finish the iteration on time? • Will the team complete the planned work based on the current burndown? • How much progress has the team made on implementing user stories in the past four weeks? • How quickly is the team identifying and closing Issues? • What were the most recent check-ins?

  41. Quality Dashboard • Is the test effort on track? • Is the team testing the appropriate functionality? • Are the team's bug fixes of high quality? • Are tests stale? • Does the team have sufficient tests? • Are any bottlenecks occurring?

  42. Test Dashboard • 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 night's build? • What are the most recent check-ins?

  43. Bugs Dashboard • 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 warrant redistribution?

  44. Build Dashboard • 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 staying constant? • Which builds succeeded? • Which builds have a significant number of changes to the code?

  45. Streamline the Process Microsoft TFS usage

  46. Microsoft TFS EnvironmentServicing organizations such as MSIT, DevDiv, Windows, SQL, AdCenter, MSN/Windows Live, Bing Mobile, Windows Azure, MEDPG, and HED Hawaii Redmond Fargo North Carolina Northern Ireland Scotland France Hyderabad Shanghai Visual Source Safe migration

More Related