Visual Studio Team System Targets Multiple Roles

With Visual Studio 2005 Team System (VSTS), Microsoft is moving beyond its traditional strength in the core development process (edit-compile-debug) to offer tools that it previously left to third parties. These tools will help with the earlier parts of the life cycle (design and architecture), as well as the later parts (testing and deployment). Its integration with the rest of Visual Studio (VS) makes VSTS worth a look for many IT organizations, but those already using competing products, such as those from Mercury or IBM/Rational, may find that competing products provide more comprehensive features.

This article provides an overview of how VSTS supports various roles in the software development process. Future articles will provide detailed coverage of features in each of the areas.

Four Roles

Many formalized methodologies attempt to apply structure to the software development process. In addition, many software development organizations employ home-grown methodologies based upon the specific skills and abilities of their staff or their historical experience. Examples of the roles commonly used in both formal and informal methodologies include the following: