26.04.2015 Views

Team Development with Visual Studio Team Foundation Server

Team Development with Visual Studio Team Foundation Server

Team Development with Visual Studio Team Foundation Server

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Team</strong> Project per Application<br />

This is the most common strategy for creating team projects. This approach is useful for<br />

both large and small applications, as well as multiple releases of applications being<br />

developed in parallel. With this approach, you create one project for each application<br />

under development.<br />

<strong>Team</strong> Project per Release<br />

This approach is useful for large teams who are working on long-running projects. After<br />

every major release, you create a new project and have a clean start. With this approach<br />

you don’t have to worry about carrying the previous release’s baggage forward, including<br />

work items. Also, this approach provides you <strong>with</strong> the opportunity either to improve the<br />

process templates or use new ones based on your newly acquired experience and<br />

learning.<br />

<strong>Team</strong> Project per <strong>Team</strong><br />

This approach is useful for large projects that span multiple teams, where central control<br />

and activity monitoring is important. With this approach, you create a project for each<br />

team. This approach closely aligns a team <strong>with</strong> the workflows defined in TFS work item<br />

types and provides a unit of reporting that spans the entire team.<br />

Process Management<br />

With VSTS, the software development lifecycle has been made an integral part of the<br />

tooling to support software project development efforts. By integrating the lifecycle<br />

processes into VSTS, the process and handoffs for development team interaction are fully<br />

supported by the tooling and can be automated in many areas.<br />

Process Templates<br />

VSTS uses process templates to define the set of instructions and artifacts like process<br />

guidance documents, document templates, default work items etc, for setting up a new<br />

project. A process template is a self-contained set of instructions that provide<br />

development teams <strong>with</strong> the methodology for a software development initiative. A<br />

process template contains the following elements:<br />

• Process guidance. This is supplied for each template and provides contextual<br />

information, help, and direction for team members who need assistance following or<br />

understanding a particular activity. Process guidance is integrated into the <strong>Visual</strong><br />

<strong>Studio</strong> Help System.<br />

• Document templates. These templates enable team members to create new<br />

documents such as specifications, risks assessment and project plans in a consistent<br />

manner.<br />

• Work items and workflow. Work items have their own set of fields and rules that<br />

determine the workflow of the work item and how team members can assign and<br />

perform work.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!