Team System has several tools that were designed out of the box to work in a distributed environment. These include Team Foundation Version Control, the load agent and controller, and Team Foundation Build. This next section looks at each one of these tools and how to deploy them in your development environments.
A large part of the implementation of distributed teams is standardization. By standardizing development, testing, and project management practices, your team will get benefits such as predictability and productivity. Another advantage is that your project assets will be easier to manage, therefore cutting down on costs and effort. When deploying Team System, an important part of the process is reexamining the way software is developed from an end-to-end perspective.
Shared repositories can help in the standardization process. To share resources, you need software that allows you to connect across corporate firewalls and networks, and you need to establish standards and practices. The Internet-connected software has to provide great performance across wide topologies.
Another advantage with a shared repository will provide your entire team with up to date information about your project. Several different types of repositories are used in a distributed environment:
Workflow—Every team member can benefit from connecting from a common Team Foundation Server. As requirements change and specifications need to be updated ...