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

Project Portal
| CMMI Process Area: Organizational Innovation and Deployment collapse all
About Organizational Innovation and Deployment |
###  |
Select Improvements |
Supporting Practices:
Collect and Analyze Improvement Proposals |
Identify and Analyze Innovations |
Pilot Improvements |
Select Improvements for Deployment |
###  |
Deploy Improvements |
Supporting Practices:
Plan the Deployment |
Manage the Deployment |
Measure Improvement Effects |
###  |
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. Issue
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. Operations Review Presentation
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. Remaining Work How much work is left to be done, and when will it be completed? This cumulative flow diagram shows work remaining in tasks on the iteration backlog as a cumulative inventory of active, resolved, and closed tasks. Velocity How quickly is the team completing work? Velocity is one of the key elements for estimation. It shows how quickly the team is actually completing planned work, and how much the rate varies from day-to-day, or iteration-to-iteration. Use this data to plan the next iteration, in conjunction with the quality measures. Similar to the remaining work chart, this is most useful when looking at days within an iteration or iterations within a project. 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. Reactivations How many work items are being reactivated? Reactivations are work items that have been resolved or closed prematurely. A low rate of work item reactivations (for example, less than 5%) might be acceptable, but a high or rising rate of reactivation should warn the project manger to diagnose the root cause and fix it. Actual Quality versus Velocity How many scenarios can be completed before quality is unacceptable? As much as teams believe the saying "haste makes waste," there is usually a business incentive to go faster. A project manager’s goal ought to be to balance the two by finding the maximum rate of progress that does not make quality suffer. This graph presents the relationship, of estimated size to overall quality for each iteration. 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? Regressions Provides a list of tests that have passed previously that now fail.
Query Definitions |
MSF for CMMI Process Improvement provides a set of work item queries designed to support the activities and roles in the process. 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.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |