1.  Stephanie Saad Group Program Manager Team Foundation Server TL04

2. Product Divisions Office, Windows, Developer Division, SQL ITMSIT

4. UsersProjectsWork ItemsSource FilesBuilds VS 200813,1062,4942,568,42040,790,715464,879 VS 20101,56914183,018 Total14,6752,5082,751,43840,790,715464,879 Dogfood: n. [Microsoft, Netscape] Interim software used internally for testing. "To eat one's own dogfood“… means to use the software one is developing, as part of one's everyday development environment… Developers… using their own software will quickly learn what's missing or broken.

5. Recent Users 2,797 Work Items 490,997 Work Item Versions 4,156,617 Source Control Files 373,328,986 Compressed File Size 3.1 Terabytes Builds7,971 Largest instance at Microsoft Largest instance at Microsoft

6. Recent Users 2,797 Work Items 490,997 Work Item Versions 4,156,617 Source Control Files 373,328,986 Compressed File Size 3,157 GB Builds7,971 We Find the Pain So We Can Promise It Works We Find the Pain So We Can Promise It Works (But This is Rough – It is Very Real Pain for Teams) (One Team’s Hall Whiteboard after TFS dogfood outages summer 08)

7. Recent Users 2,797 Work Items 490,997 Work Item Versions 4,156,617 Source Control Files 373,328,986 Compressed File Size 3,157 GB Builds7,971 Largest instance at Microsoft Largest instance at Microsoft

8. Recent Users 2,797 Work Items 490,997 Work Item Versions 4,156,617 Source Control Files 373,328,986 Compressed File Size 3,157 GB Builds7,971 Largest instance at Microsoft Largest instance at Microsoft

9. If all 373,328,986 source files were printed, they would wrap the Earth 2.6 times

10. Problems To Solve

11. The Challenge The Solution

12. 6-week iterations Iteration reviews

19. The Challenge The Solution

20. Features Experiences Value proposition Scenarios Value Props Exp Feature Exp Feature Value Props Exp Feature

21. Scenarios Value Props Exp Feature Exp Feature Value Props Exp Feature Planning Work

24. Features Experiences Value proposition Pillars Value Props Feature Groups Deliverables Feature Groups Deliverables Value Props Feature Groups Deliverables

37. The Challenge The Solution

38. VS 2005 Bug Stepdown at Beta 1

40. Security plan Static code analysis Code coverage No performance regressions Localization testing API reviews All bugs fixed

42. VS 2005 Beta 1 Product Bugs only VS 2008 Beta 1 ALL bug debt

43. The Challenge The Solution

44. $/DEV10/Main $/DEV10/PU/ $/DEV10/PU/ $/DEV10/feature/ $/DEV10/feature/ $/DEV10/PU / $/DEV10/PU / $/DEV10/feature/ $/DEV10/feature/

46. The Challenge The Solution

47. When They MigratedMirrors VSTS 2003 – Very Limited (TFS) 2005 – Most teams 2006 – ALL Product Studio (bugs) mirror Source Depot (source) mirror Developer Division 2005 – Limited 2007 – Most teams 2008 – ALL Product Studio (bugs) mirror Source Depot (source) mirror Office2007 – ALL – Planning & Bug Tracking SQL 2007 – ALL – Planning and Bug Tracking Investigating version control Windows 2007 – ALL – Planning Future - bug tracking MSIT 2005– Pilot. (Steady organic growth) 2008 – All active projects “There was a social issue around TFS adoption as well… We onboarded teams one at a time…. [The tool was so great] that as we came to recognize the flexibility in the tool, we essentially changed our process on the fly.” - Shoshanna Budzianowski, Product Unit Manager

48. When They MigratedMirrors VSTS 2003 – Very Limited (TFS) 2005 – Most teams 2006 – ALL Product Studio (bugs) mirror Source Depot (source) mirror Developer Division 2005 – Limited 2007 – Most teams 2008 – ALL Product Studio (bugs) mirror Source Depot (source) mirror Office2007 – ALL – Planning & Bug Tracking SQL 2007 – ALL – Planning and Bug Tracking Investigating version control Windows 2007 – ALL – Planning Future - bug tracking MSIT 2005– Pilot. (Steady organic growth) 2008 – All active projects “There was a social issue around TFS adoption as well [so] we on-boarded teams one at a time. [The tool was so great] that as we came to recognize the flexibility in the tool, we essentially changed our process on the fly.” -Shoshanna Budzianowski, Product Unit Manager

53. Task Lead & Process Time Savings Comments Dev Source Control 14.5% Working source control system requires less time. Dev Defect Resolution 11.6% Integrated tracking, defect tracking, and source control makes resolving issues faster and easier. Dev Reduction of Rework 6.7% Source control & build management saves substantial dev time spent reviews & inspections. Dev Automated Build 1.7% The build process time is shorter. Test Metric Reports 25% Creating test metrics requires much less time. Test Case Regression 21% Test regression suite analyzing and optimizing requires less time. Test Not Porting Docs 6% Not needing to port Word documents into defect tool saves time. Test Reactivated Bugs 6% Manual SQL query of reactivated defects is no longer necessary.

56. Agile Project Planning End to End Traceability Stunning New Reports 1-click Custom Excel reports New Dashboards Branch Visualization Distributed Build Build Windows Workflow Integration Test Planning Test Execution Manual Test Runner Test Impact Analysis Coded UI Test Historical Debugging Gated Checkin Activity Diagram Modeling Projects Logical Class Diagram Architecture Explorer Sequence Diagram Component Diagram Use Case Diagram Layer Diagram Scalability ++ TFS Administration w/MMC Database Edition merged into Development

57. Please fill out your evaluation for this session at: This session will be available as a recording at: www.microsoftpdc.com

59. © 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.