17th back-to-test project management principles

SoftThe success or failure of a piece development project depends on the level and coordination of "process, people, and technology". The process is the foundation and people are the core, while the technology is the guarantee,

These three aspects are mutually constrained and mutually reinforcing. Which one fails to keep up with and forms a weak link, and the possibility of project success will decrease. The test item is no exception. You need to work together in these three aspects. In particular, software testing, scientific and normative process definition, strict process execution, and a high sense of responsibility of personnel are all crucial.

Second, we need to have a global and correct understanding of the management of today's test projects for software development, follow the V model to better understand the relationship between requirements and validation, design implementation and verification. For details, see --> 1st back-to-V model. My complete interpretation

Furthermore, project management has three elements: cost, progress, and quality. For the management of software testing projects, the cost and progress should not be ignored. The testing strategy should be emphasized to improve efficiency, and the project should be tracked at any time to ensure that the project is executed as planned. But the more important thing is "quality", the software test Manager has more responsibility for product quality.

Finally, whether the process management of the software test project can be successful is also affected by three core layers, namely, the environment of the project team, the organization environment of the project, and the global environment controlled by the entire development process. These three environmental factors are directly related to the controllability of software projects. Project Team management and project process model, organization support environment, and project management interface are the core elements of the above three environments.

Software testing project management is a protective activity of software engineering. It starts before any test activity and continues throughout the definition, plan, and test of the test project.In order to ensure the successful management of the test project process, it is necessary to adhere to the following test project management principles on the basis of the above four points:

1. we can always put quality first. The fundamental purpose of the test is to ensure the quality of our products. We should establish the concept that "quality is the foundation of enterprise survival" in the test team, establish a suitable quality responsibility system.
2. reliable requirements. A clear, complete, detailed, and practical requirement definition should be provided with the unanimous consent of all parties. Ability to develop testing strategies, arrange work in a planned manner, system solutions, and formulate reasonable schedules. Leave sufficient time for the test plan, test case design, test execution (especially system testing), and their review, and should not use a surprise approach to complete the project.
3. pay sufficient attention to the test plan and clearly describe the test objectives, test scope, test risks, test means and test environment in the test plan.
4. test cases are the basis for test execution. Before testing cases are designed, they should be fully discussed with developers and product managers, and should be reviewed collectively to ensure high coverage. And pay attention to its continuous improvement.
5. test automation or testing tools should be introduced as appropriate. The preliminary preparations should be sufficient and should not be blindly involved.
6. do not take the test environment lightly. Check the environment's software and hardware configurations with relevant personnel.
   
7. full test and early test. Re-tests should be performed after each error or change. In the project plan, sufficient time should be set for correction, re-testing, and change.
8. when a problem occurs, the system can accurately determine whether the problem is a technical problem or a process problem, and pay more attention to the process issues to fundamentally solve the problem, rather than to solve the problem.
9. track the defect status throughout the process, and analyze and clear the defect status in a timely manner.
   
10. general project management principles, such as smooth and effective communication, document consistency and timeliness, and project risk management. The risks of testing are even greater, so you need to take appropriate measures in a more timely manner.

To predict the future, read the next decomposition:18th effectiveness and comprehensiveness of the test plan

Copyright, software testing

-For the series of discussions, see:Software testing romance-intermediate and advanced series (sequence)