Done a lot of items, each generation has a different bug, how to reduce the number of generated bug, how to avoid repeating the mistakes, the ultimate aim is to improve the quality of projects, to become our developers need to focus on place . Change the face of growing demand in the agile development we need to extract more appropriate method to deal with changing needs.
Reduce the production bug, several ways to consider the dimensions of:
1. Project design document: an iteration may be more complex business logic, a good design document to determine the development of ideas in the development of reference documents can be quickly grasp the requirements and coding.
① preparation of design documents need to be considered comprehensive, when in the need for a comprehensive new business areas in which trade-offs will affect the original logic, designed to avoid or consider when taking into account the lack of comprehensive information.
② design is complete, need to notify QA, PD and other related personnel to review the views of all sides, and finally recognized in all the circumstances to complete a final design document.
2. The development of quality: level of development officers and a different point of view, different developers to write code that is different. So will a good pair programming to deal with this problem, by two people on the needs of the division of labor to their completion of the module code, review each other's code and the code review tool by tala aggregated record defects in the code and logic problems After the end of the code to modify the code check again. Can guarantee the development phase of the code logic reduction.
3. Self-test phase: after the end of the project development, self-test phase of the project into the FBI. The first time developers can test yourself on the completion of the function. How to self-test and can be from the following points:
① Development of the code after the end of the staff of each other's code writing unit tests, through the preparation of unit test, to further improve the junction of the other officers familiar with the code and verify the development of logic whether the results meet the demand.
② the day before the submission of the test, the black box testing, reference QA test cases to verify the main process logic, as much as possible to go much branch of the process, reduce the project to submit bug after testing the risk of the generation ahead of the test to determine functional it needs to achieve to ensure a smoke test pass rate.
③ uncertain and needs of the business to achieve as early as possible, or mail in the group informed the PD, PM, and QA and other personnel, to communicate with constituents to determine service delivery, reduce the uncertainty after the submission of the test needs a result of bug, reduce communication costs.
4. Project summary: The project was released, we all need to do summary and review, you can start from the beginning the following points:
① bug analysis: generated by the project bug causes, analyzes the situation led to bug the design stage or development stage is to sum up the reasons to remind us what the next development in terms of the need to strengthen the investment.
② do good, do not try and sum up the three points: the project team in each of the developer to write the contents of these three, then the subtotals, do good need to maintain, do not We need to invest energy to improve focus, you can try to improve the entry to practice in the next iteration.
③ Xiangmu experience: developer experience through each project summary, in the continuing development of the project to achieve personal growth, not done forgot to do something to further promote the developer's personal growth.
Hope this help to give you the help to improve project quality, after more than 4 points are classified as shown in this picture is the following: