1. Requirements review: identify code changes and record requirements questions
  2. Requirements review: question points and revised risk points to the product
  3. Technical solution output: detailed design, down to which project, which class, which method code to change and how to change
  4. Technical solution review: the technical Leader checks if there are any missing points in the technical solution, and explains to the testers which points should be tested
  5. Test case review: test students explain test cases, development, product to see what is missing
  6. Code development
  7. Test by P0: Tests the basic logic
  8. To measure
  9. Test + Fix problems in test
  10. Product UAT validation test
  11. Code Review meeting for the requirements of the same iteration, the whole team will participate to see if there is any problem with the Code. If there is any problem, the Code Review + Code convergence needs to be modified
  12. Integration testing + problem fixing in testing
  13. Release system to fill in the release manual: pay attention to whether to change SQL, prepare SQL worksheet if yes, whether there is a new configuration, if to fill in the version number of the new configuration
  14. Published online
  15. Test classmate verification
  16. Product classmate verification function
  17. If there is a big problem, roll back the code
  18. If you have a minor problem, fix it immediately and re-release it