In a previous post I stated the goals of successful configuration management and as you undoubtedly realized they are not easily accomplished in the field. Now I'll try to give you an insight on how Team System helps you to tame this untamable beast.
A good SCM process makes it possible for developers to work together on a project in an efficient manner, both as individuals and as members of a team. A development team must constantly manage requirements, tasks, source code, bugs and reports. Gathering each of these item types in the same tool strengthens the communication pathways of teams and software.
Based on the goals mentioned in the previous post on SCM I'll try to indicate how Team System helps you to accomplish them:
Process management: Enforces consistent processes and promotes user accountability across the application life cycle, resulting in communication and productivity improvements enterprise-wide. Team System will include two Microsoft Solution Framework(MSF) methodologies:
I hope that by now you will agree that Team System is the new do-it all tool in the SCM's toolbox. Team System is not a methodology or process but it integrates very well with the MSF methodology. Team System integrates most of the current tools that a Software Configuration Manager has dreamt about. Microsoft will provide third party tool providers and yourself with an SDK that allows you to take advantage of common functionality that Team System provides. Well, I cannot imagine a SCM that is not eagerly anticipating the release of Visual Studio 2005 Team System, but only time will tell.