Team Development with Visual Studio Team Foundation Server

Others
1. Capture any relevant tasks for the iteration for other disciplines – such as
Architecture, Release Management, Project Management and Requirements - which
needs to be tracked.
2. Link each of these tasks to the appropriate scenario for easier traceability.
For large projects that contain a huge number of work items, you can use the Microsoft
Office Excel® integration feature to create work items in an Excel spread sheet and then
upload it to TFS. For more information see “Working with Work Item Lists in Microsoft
Excel” at http://msdn2.microsoft.com/en-us/library/ms181694(VS.80).aspx
For large projects that contain a large number of resources, you can use the integration
feature in Microsoft Office Project to track the work items and balance task assignment.
For more information see “Working with Work Items in Microsoft Project” at
http://msdn2.microsoft.com/en-us/library/ms244368(VS.80).aspx
Step 10 – Monitor Progress
Each process template includes a set of reports that you can use to track project status and
health. Below are the default reports that you can use to monitor progress:
Bugs
The bug related reports enable you to see the kind of bugs being generated and fixed and
to spot trends. The following bug related reports are available:
• Bugs by Priority. Are the correct bugs being found? This report shows you the rate
of high priority bugs found vs. low priority. This report is both of the supplied
process templates.
• Bug Rates. How effectively are bugs being found, fixed and closed? This report
shows trends over time for new bugs, bug backlogs, and bug resolution. This report is
available in both of the supplied process templates.
Release Management
Release management reports enable you to judge how close your software is to being fit
for release. The following release management reports are available:
• Actual Quality versus Planned Velocity. How many scenarios can be completed
before quality is unacceptable? This report presents the relationship, for each
iteration, of estimated size to overall quality. This report is available in both process
templates.
• Builds. What is the quality of a build? This report provides a list of available builds
including build quality and other detailed information. This report is available in MSF
for CMMI Process Improvement.
• Quality Indicators. What is the quality of the software? This report collects test
results, bugs code coverage and code churn into a single report to track project health.
This report is available in MSF Agile and MSF CMMI.