Team Development with Visual Studio Team Foundation Server

For large teams, the branching structure is deeper, so you should expect a greater time lag
between a change in a development branch and the merging of that change into the main
integration branch.
Large teams are likely to have longer build times. The frequency of continuous
integration builds should be less than the build time to avoid too much queuing and
loading of the build server. If you are still having problems with build server
performance, consider using a build server for each branch in your source control
structure.
Additional Resources
• For more information about Team Foundation Source Control, see “Using Source
Code Control in Team Foundation” at http://msdn2.microsoft.com/enus/library/ms364074(VS.80).aspx
• For more information about creating a workspace, see “How To - Create a
Workspace” at http://msdn2.microsoft.com/en-us/library/ms181384(VS.80).aspx
• For an introduction to branching and merging, see “Branching and Merging Primer”
at http://msdn2.microsoft.com/en-us/library/aa730834(VS.80).aspx
• For more information about branching, see “How To - Branch Files and Folders” at
http://msdn2.microsoft.com/en-us/library/ms181425(VS.80).aspx
• For more information about merging, see “How To - Merge Files and Folders” at
http://msdn2.microsoft.com/en-us/library/ms181428(VS.80).aspx
• For additional descriptions of how to branch and merge in Visual Studio 2005, see
“Branching and Merging Team Foundation Source Control” at
http://msdn2.microsoft.com/en-us/library/ms181423(VS.80).aspx
• For more information about Team Build, see “Overview of Team Foundation Build”
at http://msdn2.microsoft.com/en-us/library/ms181710(vs.80).aspx