Manage the software defect process - ocawley/ittsqa22 GitHub Wiki

Software defects can be very expensive. Moreover, the cost of finding and correcting defects is the one of the most expensive software development activities. It is not be possible to eliminate defects. However, their number and impact on projects can be minimised. To achieve this development teams need to implement a defect management process that focuses on preventing defects, catching defects as early as possible, and minimising the impact of defects. This little investment in this process can yield significant returns.

According to Kota[1] there are eight high-level process steps involved in the defect management process. Each of these steps would have more detailed standard operating procedures along with policies explaining the process in a great detail. These steps are as follows:

1. Identification Involves the discovery of a defect. Ideally, the person discovering the defect is someone on the testing team. However, it can be anyone including people on the project team, or even the end-user.
2. Categorisation When a defect is reported, it is assigned to a team member to confirm that the defect is actually a defect and not an enhancement, or any other categorised group. Then the defect goes to the next step of prioritisation.
3. Prioritisation Is based on a combination of an impact on the user, effort to fix, and comparison against other open defects. Prioritisation is often handled by a formal change control board in an organisation. The priority should be determined with management, the customer, and the project team.
4. Assignment The defect is assigned to a designed or other technician to fix.
5. Resolution The developer resolves the defect and moves the solution to the environment where the defect was identified.
6. Verification A software testing team or customer verifies that the fix actually resolved the defect.
7. Closure The defect is marked and closed.
8. Management Reporting Reports are provided to appropriate individuals at regular intervals as defined in reporting requirements. In addition, on-demand reports are provided on as-needed basis.

References: [1] Kota, K. Defect Management Three Components of Effective Defect Management Systems. [online] Available at: http://www.adminitrack.com/articles/defect-management-software-tools-system-plan.aspx [Accessed 18 September 2014] [2] Defect Management. [online] Available at: http://www.defectmanagement.com/defectmanagement/index.htm [Accessed 18 September 2014]