A Risk records an uncertain event or condition and its potential consequences. It supports assessment and response planning so the team can review what might affect product or project work.
When to use it
- Use it for a potential problem that may affect delivery, performance, or another objective.
- Use it when likelihood, impact, mitigation, and follow-up need to be tracked together.
Key information
- Identity and assessment: risk ID, name, description, likelihood, severity, and potential impact.
- Response: mitigation strategies, response strategy, contingency plan, and actions.
- Review: assessment date, current mitigation status, and residual risk.
Common relationships
- Risk links a Project, Product, Requirement, or other eligible record to the risk.
- Change – Risk associates a change record with relevant risk information.
- Risk – Impact connects the risk to an Enterprise Change Assessment.
Working with this record
Describe the uncertain event, the consequence, and the response clearly. Use the assessment scale agreed by your organization. Update mitigation and review information as conditions change; a recorded response does not establish that the risk has been removed.
Example
Supplier Delay is a Risk connected to Pump Redesign. The team describes the possible schedule impact, records its likelihood, and tracks a contingency plan. The project team reviews the remaining risk as the supply situation changes.
Choosing the right type
Choose Risk for uncertainty about a potential event. Choose Issue or Problem Report when a problem has been observed. Use a Task to assign a specific mitigation activity when that work needs separate tracking.
