As you know we are constantly looking at ways to improve our product in order to meet the growing market demands of our customers. Our enterprise customers today are looking to consolidate and usually decide to purchase one server for their teams and create a significant number of team projects in it.

The problem with this approach is that they lose some isolation capabilities (e.g. work item fields showing for all teams, changesets are interleaved across non-related projects) , and hit product limits (i.e. 500 team projects) relatively fast. In addition, management features like backup and restore of a "single team project" together with load balancing capabilities are a challenge in today's architecture.

Team Foundation Server started a series of investments in the TFS 2008 release and we are now planning the next major revision of the architecture by  focusing on a set of server framework services/components, encapsulation concepts and deployment/management tools that addressed the core market problems.

Our vision aligns with the Microsoft’s Promises to IT Professionals and Development Teams and it defines the direction for our current and future investments in the space.

Vision: Manage Complexity, Achieve Agility
Reduce the TCO of deploying, managing, and customizing TFS as an enterprise-wide service so IT departments can focus on delivering new business value

Today we are releasing the first of a series of specifications that have to do with this work. If you get a chance please spent some time reading it and tell us what you think:

Enterprise Team Foundation Server Management

You can find other specs located here: http://msdn2.microsoft.com/en-us/teamsystem/bb936702.aspx

If you do not post to our forum please feel free to drop me a line or send your feedback to mariorod@microsoft.com