TFS Adoption at Microsoft

It’s been 12 months since Brian blogged about Team Foundation Server adoption across all of Microsoft (not just Developer Division Dogfood Statistics). Since I’m now on the team responsible for internal adoption I’ll share some of the numbers that we publish every month.

  • The growth of unique active users across all TFS servers in August was 582, totaling 14,684 at Microsoft.

  • We’ve also surpassed 40 million source code files stored.

Now, for the summary of key growth indicators for the month:

July 2008



Unique Active Users



Total Active Users






Work Items



Source Code Files



Total Builds



We now have 27 TFS instances in production.  20 are running TFS 2008 RTM, 4 are running TFS 2008 SP1 Beta, 3 are running a preliminary Rosario build.  We’re in the process of upgrading the 2008 RTM + SP1 Beta instances to SQL 2008 RTM and TFS 2008 SP1.

This graph shows the number of active users per division within Microsoft. Each division is at a different stage of TFS adoption (Source control, Bug tracking, Feature tracking, Task tracking, Team Build, or any combination of each) which is why the numbers don’t correlate well with the size of the teams.

You may notice a ‘dip’ in the June/July numbers - Historically, we’ve reported a rollup of unique users per instance which is a true representation of instance activity but not unique users of TFS across the entire company.  For example, since MSIT has multiple instances of TFS, a single user may be working on projects on 2 or more separate instances.  The data now reflects unique users per division instead of per instance.

Active Users by Division

The number of team projects across all instances continues to grow at a steady rate of ~200 projects a month.

Total Team Projects

I hope you find this useful and if you have any other questions or numbers that you’d like to see, let me know and I’ll see what I can do.

Comments (3)
  1. Ted says:

    TFS works good for us developers but greatly lacks integration into an issue tracking, ticketing or help desk application that non developers have access to.  It is impractical and too costly for our business users (i.e, originators of requirements) to have a copy of TFS installed and learn how to use the developer tool.  This is the critical point where TFS is lacking.  Its current version puts all requirement and trouble ticket/bug tracking on the developer instead of receiving them in a feed from an enterprise capable ticketing, help desk, requirements tracking system.

  2. Llib says:

    What is your Team Project structure? Are you per App? per Release, per Team?

  3. Every month our internal teams put together statistics on the TFS servers deployed at Microsoft. Previous

Comments are closed.

Skip to main content