Microsoft Visual Studio Team System Team Foundation Server: How We Use It at Microsoft Stephanie Saad Group Program Manager Team Foundation Server TL0 4
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Microsoft Visual Studio Team System Team Foundation Server: How We Use It at Microsoft
Stephanie SaadGroup Program ManagerTeam Foundation Server
TL04
Two Major Adoption Profiles
Product Divisions
Office, Windows, Developer Division, SQL
IT
MSIT
Some Cool Facts about Microsoft Development
VSTS Usage At Microsoft
Two Primary Uses >1. Dogfood * 2. Product Development
Users Projects Work Items Source Files Builds
VS 2008 13,106 2,494 2,568,420 40,790,715 464,879
VS 2010 1,569 14 183,018
Total 14,675 2,508 2,751,438 40,790,715 464,879
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 wil l quickly learn what's missing or broken.
Developer Division
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
Builds 7,971
Largest instance at Microsoft
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
Builds 7,971
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)
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
Builds 7,971
Developer Division
7 Terabytes of Data
Largest instance at Microsoft
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
Builds 7,971
Developer Division
490,997Work Items
Largest instance at Microsoft
If all
373,328,986 source files were printed,
they would wrap the Earth2.6 times
Problems To Solve Trustworthy Transparency Planning and Tracking Driving Quality during Development Branching in Monster Teams Legacy Interop
The Challenge
The Solution
Trustworthy Transparency
Each team needs to optimize process differently for their needs
Leadership teams need central rollup to track progress
Hub-spoke federated model… All teams use TFS for central tracking Each team uses best process for its needs Single reporting system
VSTS Release Tracking
6-week iterationsIteration reviews
Team ArchModified Agile
Team DevModified Agile
Team DataScrum
Team TestScrum
TFSModified Agile/XP
P&PXP & Scrum
Iteration Reviews – Business
Iteration Reviews – Business
Iteration Reviews – Business
Iteration Reviews – Product Unit
Iteration Reviews – Product Unit
Effective Reporting
demo
The Challenge
The Solution
Planning And Tracking
Is the organization aligned? How are we doing against biz objectives? Are we making progress on the right things?
Traceability and Reporting Create a hierarchy mapping requirements to work Break down work into tasks Track progress Roll up status
Our Process – VS 2008
Features
Experiences
Value proposition
Main objectives Scenarios
Value Props
Exp
Feature Feature
Exp
Feature
Value Props
Exp
Feature
Features
Experiences
Value proposition
Main objectives Scenarios
Value Props
Exp
Feature Feature
Exp
Feature
Value Props
Exp
Feature
Our ProcessPlanning
Work
Value Proposition
Feature
Our Process – VS 2010
Features
Experiences
Value proposition
Main objectives Pillars
Value Props
Feature Groups
Deliverables Deliverables
Feature Groups
Deliverables
Value Props
Feature Groups
Deliverables
"Behind the Scenes": VSTS 2010 Planning
demo
Value Propositions
Deliverables
Features
Deliverables
Tracking Tasks In Microsoft Excel
Tracking Tasks In Microsoft Project
Planning And TrackingProject IntegrationExcel Integration
demo
Tracking Several Features
Tracking Several Features
Tracking Several Features
Tracking Several Features
Tracking Several Features
More Reporting In VS 2010
demo
The Challenge
The Solution
Driving Consistent Quality In Huge Teams
Incredibly difficult to drive a release with 2,000 people. High degree of churn. Complex interdependencies. Inexorable schedule
“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
VS 2005 Debt
VS 2005 Bug Stepdown at Beta 1
“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
Quality Gates
Security plan
Static code analysis
Code coverage
No performance regressions
Localization testing
API reviews
All bugs fixed
Did It Work… ??
2005 Debt Verses 2008 DebtVS 2005 Beta 1
Product Bugs onlyVS 2008 Beta 1ALL bug debt
The Challenge
The Solution
Effective Branch Strategies
Massive division – 2,000+ people Code churning at every level
Isolation and Integration Isolate major feature areas in branches Automate branch quality checks Rhythm of regular merges Handles integration complexity
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/feature/<BranchName>
$/DEV10/PU/<BranchName>
$/DEV10/feature/<BranchName>
Gated CheckinBranch/Merge Visualization
demo
The Challenge
The Solution
Migration and Legacy Interop
I have tools in place already. I WILL NOT disrupt my shipping releases. How should I switch? When should I switch? Should I switch?
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
Migration History of “Big Five”
When They Migrated Mirrors
VSTS2003 – Very Limited (TFS)2005 – Most teams2006 – ALL
Product Studio (bugs) mirrorSource Depot (source) mirror
Developer Division2005 – Limited2007 – Most teams2008 – ALL
Product Studio (bugs) mirrorSource Depot (source) mirror
Office 2007 – ALL – Planning & Bug Tracking
SQL 2007 – ALL – Planning and Bug Tracking Investigating version control
Windows 2007 – ALL – PlanningFuture - bug tracking
MSIT 2005– Pilot. (Steady organic growth)2008 – All active projects
Migration History of “Big Five”
When They Migrated Mirrors
VSTS2003 – Very Limited (TFS)2005 – Most teams2006 – ALL
Product Studio (bugs) mirrorSource Depot (source) mirror
Developer Division2005 – Limited2007 – Most teams2008 – ALL
Product Studio (bugs) mirrorSource Depot (source) mirror
Office 2007 – ALL – Planning & Bug Tracking
SQL 2007 – ALL – Planning and Bug Tracking Investigating version control
Windows 2007 – ALL – PlanningFuture - 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
Sync Tools and Solution ProvidersTools: 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
HP Quality Center Connector
announcing
TFS HP Quality Center Connector
Full Defect Synchronization
Administration: GUI & Command Line
Pre-Release on Microsoft Connect
Contact Product Teams for more information ([email protected])
“I can’t imagine what we’d do if you pulled [TFS] away…”
“I think what TFS doesblows CVS away.”
Michael Lucas, Senior PM, MSIT
MSIT Development Benefits
TaskLead & 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.
Slides And Demos
http://blogs.msdn.com /StephanieSaad
Summary
We’ve had a lot of the same problems you may have. We’ve rolled learnings into TFS.
Trustworthy Transparency Planning and Tracking Driving Quality during Development Branching in Monster Teams Legacy Interop
Visual Studio Team System 2010
Agile Project Planning
End to End TraceabilityStunning New Reports
1-click Custom Excel reports
New Dashboards
Branch Visualization
Distributed Build
Build Windows Workflow Integration
Test PlanningTest Execution
Manual Test RunnerTest Impact
Analysis
Coded UI Test
Historical Debugging
Gated Checkin
Activity Diagram
Modeling ProjectsLogical Class Diagram
Architecture ExplorerSequence Diagram
Component Diagram
Use Case DiagramLayer Diagram
Scalability ++
TFS Administrationw/MMC
Database Edition merged into Development
Evals & Recordings
Please fill
out your
evaluation for
this session at:
This session will be available as a recording at:
www.microsoftpdc.com
Please use the microphones provided
Q&A
© 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.
Related Documents
