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

Project Portal
| Set as Start page
| Build Engineer
collapse all
About Build Engineer |
Tracks
Governance |
Envision |
Planning |
Build |
Stabilize |
Deploy |
Operational Management |
Show All |
Workstreams and Activities |
Responsible Build a Product |  |
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 Requirement Task Review Bug
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. Test Approach Stakeholder Involvement Plan Iteration Plan Knowledge and Skills Plan Commitments Lessons Learned Improvement Suggestion Communication Plan Test Approach Threat Model Peer Review Exception Review Minutes Peer Review Checklist Shared Vision Evangelization Presentation Persona Load Test Web Test Manual Test Unit Test Changeset
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. Triage Provides an overall and by work item type count over time of work items in the Proposed state. 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. 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. Scenario Details Provides detailed information for each scenario including rank, overall status, linked developer tasks with status, risks with status, test tasks with status, and test cases with status. 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. Inconsistencies Report 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. Builds Provides a list of available builds, including detailed information on each. Bugs by Priority Are the correct bugs being found and triaged? Bugs reported by priority assess the effectiveness of two things: bug hunting and triage. Discovering bugs is a normal part of product development. Often however, the easy-to-find bugs are not the ones that will annoy customers the most. If the high-priority bugs are not being found and a disproportionate number of low-priority bugs are, redirect the testing efforts to look for the bugs that matter. In triage, it is easy to over-prioritize bugs beyond the capacity to resolve them, or under-prioritize them to the point where customers are highly dissatisfied.
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. 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. Development Tasks This query returns a status summary of all development tasks in the team project iteration. It includes links to each development task to facilitate detailed evaluation. Test Tasks This query returns a status summary of all test tasks in the team project iteration. It includes links to each test task to facilitate detailed evaluation. Resolved Bugs This query returns a list of bugs that are resolved.
Technical How To's |
How Tos present information on how to accomplish tasks related to activities and workstreams How to: Create a Bug How to: Reassign a Bug How to: Resolve a Bug
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |