1. Demand stage
1. The product does not know what you want
2. Even if the product knows what it wants, it cannot give specific business details, such as how many digits the user input should be limited to, whether to perform existence or uniqueness verification, etc.
3. Even if the product knows what it wants and the business details, it cannot connect with the developers, and there are often errors.
4. Even if you are fortunate enough to connect the product with the technology, it is difficult to remember these consensuses in the future.
5. Even if the document description is added to prevent future forgetting, it is difficult to ensure that the document can be recorded accurately. I remember what my first Boss said: a Chinese word, 100 people can understand 100 people.
2. Development stage
1. Only the Team Leader himself knows what the product wants, and the brothers under his command do not know
2. Even if the brothers understand the requirements by analyzing the requirements and explaining the requirements, everyone only cares about the system they are responsible for and the surrounding modules.
3. Even if we let everyone know what our goal is, it is difficult to guarantee that everyone's development direction will not deviate in the daily project progress.
4. Even if you let everyone know the current progress and adjust the direction through the form of a stand-up meeting, it is difficult to ensure that everyone's understanding is consistent.
5. Even if everyone's understanding is consistent, and by standardizing the interface between modules, it is difficult to ensure that everyone's code is not reinventing the wheel
6. Even if the wheels are used every time, the impurities are removed as much as possible, leaving only one least common factor module, which is often ignored because it does not meet the case scenario.
3. Integration stage
1. What is often experienced is that the first round of integration is actually unit testing of individual modules.
2. Even if the unit test is passed, the lack of functions will be caused by the unclear responsibilities of the interface.
3. Even after several rounds of integration testing, the responsibilities have been clarified and straightened out, but time will be lost due to the deployment environment.
Fourth, the release stage
1. The day of the release is often the same as the Chinese New Year. Some people are passionate, and some people are frightened.
2. The release is often failed because the production environment is inconsistent with the test environment.
3. Even if the environment is the same, the release will fail due to inconsistent configuration parameters.
4. Even if the configuration parameters are consistent, there will be some inexplicable bugs due to the inconsistency between the dependent system and the test environment.
5. Even if the release is successful and there is no exception, some bugs that are not currently covered by the release will appear after a few days of operation, such as failure of third-party calls.
5. Iterative process
1. If it is the first time the product is released, then congratulations, you are very lucky, you can do what you want for the first time, as long as the function can be realized.
2. Even if it is not the first release, if you have participated in this iterative release from the first release to the present, then congratulations, you are also very lucky.
3. If you are Cheng Yaojin who came out halfway and start to receive this release, then I also congratulate you, you have won the lottery.
4. The system that takes over halfway, no matter how well the handover work is done, will not be detailed in the processing logic of each code, especially the logic of conditional expression judgment.
5. You often feel that you have modified the code according to the new requirements and updated the version, but you cannot step on another thunder.
6. If the mine exploded when it was released, or before it was released, then you are also lucky, you still have the ability to cover the mine.
7. If you think that your version iteration is successful, when Meizizi was ready to wait for the boss's reward, the boss's call came: the system was found to be a bug by the leader. As a result, you checked for a long time, only to find out that the cause of the problem was that you stepped on a thunder, then congratulations, you are lying.