Overview |  | Roles |  | Work Items |  | Views |  | CMMI |  | Index |  | Glossary |

Project Portal
| CMMI Process Area: Validation collapse all
About Validation |
###  |
Prepare for Validation |
Supporting Practices:
Select Products for Validation |
Establish the Validation Environment |
Establish Validation Procedures and Criteria |
###  |
Validate Product or Product Components |
Supporting Practices:
Perform Validation |
Analyze Validation Results |
###  |
Step by Step |
Workstreams and Activities
Work Items |
A work item is a database record which Visual Studio Team Foundation uses to track the assignment and state of work. The MSF for CMMI® Process Improvement process defines seven work items to assign and track work. These seven work items are task, change request, risk, review, requirements, bug, and issue. Change Request Bug Requirement Task
Work Products Examples and Templates |
Work products are files, documents, specifications, binaries, parts, and other tangible items that are necessary to complete activities and build the product. Many times the creation of one work product is dependent on the completion of another work product. Manual Test
Report Examples |
Project health charts aggregate metrics from work items, source control, test results, and builds. They answer questions about the actual state of your project at many scales: for the days within an iteration, iterations within a project, or projects with in a program. The questions are also relevant for many kinds of work items such as scenarios, quality of service requirements, tasks, and bugs. Requirements Test History Requirements Test history shows the progress of system testing of product requirements (functional, operational, security, safety, interface) or user acceptance testing of customer requirements (scenarios and qualities of service) over the duration of the iteration. Bugs by Priority Are the correct bugs being found and triaged? Bugs reported by priority assess the effectiveness of two things: bug hunting and triage. Discovering bugs is a normal part of product development. Often however, the easy-to-find bugs are not the ones that will annoy customers the most. If the high-priority bugs are not being found and a disproportionate number of low-priority bugs are, redirect the testing efforts to look for the bugs that matter. In triage, it is easy to over-prioritize bugs beyond the capacity to resolve them, or under-prioritize them to the point where customers are highly dissatisfied. Triage Provides an overall and by work item type count over time of work items in the Proposed state. Test Failure Without Active Bug Identifies failed tests that do not have active bugs for tracking. It helps consolidate the iteration and release quality. Test Passing With Active Bug Identifies failed tests that still have active bugs. It helps reduce wasted effort.
Query Definitions |
MSF for CMMI Process Improvement provides a set of work item queries designed to support the activities and roles in the process. Active Bugs This query returns a list of all of your active bugs. This query can also be used to generate a Microsoft Excel spreadsheet of your bugs. It can be used at any point during the project once bugs have been written. Resolved Bugs This query returns a list of bugs that are resolved.
Technical How To's |
How Tos present information on how to accomplish tasks related to activities and workstreams How to: Create a Bug List
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |