Deferred risk

Also called: deferred with risk, accepted risk, known issue

Deferred risk is a known gap or defect that the business has chosen to ship with, recorded with its impact, workaround, owner and review date.

Not everything gets fixed or tested before a release. Deferring is legitimate when it is a decision: someone with the authority to accept the risk has seen what could go wrong, for whom, and has agreed to carry it until a stated date.

It becomes dangerous when it is only a label. “Known issue” and “minor issues remain” hide which journey is affected and who agreed. A deferral without an owner and a review date is a defect nobody wants to look at.

I write each deferral in the same parts: the journey, the gap, who meets it and how often, the workaround a real user can perform, who accepted it, and when it is reviewed.

Template: Deferred risk record template

More on this subject: UAT and stakeholder engagement. Written by Marius Ene, senior QA consultant. See how I work with teams or browse all terms.