Threats
Threats are uncertain events or conditions that, if they occur, will harm the project or hinder achievement of its objectives.
Key Points
- They are the negative side of risk; the positive side is called opportunities.
- Analyze each threat by likelihood and impact, then prioritize in the risk register or risk backlog.
- Common response strategies include avoid, mitigate, transfer, and accept.
- In agile teams, track threats frequently using a risk-adjusted backlog or a risk burndown chart.
Example
A project depends on a third-party API that may be rate-limited during peak season. This uncertainty could delay integration and the release date, so the team plans mitigations such as caching, a fallback provider, and extra test stubs.
PMP Example Question
During sprint planning, the team learns a supplier might deliver a critical component two weeks late. How should this be classified?
- A potential threat that could negatively affect schedule objectives
- An opportunity to increase project value
- An issue that must be escalated immediately
- An assumption that reduces uncertainty
Correct Answer: A - threat (a negative risk)
Explanation: The delay is an uncertain event that could harm schedule performance, so it is a threat. It is not an opportunity, not an issue because it has not occurred yet, and not an assumption.
