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

Project Portal
| CMMI Process Area: Integrated Teaming collapse all
About Integrated Teaming |
###  |
Establish Team Composition |
Supporting Practices:
Identify Team Tasks |
Identify Needed Knowledge and Skills |
Assign Appropriate Team Members |
###  |
Govern Team Operation |
Supporting Practices:
Establish a Shared Vision |
Establish a Team Charter |
Define Roles and Responsibilities |
Establish Operating Procedures |
Collaborate Among Interfacing Teams |
###  |
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. Project Organization Chart Vision Document Persona Communication Plan Team Charter Document Meeting Minutes Shared Vision Evangelization 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. 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. 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?
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 |