Defect Management Guide. Part 1: 8 Stages of Handling Defects

by TestFortExpert on 03/11/2014

Software development and testing teams have a wide choice of tools for defect management which help support different software defect efforts. However, selecting and utilizing the right is only part of the whole defect management system.

Basically, defect management systems consist of the combination of different defect management tools and defect management process. The two major components work together supporting each other. If you ignore either one, you risk receiving sub-optimal results.

Therefore, below we present an overview of the average defect management process. A regular defect management process involves the following common process steps.

Identification

This stage suggests the discovery of the defect. Hopefully, someone of the QA team should discover it. However, in reality it can be anybody including other individuals of the project team and even end customers on rare occasions.

Categorization

Once the defect is reported, it is usually assigned to the designated team member in order to confirm it is really a defect rather than an enhancement or any other appropriate category defined by the company.

Prioritization

This is usually based on the combination of the level of impact on users, relative fixing effort as well as comparison against some other open defects. Often the prioritization is done by a formal control board of changes depending on the organization’s size and structure. The priority is determined with from the management, customer and project team representation.

Assignment

After a defect is prioritized, it is assigned to the developer or some other technician for fixing.

Resolution

Then the developer fixes this defect and moves its fix back to the environment in which the defect was identified originally.

Verification

According to the environment of the defect’s location and its fix’s application, the testing team or the customer normally verifies that this fix resolved the defect indeed.

Closure

Once the defect is resolved and verified, it should be marked ‘closed’ and move on to the last stage.

Management Reporting

Appropriate individuals should be provided with management reports at regular intervals according to the defined reporting requirements. On-demand reports can be additionally provided when needed.

In case of implementation inside a specific organization, these steps would have somewhat more detailed operating procedures and policies of executing the process details.

In Part 2 of our Defect Management Guide we will also list some key features you should look for in tools for effective defect management.

We Work With

Having one outside team deal with every aspect of quality assurance on your software project saves you time and money on creating an in-house QA department. We have dedicated testing engineers with years of experience, and here is what they can help you with.

Software is everywhere around us, and it’s essential for your testing team to be familiar with all the various types and platforms software can come with. In 21+ years, our QA team has tested every type of software there is, and here are some of their specialties.

There are dozens of different types of testing, but it takes a team of experts to know which ones are relevant to your software project and how to include them in the testing strategy the right way. These are just some of the testing types our QA engineers excel in.

The success of a software project depends, among other things, on whether it’s the right fit for the industry it’s in. And that is true not just for the development stage, but also for QA. Different industry have different software requirements, and our team knows all about them.

Full-Cycle Services

By Platform

By Type

Industries