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

Project Portal
| CMMI Process Area: Integrated Project Management for IPPD collapse all
About Integrated Project Management for IPPD |
###  |
Use the Projects Defined Process |
Supporting Practices:
Establish the Projects Defined Process |
Use Organizational Process Assets for Planning Project Activities |
Integrate Plans |
Manage the Project Using the Integrated Plans |
Contribute to the Organizational Process Assets |
###  |
Coordinate and Collaborate with Relevant Stakeholders |
Supporting Practices:
Manage Stakeholder Involvement |
Manage Dependencies |
Resolve Coordination Issues |
###  |
Use the Projects Shared Vision for IPPD |
Supporting Practices:
Define Projects Shared-Vision Context |
Establish the Projects Shared Vision |
###  |
Organize Integrated Teams for IPPD |
Supporting Practices:
Determine Integrated Team Structure for the Project |
Develop a Preliminary Distribution of Requirements to Integrated Teams |
Establish Integrated 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. Change Request 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. Meeting Minutes
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. Triage Provides an overall and by work item type count over time of work items in the Proposed state. 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. 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. 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 |