Everything you want to know about Visual Studio ALM and Farming
Brian Harry is a Microsoft Technical Fellow working as the Product Unit Manager for Team Foundation Server. Learn more about Brian.
More videos »
It’s been a while now since I have an overall look at the adoption of TFS at Microsoft. I decided to go ahead and do it this month even though some of the numbers (particularly active users) are a bit skewed by the recent holidays. Regardless, there’s some good data here. One big milestone that we passed recently is more than 50,000,000 distinct source files being managed across the deployment. We have 27 TFS instances in production.
Here’s some charts to show how things are going…
Brian
You guys can not make product like sub version. Everything need to be connected all the time. disconnect from source control is missing from the day one.
Thanks for the update Brian, it's a very interesting watching the evolution of the MS TFS usage. Particularly since I'm working in a company with high TFS usage.
I'm interested in finding out more about how the clustering of TFS is done, would you consider doing some more in-depth posts on that?
Yep i agree with Aaron. An overview of your technical set up that supports 15k active users would be great!
Scott Dorman on Microsoft Test and Code Coverage Brian Harry on Microsoft TFS Adoption Update Steve St
I know of an architect who has for some time been proclaiming that the Team Foundation Server solution
subversion user: Please do your homework and know your facts before talking.
We're reluctant to buy TFS for VSS's default autocheckout on modify problem.
This has caused large problems for us with offshore development teams that insist on always checking in each and every file that is modified whether or not it needs to be checked in including many many files that have tabs/spaces changed or extra unneeded blanks added to the end of source files.
More importantly, TFS does not integrate with a corporate wide help desk/ticketing system including receiving tickets from the system and sending/updating tickets in the system. This prevents us from using TFS for our own internal ticketing as our end users aren't developers and don't need a TFS install/license. This point is quite lost on developers that have never worked with an enterprise wide ticketing/help desk/requirements/customer support system.
We can get our end users to use a corporate wide ticketing system for requirements, external customer support, bug tracking, help desk tickets but could not possibly get them to use TFS. This lack of corporate wide benefit to non-developers prevents us from even beginning to build a business case for TFS adoption.
What is the current situation relating to TFS CALS for "periferal" users of TFS, e.g. users reporting bugs, managers viewing reports/lists of outstanding tasks etc?
The situation is unchanged. In general, everyone requires a CAL to access TFS in any form. In TFS 2008, we added one exception to that. People can file bugs and view the status of bugs they filed without a CAL.