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

Project Portal
| CMMI Process Area: Project Planning collapse all
About Project Planning |
###  |
Establish Estimates |
Supporting Practices:
Estimate the Scope of the Project |
Establish Estimates of Work Product and Task Attributes |
Define Project Life Cycle |
Determine Estimates of Effort and Cost |
###  |
Develop a Project Plan |
Supporting Practices:
Establish the Budget and Schedule |
Identify Project Risks |
Plan for Data Management |
Plan for Project Resources |
Plan for Needed Knowledge and Skills |
Plan Stakeholder Involvement |
Establish the Project Plan |
###  |
Obtain Commitment to the Plan |
Supporting Practices:
Review Plans That Affect the Project |
Reconcile Work and Resource Levels |
Obtain Plan Commitment |
###  |
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. Review Requirement 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. Deployment Plan Stakeholder Involvement Plan Iteration Plan Project Plan Knowledge and Skills Plan
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. Unplanned Work How much unplanned work is there? This graph distinguishes the total work from the remaining work and charts it into planned and unplanned. Very few projects identify all of the work to be done ahead of time, even within the iteration. This may be perfectly acceptable, if you schedule a sufficient buffer for handling the load of unplanned work (for example, bugs). On the other hand, it may be a real problem if you have not scheduled the capacity and are forced to cut back on the planned work. 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. 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. Customer Requirements This query returns all of the active customer requirements (scenarios and quality of service requirements) for the team project. This query can be used to generate a customer requirements list in Microsoft Excel. 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.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |