Development and Team System

The developer advocates for the development constituency in the MSF Team Model. The developer is responsible for the bulk of the work of building the product. Other development roles such as the lead developer and development manager have additional communication and project management responsibilities. The developer should suffer a minimum of communication overhead allowing for a maximum effort on construction of code. In addition, during the early stages of a project, developers may be expected to help specify product requirements not included in the customer requirements and to work on analysis and architecture activities as part of a multi-disciplinary team. A lead developer's role is to lead and to communicate on behalf of other developers. A lead developer advocates for the development constituency in the MSF Team Model. A lead developer lends experience and skill and shows leadership by coaching fellow developers. Lead developers carry responsibility for code reviews, design, and unit testing coverage. Lead developers act as a conduit to the rest of the project for the developers. As an aid to productivity, lead developers funnel communications between the wider project team and external organizations, and shield developers from noise and random interference in their daily schedules. Because of this, lead developers can seldom dedicate themselves to development tasks. Typically, they spend about 50% of their time on communication and split the remainder between leading and coaching the developers on their team, and actually writing code for development tasks.

The development workflow is as follows:

  • Analysis

  • Create Solution Architecture

  • Develop Documentation

  • Establish Environments

  • Establish Project Process

  • Fix a Bug

  • Implement a Development Task

  • Release a Product

  • Test a Customer Requirement

  • Verify a Product Requirement

Also listed here are links to help developers adopt the workflow for the MSF Team Model using Microsoft Visual Studio 2005 Team System.

Process Guidance

Working with Team Projects

Working with Work Items

Working with Source Control

Work Items

Files

Workspaces

  • How to: Edit a Workspace
    Describes how to edit an existing workspace to change the name, comments, or working folders.

Changesets and Pending Changes

Shelving

Branching and Merging

Labels

Working with Team Foundation Build

  • Using Test Lists
    Describes how to run build verification tests as part of a build.

Monitoring and Reporting

Working with Team Edition for Developers

This page contains links to popular topics for getting started with Distributed System Designers in Visual Studio Team Edition for Architects. To view other categories of popular topics, see How Do I in Team Edition for Developers.