HKSM

Risks that the Scrum Team has reduced to an acceptable level by executing planned responses during the project.

Key Points

• Mitigation lowers a risk's probability, impact, or both to an agreed acceptable level.
• Actions are planned, implemented, and tracked by the Scrum Team as part of ongoing risk management.
• Residual risk may remain and should be monitored and reassessed regularly.
• Common tactics include design changes, tests, controls, spikes, buffers, and process improvements.

Example

During Sprint 3, the team identifies a risk that a third-party API might throttle requests, slowing user logins. They implement caching, retries with backoff, and a circuit breaker. After testing, the likelihood and impact are both reduced, and the risk is marked as mitigated and monitored for residual effects.

PMP Example Question

In an agile project, the team adds rate limiting and a circuit breaker to handle potential API throttling. The risk's probability and impact are now low and recorded as such. What best describes this risk?

1. Accepted risk
2. Mitigated risk
3. Transferred risk
4. Issue

Correct Answer: B — Mitigated risk

Explanation: The team implemented actions that reduced the likelihood and/or impact to an acceptable level, which is mitigation.