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

Project Portal
| Risk
### Work Item Database
Overview |
States and Transitions |
Fields |
### Process Guidance |
Activities |
Workstreams |
Risk Fields Risk work items document a probable event or condition that can have a potentially negative outcome on the project in the future. An essential aspect of project management is to identify and manage the inherent risks of a project. If a risk is assigned for mitigation, it becomes Active. The risk remains active until the mitigation actions are complete, at which point, the risk is resolved. If a resolved risk is verified to be completely mitigated, it is then closed. If at any point the event identified by the risk occurs, the risk becomes an issue and a contingency plan is enacted.
Field | Description
--- | ---
Title | Required. The title provides a concise overview of the risk that may occur. The title should be descriptive enough to allow the team to understand what the potential risk is.
Area Path | Used to group the risk into an appropriate feature or team area. The area must be a valid node in the project hierarchy.
ID | The unique identifier used to identify the task. Team Foundation Server automatically creates the ID when the work item is created.
Assigned To | The current person that the risk is assigned to. Generally, it is a project manager or an architect but may be any of the project team members.
Severity | The severity is a subjective ranking of the magnitude of adverse effects, such as cost and loss, should the risk be realized within the project. Valid values are Critical, High, Medium, or Low.
Probability | The likelihood that the risk will occur. Percentage is a number between 1 and 99.
Reason | The reason a risk is in the current state. For example, a risk can be in the Closed state because it was Avoided.
State | Required. A risk is in the Proposed, Active, Resolved, or Closed states.
Mitigation Plan | The actions to take to reduce the likelihood of the risk, or impact of the risk. The mitigation plan is assigned and tracked through tasks.
Mitigation Triggers | The conditions or events that determine that a risk should be mitigated. For example, if the weather forecast is predicting an ice storm or hurricane to hit within 50 miles of the office, within the next 4 days, it may be appropriate to authorize and obtain a reserve generator.
Contingency Plan | The actions to take in the event the risk occurs. The contingency plan is assigned and tracked through an issue work item and tasks.
Attachments | Contains the files that have been attached to the risk.
Mitigation Estimate | An estimate of how much work is involved to implement the mitigation plan.
Created By | Identifies who created the risk.
Created Date | Identifies when the risk was created.
Changed By | Identifies the person who last made a change to the risk.
Changed Date | Identifies the date the risk was last changed.
Closed By | Identifies the person who closed the risk.
Closed Date | Identifies the date the risk was closed.
Description | A description of the proposed action to mitigate the risk.
Remaining Work | An estimate in person hours of the work remaining to complete the mitigation action.
Completed Work | An estimate in person hours of the time spent to date to complete the mitigation action.
Priority | The priority is a subjective importance rating. Valid values are 1, 2, and 3 (default).
Blocked | Indicates if progress on completing the mitigation action has been blocked. If an Issue work item has been opened to track the blocking problem, a link should be made to that work item as well.
History | This history is a running discussion about the risk that accumulates additional written entries as changes are made. Each time a change is made to the risk, an entry is made in the History field describing what change was made and why, as well as any additional pertinent information about the change.
Links | This field shows the other work items that have been linked to the risk. In the case of a risk, tasks for mitigating the risk should be linked to the risk work item.
Iteration Path | The Iteration Path identifies in which iteration the bug will be fixed.
Resolved By | Identifies who resolved the risk. This information appears in the History field and not in its own field.
Resolved Date | Identifies when the risk was resolved. This information appears in the History field and not in its own field.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |