Defect tracking of large-scale Japanese outsourcing enterprises

The author of this document is a manager of a large software outsourcing enterprise. The company ranked among the top 50 national Service outsourcing companies in 15. To protect privacy, we are here to hide the name of the customer.

Since the company's business is Japan outsourcing, and outsourcing will encounter 2 customers-the employer and the user, defect management becomes very complex, but also very important.

Before the use of Urtracker, the company's defect management is quite confusing, and the modification is inefficient, no trace can be found.

Therefore, the company's leadership decided to find a reasonable management tool to manage, after repeated comparison of choice, and finally selected Urtracker as the company's defect management tool, the use of nearly two years, the effect is significant.

The following detailed introduction of the company's urtracker use of the way.

1. Previous issues

Before introducing Urtracker, the defect is to use Excel+email submission Method------------------------------------------ But in this way, there are many problems.

1.1. Waste of time

One of the big problems with Excel is that if you find a flaw and submit it right away, not only does it take a lot of work to send and receive email notifications, it's hard to track, and if you aggregate a certain amount, There will be a waste of periodic working time when the test group waits to revise or develop the collective waiting for the defect.

1.2. Repeated Serious

Because of the limitations of Excel, the test can not guarantee the complete accurate description of the defect information, the developer can not guarantee the complete and accurate description of the changes, defects in the development of testing and transmission between the phenomenon has occurred repeatedly, has been unable to eradicate.

1.3. Communication inconvenience

Test found a flaw, the use of Excel submitted to the development side, if there is a supplement, need to be another email to explain, very inconvenient.

1.4. Difficult to track

Before the defect, often a lot of leakage change leakage test phenomenon. Many of the defects were submitted on the Test side, and in the development side of the allocation of changes and changed hands, the final modification of the defect is far less than the previous submission of defects, in the same case, the test will also be missing phenomenon.

1.5. Difficulty in keeping records

In the process of Excel delivery, there will inevitably be transmission errors or omissions, if there are problems with configuration management, then the previous defect records can easily be lost.

1.6. Statistical inconvenience

The use of Excel to record defects, a project often requires many forms, if the company's projects are many, that the statistics of defects, experience data retention, it will require a very large workload.

2. Process classification

According to the needs of different stages of development, and after continuous improvement, we designed 3 kinds of defect process-unit test process, system testing process, post release process.

2.1. Unit Test process

The unit test process is used for development group internal testing, which is submitted and left by the developer and is subject to review by the Test manager and the project manager.

2.2. System Test Flow

As the system testing is basically done by the employer, in the system testing phase, relative unit testing, the defect should be the internal validation of the company.

In addition, under the constraint of configuration management, the version provided by the employer must be baseline, so in the system test process, the link of SCM baseline is increased.

2.3. Post-release process

As a result of the release of the process included in the defect by the user or the employer to replace the user to submit, so the process is basically the same as the system test process, need to make 2 confirmed, the difference is that after the release process requires users to fill in the product version number to confirm.

3.1. Unit Test

3.1.1. People and Roles

Participants in the unit test are internal personnel, including project managers, test managers, development, testing, SCCB, and others.

Role	Duty
Project Manager	Assigning defects to modified personnel
Validation of defect modification descriptions and logic accuracy
Test Manager	Verify the flaw description and the accuracy of the logic
The verifier after the assignment modification is complete
Test	Submit defect
Verify defect modification and close
Development	Modify defect
Sccb	How to deal with the defect of adjudication
Other	Includes SQA, department managers, and technical managers to monitor project defect status