Residual and Accepted Risk
Residual and Accepted Risk are risks left after mitigation and intentionally accepted in Agile projects.
Residual and Accepted Risk refers, respectively, to the portion of a risk's original exposure that remains even after mitigation or other response actions have been applied, and to a deliberate decision to knowingly proceed without further action against a risk, whether because its residual level is judged tolerable or because the available responses are not justified relative to the risk's actual significance. Both concepts describe risk that the project consciously carries forward rather than eliminates, and distinguishing between them, while managing each deliberately, is an essential closing element of a mature Agile Risk and Uncertainty Management practice.
Understanding Residual Risk
What Remains After Response
Residual risk is the exposure that persists after a chosen response strategy, most commonly mitigation, has been applied, reflecting the reality that most response actions reduce rather than completely eliminate a risk's likelihood or impact.
Why Residual Risk Is Rarely Zero
Because mitigation actions target specific contributing factors rather than every conceivable pathway to a risk's occurrence, and because some uncertainty is often inherent to complex work, a genuinely zero level of residual risk is uncommon even after thorough mitigation effort.
The Importance of Explicitly Assessing Residual Risk
Simply having applied a mitigation action does not by itself indicate how much risk remains; residual risk requires its own explicit reassessment following mitigation, distinct from the original assessment made before any response was applied.
Understanding Accepted Risk
A Deliberate, Conscious Decision
Accepted risk arises from a deliberate decision to proceed without further mitigation against a specific risk, made consciously and with awareness of the potential consequences, distinguishing it clearly from a risk that is simply overlooked or forgotten.
Common Reasons for Acceptance
A risk is often accepted when its assessed likelihood and impact are low enough that further response is not justified relative to its actual significance, or when the cost of any available mitigation substantially exceeds the risk's potential harm.
Acceptance Applied to Both Original and Residual Risk
Acceptance can apply either to an original risk for which no mitigation is pursued at all, or to the residual risk remaining after mitigation has already been applied and further reduction is judged not worthwhile relative to its remaining cost.
Why Distinguishing the Two Matters
Different Origins, Same Practical Consequence
Both residual risk and accepted risk represent exposure the project continues to carry, but they arise from different circumstances — one from the limits of an applied response, the other from a deliberate choice not to respond further — and recognizing this distinction helps clarify why a given level of exposure remains.
Avoiding Confusion Between Unaddressed and Deliberately Accepted Risk
Without a clear distinction, it becomes difficult to tell whether remaining exposure reflects a genuine, considered decision or simply an oversight where the risk was never adequately addressed, a difference that matters significantly when later evaluating whether the team's risk management was sound.
Practices for Managing Residual and Accepted Risk
Explicitly Documenting the Decision to Accept
When a risk or its residual portion is accepted, this decision, along with its rationale, is recorded explicitly, providing a clear record that the exposure was consciously chosen rather than simply left unaddressed by default.
Continuing to Monitor Accepted Risk
Acceptance does not mean a risk is removed from ongoing attention; accepted risks typically remain under monitoring, since the conditions that justified acceptance can change, potentially warranting a different response later.
Periodic Review of Acceptance Decisions
Because circumstances evolve, previously accepted risks are periodically reconsidered to confirm that acceptance remains the appropriate response, rather than assuming an earlier acceptance decision continues to hold indefinitely without reexamination.
Communicating Accepted Exposure to Stakeholders
Where an accepted risk carries meaningful potential consequence, relevant stakeholders are informed of the acceptance and its rationale, ensuring the decision is not made in isolation without the awareness of those who may ultimately be affected if the risk materializes.
Consequences of Poor Management of Residual and Accepted Risk
False Sense of Security From Unassessed Residual Risk
Assuming a mitigated risk has been fully resolved without explicitly assessing what remains can leave a team unaware of genuine, ongoing exposure that a proper residual assessment would have revealed.
Undocumented Acceptance Mistaken for Oversight
Without clear documentation, a deliberately accepted risk that later materializes can appear, in hindsight, as though it were simply neglected, damaging trust in the team's risk management even when the original decision was reasonable and well considered at the time.
Visual Representation
The original risk is reduced by mitigation, and the remaining portion is then explicitly and consciously accepted. This relationship can be expressed as:
Residual and Accepted Risk is the deliberate recognition and documentation of this remaining quantity, ensuring it is knowingly carried forward rather than mistaken for risk that has been fully resolved.