1 / 60

Microsoft Visual Studio Team System Team Foundation Server: How We Use It at Microsoft

TL04. Microsoft Visual Studio Team System Team Foundation Server: How We Use It at Microsoft.  Stephanie Saad Group Program Manager Team Foundation Server. Two Major Adoption Profiles. Product Divisions Office, Windows, Developer Division, SQL. IT MSIT.

euclid
Télécharger la présentation

Microsoft Visual Studio Team System Team Foundation Server: How We Use It at Microsoft

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. TL04 Microsoft Visual Studio Team System Team Foundation Server: How We Use It at Microsoft  Stephanie Saad Group Program Manager Team Foundation Server

  2. Two Major Adoption Profiles Product Divisions Office, Windows, Developer Division, SQL IT MSIT

  3. Some Cool Facts about Microsoft Development

  4. Two Primary Uses > Dogfood * Product Development VSTS Usage At Microsoft • Raw Data > • ..21 TFS instances • ..VS 2008 in use since ‘05 • ..VS 2010 in use since ‘07 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. Developer Division • Largest instance at Microsoft

  6. Developer Division • 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. Developer Division • Largest instance at Microsoft 7 Terabytes of Data

  8. Developer Division • Largest instance at Microsoft 490,997Work Items

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

  10. Problems To Solve • Trustworthy Transparency • Planning and Tracking • Driving Quality during Development • Branching in Monster Teams • Legacy Interop

  11. Trustworthy Transparency The Challenge • Each team needs to optimize process differently for their needs • Leadership teams need central rollup to track progress The Solution • Hub-spoke federated model… • All teams use TFS for central tracking • Each team uses best process for its needs • Single reporting system

  12. VSTS Release Tracking 6-week iterations Iteration reviews Team Data Scrum Team Test Scrum TFS Modified Agile/XP Team Dev Modified Agile P&P XP & Scrum Team Arch Modified Agile

  13. Iteration Reviews – Business

  14. Iteration Reviews – Business

  15. Iteration Reviews – Business

  16. Iteration Reviews – Product Unit

  17. Iteration Reviews – Product Unit

  18. demo Effective Reporting

  19. Planning And Tracking The Challenge • Is the organization aligned? • How are we doing against biz objectives? • Are we making progress on the right things? The Solution • Traceability and Reporting • Create a hierarchy mapping requirements to work • Break down work into tasks • Track progress • Roll up status

  20. Our Process – VS 2008 • Main objectives • Scenarios • Value proposition • Value Props • Value Props • Experiences • Exp • Exp • Exp • Features • Feature • Feature • Feature • Feature

  21. Our Process Planning Main objectives • Scenarios Value proposition • Value Props • Value Props Experiences • Exp • Exp • Exp Features • Feature • Feature • Feature • Feature Work

  22. Value Proposition

  23. Feature

  24. Our Process – VS 2010 • Main objectives Pillars • Value proposition • Value Props • Value Props • Experiences Feature Groups Feature Groups Feature Groups • Features Deliverables Deliverables Deliverables Deliverables

  25. demo "Behind the Scenes": VSTS 2010 Planning

  26. Value Propositions • Deliverables

  27. Features • Deliverables

  28. Tracking Tasks In Microsoft Excel

  29. Tracking Tasks In Microsoft Project

  30. demo Planning And TrackingProject IntegrationExcel Integration

  31. Tracking Several Features

  32. Tracking Several Features

  33. Tracking Several Features

  34. Tracking Several Features

  35. Tracking Several Features

  36. demo More Reporting In VS 2010

  37. Driving Consistent Quality In Huge Teams The Challenge • Incredibly difficult to drive a release with 2,000 people. High degree of churn. Complex interdependencies. Inexorable schedule The Solution • “Feature Crews”: Carry no debt on features • All features merged are completely done • All meet stringent quality gates • Pay down debt up front and carry no debt forward • Use central tracking to shut down

  38. VS 2005 Debt VS 2005 Bug Stepdown at Beta 1

  39. “Feature Crews” Model • Carry no debt in feature development • Feature Must Pass “Quality Gates” on Finish before • Feature complete • Test Complete • All Bugs Fixed • Security Plan • Static Code Analysis • Code Coverage • No Performance Regressions • Localization Testing • API Reviews • Feature may merge to active branch only when Quality Gates are met

  40. Quality Gates

  41. Did It Work… ??

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

  43. Effective Branch Strategies The Challenge • Massive division – 2,000+ people • Code churning at every level The Solution • Isolation and Integration • Isolate major feature areas in branches • Automate branch quality checks • Rhythm of regular merges • Handles integration complexity

  44. Source/Branch Structure • 1 branch per product • Gated checkin procedure • VBLs build in parallel • Nightly test suites verify branch health • Regular schedule for merges • Stringent criteria for merges to main $/DEV10/Main $/DEV10/PU/ <BranchName> $/DEV10/PU /<BranchName> $/DEV10/feature/ <BranchName> $/DEV10/feature/ <BranchName>

  45. demo Gated CheckinBranch/Merge Visualization

  46. Migration and Legacy Interop The Challenge • I have tools in place already. I WILL NOT disrupt my shipping releases. How should I switch? When should I switch? Should I switch? The Solution • Legacy Interop and Phased Migration • Assess needs and plan migration • Migrate at natural breaks in the development lifecycle • Create mirroring with legacy tools as needed

  47. Migration History of “Big Five” “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. Migration History of “Big Five” • “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

  49. Sync Tools and Solution Providers Tools: • Visual Source Safe Migration Tool • Rational ClearCase Migration Tool • Rational ClearQuest Migration Tool • HP Quality Center Bug Sync Tool • Migration Toolkit Solution Providers: • Notion Solutions • Accentient • Persistent Systems

  50. announcing HP Quality Center Connector

More Related