How to raise, assign severity and prioritise defects.
Defect tracking is important in software engineering as complex software systems typically have tens or hundreds or thousands of defects: managing, evaluating and prioritizing these defects is a difficult task. Use of a defect tracking system can make the management task much easier. We use JIRA for defect management.
The defect management process contains the following elements:
All our projects use an agile development methodology and usually we encounter these situations:
A defect must use the standard template for any defect with any severity level. At the minimum level the defect details must have the following sections presented in this order:
The information captured about the bug should be enough to reproduce the defect and allow development to determine its root cause and impact. Apart from the template above, all defects must have Severity mentioned.
All the bugs raised should adhere to the standard severity definition, S1 (being most severe) to S4 (minor).
We have the following set release criteria: