Software test management Analysis in the project _ Performance test

There have been a lot of stories over the last three projects and three project tests.
Member Introduction: Team Leader W, member L, member Z.
Member background: Team leader W just arrived at the company, former old employees. Member L familiar with Project A, member Z familiar with Project C.
Team Leader Objective: Training team member L have the management ability of team leader, exercise Team Z have the management ability of team leader.
Task Division: Member L is responsible for the test of Project A, member Z is responsible for the test of Project C, team leader W is responsible for Project B test.
Project progress: Project A just started submitting some modules to be tested. Project B side design side coding phase. The Project C integration test will be over in a week. The original project C of the test leader is now leaving, the original project a test leader is now leaving, at this time the team leader W must ensure the project a test task under the premise of Supervision Project C, because the member responsible for the test Z, member L have no management experience. Originally 4 person's project, because originally 2 team leader's turnover, causes the leader W succession to need to have the adaptation process, this process approximately 2-3 weeks.
The whole project C, team leader W participation is less, only concerned about key test progress, milestones, specific matters are given to member Z processing. The schedule is very smooth and the test task is completed on schedule. But the project manager repeatedly feedback member Z, the test carelessness, confirmed acceptance test and team leader W's Test feedback, Project C simpler, the project manager walks the code seriously, the bug is less normal phenomenon.
Project A because in the early stage only member L participation, encountered problems do not know how to deal with, many times rely on the test leader W resolution, resulting in team leader W can not participate in the normal Project B test. The final team leader W abandons Project B's simultaneous testing, chooses to lead the member L test, and during the test, gradually guides the member L how to solve the problem. Due to the failure of the Prophase Test task arrangement, the team leader W, the test member L many overtime test. Project a software coding period, due to the developer's business trip, resulting in the project stopped, resulting in a project extension of 2 weeks. This issue is at risk in later test Project B. Since project a originally ended 4 weeks before Project B, it is now only 2 weeks ahead of schedule and Project B has no resources for testing.
Project A during the test, the development team will travel to the forefront of the project, the project manager also travel to the project frontline, once the project A into the unmanned management stage, only 1 ordinary developers to modify the defect, encounter the issues to be discussed can not be resolved, affecting the project progress. Test post-Collation Database installation package, packaging program, the development leader is not involved, just assigning tasks to inexperienced ordinary developers, resulting in simple problems many times to modify the situation, the development team leader at this time not only not help, but only ordinary developers to solve the process, which caused the delay of 3 days of work. Test later Database installation package verification and program verification, team leader W are interested in testing member L participation, this project Test member L learned, encounter problem solving ideas, write test report, verify the release of the program, database installation package.
Project B has been slow to test for Project B due to the test leader W multiple help item A, and project A is also closed 7 days after the project C knot. Team Leader W will test member Z, Test member L are all involved in Project B test. At this point there are 2 weeks left for Project B's knot. 3 people participated in the test 1 weeks, due to project B in the project pilot feedback, need for the requirements, design, coding rework, resulting in a 4-day extension of the workload, test leader W feedback test needs to be postponed for 4 days to knot, the project manager to accept the extension of the application, to the company's superiors to apply for Project B extension. After several extensions, the project was postponed for 6 days. At the beginning of the system test, as a result of the lack of cooperation between developers, it is difficult to build a test environment, while the test leader W let the test member Z responsible for the environment, but found that the test member Z for the environment, installation package calibration is very confusing, test member Z took a long time to build the environment. For the newly built environment, according to the Test team leader meeting timely feedback of the installation package issues, after the project manager, product Manager discussion, the original database installation package needs to be done, the procedure will also be adjusted, and now caused 2 days of work delay. Most of the user manuals have been written due to the advance arrangement of the test leader W and the overtime work of the Test team members. Later problems arise because of timely feedback and the initiative of the project manager to consult, are effectively dealt with.
3 projects are over, but the testing side of the problem with the project team unreasonable arrangements, as well as sudden changes in requirements, planning changes, plus with the development of communication problems and coordination issues, conflict, resulting in the testing process is not smooth, many changes, many times rework. Testers are tired of testing, the developer code is also very tired, coupled with the developer communication during the period of cooperation, resulting in very serious negative emotions.
I really hope that the next time these projects to apply for change, the test lead should be more reflective of whether the impact of testing resources, test managers should train test members of the basic management capabilities. Otherwise, the tester is very tired, the test person is more tired. On the issue of communication, we should not only grumble about the weak communication ability of the developers, we should consider whether the test staff communication should be changed, for people who are not good at communication, reduce text communication, more verbal communication. In the project task development, the project team has a very important responsibility, the internal too lack of communication discussions, both oral small discussion to solve the problem, the results of the issue without written formal notice, are passed to the tester, in this, the tester opinion is very large. requirements, design, responsible for the development of personnel irresponsible, testing personnel encountered problems, can not be resolved is not feedback to the leadership, are refusing to reply to the test staff, resulting in the tester's work attitude to the developer, the character greatly compromised.
Copyright NOTICE: This article is from the guofei318 51Testing Software Test Blog: http://www.51testing.com/html/17/n-863617.html
Original works, reprint, please be sure to hyperlink form to indicate the original source, author information and this statement, otherwise it will be held accountable.