How to manage the Test team well

How to manage the Test team well

1 , as a team manager, the minimum is to understand their own product or project business. This is important, first of all, it helps to distribute work to the team members, otherwise it is difficult to understand the business difficulty and the amount of work assigned to team member is a very unacceptable thing. Second, to help oneself and other team or department cooperation and communication, not the other team asked questions, I still do not know to agree or deny to do.

　　2 , as a manager, to understand more technology, at least to learn more Test technology, to understand how it works, it helps the team member research or technology application to the actual test work. Also can improve their own in the Test team of the Wei, I know more can let more students to recognize and convincing.

3 , balancing tasks assigned to team member . for Senior Testers We assign more tasks to design test Case, the junior tester may be more assigned to perform the test. Assigning work is also to see which testers have the expertise, some testers are more sensitive to the GUI, some testers are concerned about logic, some testers of the entire system is more clear, these are as a Test manager assigned a baseline of tasks, so that a better team, to improve the area of the . Span style= "text-decoration:underline;" > software tests the level and quality of .

4 , to manage the risk of testing. in general, we want to minimize the risk of testing, but also a very important issue in the test management, I can only talk about some of my own partial views. Testing risk begins with software requirements analysis, and we are better able to identify these risks lurking in demand or development design in the early stages: 1) If demand does not meet the requirements of the function, or there is a need to violate the existing functions we must put forward in the demand analysis; 2) some features or essentials in software requirements design that cannot be tested Also to be presented in the test requirements Analysis, 3) The development of static testing of design documents, which I think is very important, many small companies will basically ignore this, static testing (mainly refers to the documentation aspects of testing), the development of design documents or prototype design documents review or testing to help test the reduction of risk can also find some conflict with the design of the demand, to strive for errors in the early detection. At the same time we test case can also better match with the test, design better test cases to test, Whether it is from the GUI, or the development of testing technology testing is beneficial; 4. Review or static testing of test cases, which facilitates the optimization of test cases, the addition of more useful test cases and the removal of some useless or repetitive use cases, which can improve test execution efficiency. 5. Monitoring test execution and bug Management, Bug is one of the results of testers, we as managers must be managed well, At the same time, we can clearly see the existence of testing risk, through the existing bug trends to determine the future of how many bugs in the system, can be the type of bug to analyze how long the fix bug and how much more likely to produce the bug, This gives us a clear idea of when the current testers and developers are going to have to work overtime or to deploy more people ..., we also have to focus on the test execution progress, testing the initial bug trend chart, which types of bugs more, this will affect the mid-test, Logic is a lot of bugs will affect the quality of testing and testing efficiency, at this time to remind the development team to pay attention to the logic type bug fix, you can not drag this type of bug to the post fix, which will affect the quality.

Of course, software quality risk has other factors, such as project or product time assessment, I think this part is mostly hard, we can negotiate the project time of testing, as well as personnel leave or leave, and test team personnel changes, and testers emotional fluctuations will affect the test quality risk.

　　5 , reasonably evaluate or measure the performance and level of testers. believe that this is also difficult to do, not to do well, not only can not make the whole team to work hard, more internal contradictions, resulting in staff turnover will have, is to let a team the most headache, then how can we reasonably evaluate the work of the testers? First of all, I think the public hard performance standards, so that we all understand a standard, but also the purpose of common development team, so do justice, there will be no selfishness. I think we can measure from several aspects: a) work attitude and enthusiasm B) workload and work quality of a linear comparison, the workload is the most laborious, but to work with the quality of reference, of course, we can not put an employee to find the number of bugs as a result of their work performance standards, I remember a former Test manager did this, it is very deadly and harm the whole company, because the test object or the level of the developer is different and the size and ease of the project is not the same factor, I think a better standard is from the perspective of the various, Test execution process and test case two aspects, the implementation of the test process Bug trend chart and bug type distribution map and the software delivery bug feedback rate, the tester should find in the test execution process should be found in various stages of the bug, not the obvious bug and found at the end, these can see the tester's level In addition, the design of test cases is also a very important standard, good test cases, will find the bug as early as possible, of course, the design of the test case is operational, detailed and so are measured standards.

　　6 , cohesion, and the potential to inspire team members. this, although a bit of a big talk, but really is very important, I think it is very important that everyone in the team is growing up, to arrange a reasonable role in the work is very important, so that they can better see their growth space, If you let a junior tester design a simple test case for a test project or requirement, he also feels that he can design the test case, so that the senior tester is responsible for the project and that he is the protagonist of the project rather than the Test manager, so that the members of the team will be more responsible. Schedule more idle tests to research the updated technical or test techniques and share them with all the members through the lectures; During the execution of the project, the testers are arranged to exchange tests in the process so that the members involved in the project can understand the whole system. Each part of the project is equivalent to having a backup person, not worrying about the project's absence, and training the tester's business knowledge. Make a lot of communication between members and participate in activities outside the work.

　　7 , communication members, understanding the mentality of members. as a manager to pay more attention to the members of the psychological problems and growth issues, why the work is not very positive? Why is the project not high quality? .... Can be talked about in private chat, and help them solve!

Reprint: Http://wenku.baidu.com/link?url= lrfuurxjgysg5sa1c90xz4kyh2y5vofraduokbli0c9oiwv-vmkwciuuagf9z5u6cr4m9ewuhgznr5i4jihpopjphtqzqx711aznqo2yxde###

How to manage the Test team well