Team Development with Visual Studio Team Foundation Server

• Work items
• Groups and permissions
• Source control
• Areas and iterations
• Reports
• Portal
The following sections detail the important defaults available to you when using the MSF
Agile process template.
Work Items
The MSF Agile process template contains the following work item types:
• Bug. Represents a problem or potential problem in your application.
• Risk. Represents a possible event or condition that would have a negative impact on
your project.
• Scenario. Represents a single path of user interaction through the system you are
building.
• Task. Identifies a specific item of work for a team member to perform.
• Quality of Service Requirement. Represents a non-functional requirement such as a
security, performance or manageability requirement.
When you create a new team project based on the MSF Agile process template, the
following work items are created for you. This saves you work by providing you with a
common set of tasks that you need to perform at project initiation.
• Set up: Set Permissions. The purpose of this task is to add team members to one of
the four security groups: Build Services, Project Administrators, Contributors, or
Readers.
• Set up: Migration of Source Code. The purpose of this task is to migrate your
existing source code from Microsoft Visual SourceSafe®, if you are moving an
existing project to Microsoft Visual Studio Team Foundation Server (TFS). You
should complete migration of source code before you grant team members access to
the team project.
• Set up: Migration of Work Items. If you are bringing an existing project into TFS,
you can migrate work items such as bugs and tasks from Clearquest or a commaseparated
value (CSV) file. You should complete this migration of work items before
you grant team members access to the team project.
• Set up: Set Check-in Policies. The purpose of this task is to setup the business rules
or policies that surround source code check-ins.
• Set up: Configure Build. The purpose of this task is to create an initial source tree
and set up the build to run on a periodic (usually daily) basis.
• Set up: Send Mail to Users for Installation and Getting Started. The purpose of
his task is to send an e-mail to team members that provides information about which