Software Test Management and Analysis in the project

Three projects have just ended recently, and many stories have occurred during the three project tests.
Member Introduction: Leader W, member L, member Z.
Member Background: W, a former employee, has just arrived at the company. Member L is familiar with Project A and member Z is familiar with Project C.
Objective: To train Team Leader (L) and team leader (z.
Task division: member L is responsible for project a testing, member Z is responsible for project C testing, and lead W is responsible for Project B testing.
Project Progress description: Some modules to be tested are submitted at the beginning of Project. Project B side design side coding stage. The Project C integration test will end in another week. The test team lead of the original project C is now resigned, and the test team lead of the original project a is now resigned. At this time, the team lead W must ensure that project a is under supervision of project C, because the test Member Z and member l have no management experience. In the original four-person project, due to the departure of the original two leaders, the leader w needs to adapt to the process of taking over. This process is about 2 ~ 3 weeks.
The entire project C, team lead W seldom participates, only focus on the key test progress, milestones, and specific matters are handed over to member Z for handling. The test task is completed on schedule. However, the project manager repeatedly gave feedback to member Z, and the test was careless. After confirmation of the acceptance test and the test feedback from the team lead W, Project C was relatively simple, and the Project Manager checked the code carefully, it is normal to have fewer bugs.
Project A is unable to participate in project B's test due to the fact that only Member L is involved in the preliminary stage and does not know how to handle the problem. The team lead W has been resolved by the test team lead for many times. In the end, the team lead W gave up Project B's test at the same time, chose to lead member L to test, and gradually guided Member L to solve the problem during the test. Due to errors in the pre-test task arrangement, the team lead W and test member l work overtime for multiple tests. During the software coding period of Project A, due to the developer's business trip, the project was suspended, and the project was extended for two weeks. This problem poses a risk in the later Test Project B. Because Project A originally ended four weeks before Project B, it is only two weeks ahead of schedule, and Project B has no test resource schedule.
During the test period, project a will lead the development team to the front line of the project, and the Project Manager will also go to the front line of the project. At one time, Project A will be put into the stage of unmanned management, there is only one common developer who can modify the defect and cannot solve the problem that needs to be discussed, which affects the project progress. The database installation package is organized at the end of the test. During the package process, the development team members are not involved. They only assign tasks to inexperienced ordinary developers, which leads to the failure of repeated modification to simple problems, at this time, the development team did not help, but only let ordinary developers solve the problem by themselves, resulting in a delay of three days of work. After testing the database installation package and program verification, the team lead W intends to involve test member L. the test member L of this project has learned how to solve the problem and compiled the test report, verify released programs and database installation packages.
Project B's Test Progress is slow because the test leader W has helped project a multiple times. When Project C completes the project, project a also closes the project seven days later. Team lead w will test Member Z, and test member l will participate in project B's tests successively. There are still two weeks before Project B's completion. Three people participate in the test for one week. Due to Project B's feedback on the pilot project, the work needs to be extended for four days due to demands, design, and code rework, the test team lead W reported that the test should be postponed for 4 days to complete. The Project Manager accepts the application for extension and applies to the company's superior leadership for extension of Project B. After multiple delays, it is agreed that the project should be postponed for six days. At the beginning of the system test, it was difficult to set up the test environment because of the lack of cooperation of developers. At the same time, the test team lead W asked the test Member Z to take charge of the establishment of the environment, however, it was found that the verification of the installation package is messy when the test Member Z sets up the environment for a long time. According to the installation package problem reported at the test leader's meeting, after discussion by the Project Manager and product manager, the original database installation package needs to be redone and the program needs to be adjusted, at this moment, the workload is extended for another two days. Most user manuals have been prepared due to the arrangement of test team lead W in advance and the overtime work of test team members. Problems that may occur later are handled effectively by timely feedback and proactive consulting by the Project Manager.
The three projects are over, but the problems on the test side are unreasonable arrangement with the project team, sudden demand changes, planned changes, and communication issues and cooperation issues with developers, conflict, resulting in poor testing, multiple modifications, and multiple rework. The testing staff is very tired, the coding staff is also very tired, and the lack of cooperation during the communication between the developers, resulting in a very serious negative mood.
I really hope that when applying for changes to these projects, the test owner should reflect more on whether the test resources are affected, and the test owner should train the test members with basic management capabilities. Otherwise, the tester is tired and the test Manager is tired. In terms of communication, we should not only complain about the weak communication ability of developers. We should consider whether the communication methods of testers should be changed. For those who are not good at communication, we should reduce text communication, multi-verbal communication. In the formulation of project tasks, the project team has a great deal of responsibilities. There is a lack of internal communication and discussion, both of which are oral discussions to solve the problem. No formal notification is given to the results of the problem, all of them are forwarded to the test personnel, which gives great comments to the test personnel. In terms of requirements and design, developers are not responsible. The problems encountered by testers cannot be solved. Instead, they are rejected by the testers, as a result, the tester's attitude towards developers and their character are greatly compromised.
Copyright: This article from guofei318 51testing software testing blog: http://www.51testing.com/html/17/n-863617.html
For original works, you must use hyperlinks to indicate the original source, author information, and statement of this Article. Otherwise, you will be held legally liable.