Defect Severity & Priority

Table below gives the definitions of Defect Severity for the defects:

Severity Level	Definition	Consequence
Severity 1	Showstopper - Severe business impact and No work around available.	Such defect results in failure of the complete software system / sub-system / program / module within the system. Tester's ability to operate the system either totally or almost totally, affected.
Severity 2	Considerable business impact, but work around available to overcome the issue.	Such defect results in failure of the complete software system / subsystem / program / module within the system. Defect affects an area of functionality but there is a work-around which negates the impact to business process and testing can continue.
Severity 3	Non-critical impact & there is no data loss	Such defect does not result in a failure, but causes the system to produce incorrect, incomplete or inconsistent results, or the defect impairs the systems usability.
Severity 4	Minor impact on system function or a cosmetic error	This is for minor problems, such as failures at extreme boundary conditions that are unlikely to occur in normal use, or minor errors in layout/formatting.

Table below gives the definitions of Fix Priority for defects:

Fix Priority	Definition
Critical	Further testing cannot occur until the defect has been repaired. The system cannot be used until the defect is fixed.
High	The defect must be resolved during current sprint but fix to be delivered with Next sprint
Medium	The defect should be resolved in the normal course of development activities. It can wait until next/ future sprint
Low	The defect is an irritant which should be repaired but can be repaired after more serious defects are fixed.
Deferred	After Defect Triage meeting if defect fix is not planned within the next two immediate sprints then it will be moved to Deferred.