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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Additional Resources<br />

• For more information about source tree structure, see “Chapter 5 – Defining Your<br />

Branching and Merging Strategy” in this guide.<br />

Work Items<br />

• Capture your scenarios at the start of your project.<br />

• Define your Quality of Service requirements appropriately.<br />

• Break scenarios into manageable, modular development tasks.<br />

• Set acceptance criteria for each task.<br />

• Link requirements and tasks to scenarios.<br />

• Use Microsoft Excel for bulk editing of work items.<br />

Capture Your Scenarios at the Start of Your Project<br />

Create and capture a set of project scenarios at the start of your project. This helps you to<br />

gain a complete picture of your project and can later be used track progress. During the<br />

course of development, you can modify existing scenarios or add new scenarios to<br />

represent what you learn over time.<br />

To capture scenarios at the start of the project<br />

1. Use the project back log (PBL) document, which is a requirement document based on<br />

input from various stakeholders (including customers, business analysts, end users,<br />

and product managers), and scope out the scenarios for your project.<br />

2. In <strong>Team</strong> Explorer, expand the project node, right-click the Work Items folder, point<br />

to Add Work Item, and then click Scenario.<br />

3. On the New Scenario page, enter the details for the scenario. Make sure to set the<br />

Iteration to Iteration 999.<br />

4. Save your new scenario.<br />

5. Repeat the above steps for all scenarios that you have identified for the project.<br />

Additional Resources<br />

• For more information about capturing scenarios, see “How To – Manage Projects in<br />

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

Define Your Quality of Service Requirements Appropriately<br />

Define your Quality of Service (QoS) requirements for each of the scenarios to be<br />

worked on during the iteration cycle. This helps to define the acceptance criteria for the<br />

scenario. The inputs for the QoS requirements come from project goals and requirements<br />

and specification documentation, if available.<br />

To define your QoS requirements<br />

1. Right-click your project’s Work Items folder, point to Add Work Item, and then<br />

click Quality of Service Requirements.<br />

2. On the New Quality of Service Requirements page, add the following details:

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

Saved successfully!

Ooh no, something went wrong!