Working with Microsoft Visual Studio 2005 Team System (Pro-Developer)

Roles Within Team System

Remember that a role doesn't necessarily mean a person. In fact, it's doubtful that any team will exactly fit the Team System model, with every role covered perfectly and no overlap. As you read through this section, remember what I've been saying about the flexibility of Team System.

Here are the four Team System roles:

• Project Manager

• Architect

• Developer

• Tester

If you get creative, you can come up with a few more roles. For example, you can break the architect role into two subroles:

• Application Architect—designs software and services

• Infrastructure Architect—designs deployment environments, including network and infrastructure

Another role that is affected by Team System includes the IT professional (IT Pro) staff that will be asked to deploy the finished product into the environment. With that in mind, you can come up with some other pseudo and combination Team System roles:

• IT Professional—software deployment

• Tester/IT Professional—software testing and deployment

• Developer/Tester—software development and testing

• Application Architect/Developer—software design and development