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.

• The iteration cycle should be long enough to allow team members to get substantial<br />

work done, and should cover at least a few different scenarios.<br />

• The iteration cycle should be short enough to flexibly accommodate changes and<br />

priorities.<br />

In practice, a two-week iteration cycle works for most projects.<br />

Additional Resources<br />

• For more information about iteration cycle duration, see “How To – Manage Projects<br />

in <strong>Visual</strong> <strong>Studio</strong> <strong>Team</strong> <strong>Foundation</strong> <strong>Server</strong>” in this guide.<br />

• For further information about iteration cycle duration, see “Chapter 11 – Project<br />

Management Explained” in this guide.<br />

Check-in Policies<br />

• Use check-in policies to enforce code quality.<br />

• Use check-in policies to ensure that developers associate work items <strong>with</strong> checkins.<br />

• Create check-in policies to enforce coding standards.<br />

• Set up notifications to inform you when developers bypass check-in policies.<br />

Use Check-in Policies to Enforce Code Quality<br />

Use a combination of code analysis and testing policies to improve check-in quality for<br />

your project. For example, use the supplied testing policy to ensure that specific tests are<br />

executed and passed prior to allowing source to be checked into Microsoft <strong>Visual</strong><br />

<strong>Studio</strong>® 2005 <strong>Team</strong> <strong>Foundation</strong> <strong>Server</strong> (TFS) source control. You can also configure a<br />

code analysis policy to help ensure that your code meets certain quality standards by<br />

ensuring that security, performance, portability, maintainability, and reliability rules are<br />

passed.<br />

By enforcing this type of check-in policy in addition to policies that enforce coding<br />

standards and guidelines, you ensure that your code meets a specific quality standard.<br />

To enforce a code analysis check-in policy for a team project<br />

1. In <strong>Team</strong> Explorer, right-click your team project, point to <strong>Team</strong> Project Settings, and<br />

then click Source Control.<br />

2. Click the Check-in Policy tab, click Add, and then select and configure the<br />

appropriate policy.<br />

Additional Resources<br />

• For more information about creating and using a custom check-in policy, see “How<br />

To – Step Through Creating Custom Check-in Policies for TFS” in this guide.

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

Saved successfully!

Ooh no, something went wrong!