How to form and manage a test team, how to manage your own test team

Ability. As a team leader, ability must be valued, and only with professional level and ability can the team members be recognized and obeyed.

What do you mean by your own testing team?

No matter what kind of team it is, to manage it well, the leader must lead by example, so that the team members will obey the assignment.

Only when the leader takes the lead can the members be motivated, and the team can develop rapidly.

In order to enhance the competitiveness and quality of software, many enterprises have begun to build their own testing teams. How to build a test team needs to be realized from the steps of "dream - > strategy - > goals - > organization - > process - > link - > standard - > inspection - >rewards and punishments".

Dream. The dream is to improve the quality of software, not to test for the sake of testing. For example, adding a testing team to the R&D center can improve the quality of the product, but there are still many problems after delivery, and the reasons are:

The R&D center is responsible for delivering the product, and in order to deliver on time, the quality problem will be suppressed, and the end result is that there are still many problems with the delivered product. So, testing is a means to improve quality, but it's still not enough.

Stratagem. Is quality or product characteristics important? Is a product launch important? There is no certain standard, but the basic quality must be guaranteed, and this is the strategy. Each has its own approach, so I won't repeat it.

Target. It is our goal to improve the quality of our products through SQA and the testing team. Can be subdivided into:

First, all products delivered to customers need to pass functional tests, integration tests, and acceptance tests; Second, new versions need to pass regression testing before they can be delivered; Third, if there is a problem with the product after it is put into production, it should be traceable.

Organization. The organization is subordinate to the goal, so there should be an organization where the goals of various departments are not aligned, but the ultimate goals are the same. For example, product development requires an acceptance test team, which is only subordinate to product quality and is not responsible for the delivery date; However, the granularity of acceptance testing is insufficient, and the understanding of the product and technical architecture is not thorough, so a testing team within the R&D department is needed to be responsible for functional testing and integration testing.

The development team needs to add SQA to improve the quality of design, documentation, and quality.

process. Processes should adhere to a lifecycle model, with quality management and testing as part of the overall development cycle, rather than siloing. For example, if the UAT team does not pass, it cannot be delivered and released, rather than the R&D department will end when the development is completed.

Tache. In the process that different departments are responsible for, many links should be designed as checkpoints, and there should be clear inspection objectives. My experience is that there have been designs that are flexible with KPIs, but they have been poorly executed.

So, we need to set clear KPIs. For example, the UAT looks at the defect retention rate (the number and percentage of defects that are not found by the development department).

Examine. With KPIs, it is necessary to have inspection data, which is generally divided into departmental KPIs and KPIs of each team (the team leader is responsible). It is necessary to check and check the raw data to prevent KPIs from being filled in arbitrarily.

According to the above steps, we can gradually establish a relatively complete test team, test process, improve product quality, and also be able to assess the test team and development team.