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

Project Portal
| Set as Start page
| Infrastructure Architect
collapse all
About Infrastructure Architect |
Tracks
Governance |
Envision |
Planning |
Build |
Stabilize |
Deploy |
Operational Management |
Show All |
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. Issue Task Change Request Risk
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. Improvement Suggestion
Report Examples |
xxx Brief description... xxx Brief description... 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. Open Issues and Blocked Work Items Trend How many issues are open in the issue log and what has been the trend in open issues throughout the iteration? Unresolved open issues can cause work items to block and consequently schedules to slip. How many work items are currently blocked and what has been the trend in blocked worked items? Triage Provides an overall and by work item type count over time of work items in the Proposed state. Quality Indicators What is the quality of the software? Ideally, test rates, bugs, and code churn would all produce the same picture, but often they do not. When you find a discrepancy, you need to examine in further detail the appropriate build and data series. This graph combines the test results, code coverage from testing, code churn, and bugs, to help you see many perspectives at once. Bug Rates How effectively are bugs being found, fixed, and closed? Bug rates are best interpreted relative to all of the current team project activities and the other metrics on the Quality Indicators graph. For example, a high find-rate may be a sign of poorly written code, newly integrated code, effective testing, or exceptional events such as a bug bash. On the other hand, a low find rate may mean high quality product or ineffective testing. Use code coverage, code churn, and test rates to help you assess the meaning.
Query Definitions |
MSF for CMMI Process Improvement provides a set of work item queries designed to support the activities and roles in the process. Blocked Work Items This query returns a summary list of all blocked work items in the team project iteration. It includes links to each work item to facilitate detailed evaluation. Issues This query returns a summary list of all issues in the team project iteration. It includes links to each issue to facilitate detailed evaluation. Corrective Actions This query returns a summary list of all corrective actions in the team project iteration. It includes links to each corrective action to facilitate detailed evaluation. Change Requests This query returns a summary list of all change requests in the team project iteration. It includes links to each change request to facilitate detailed evaluation. Risks This query returns a summary list of all risks in the team project iteration. It includes links to each risk to facilitate detailed evaluation. Mitigation Action Status This query returns a status summary of all mitigation actions in the team project iteration.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |