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.

Figure 12.2 Transition States for MSF Agile<br />

Customizing Work Items<br />

There are a few scenarios in which you may want to modify the work item types defined<br />

in MSF Agile or MSF CMMI:<br />

• A work item is missing a field that is important for your development process.<br />

• A work item workflow does not match how your team works.<br />

• You need a new work item type.<br />

To support these scenarios, you can do the following in TFS:<br />

• Add/remove work item types.<br />

• Modify fields in existing work items.<br />

• Modify states and transitions in existing work items.<br />

For more information about customizing work items, see “How To: Customize a Process<br />

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

Summary<br />

Work items are used by project managers and team leaders to track the work to be done<br />

on a project. They are used to create development tasks to represent the work that must<br />

be completed, create bugs to represent defects in the implementation and create user<br />

requirements or Quality of Service (QoS) requirements. Additionally they can be used to<br />

track development and testing against requirements, and to determine the quality of the<br />

application and its readiness to be shipped.<br />

The MSF Agile and MSF CMMI process templates provide a set of default work item<br />

types. You can customize these or create new work item types to meet your process<br />

requirements.

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

Saved successfully!

Ooh no, something went wrong!