Share the project management team to drive programmers who do not want to write documents out of your team.

Recently, I was quite depressed when I encountered a very bloody thing. A UnionPay card payment project developed by my hand has some problems in the system O & M phase. Although it was finally solved, the emergence of reflection on the problem and the deep-seated reasons have deep feelings for the skills of project management and the establishment of team rules. The major issues that have emerged include:

1. The bank card overseas transaction failed.

2. Some countries in which the bank card is traded outside China failed: some countries succeeded, and some countries failed.

3. internal transactions of overseas banks fail.

4. During this transaction on his behalf, an error occurred while inserting the non-standard packet database table.

5. pre-authorized transaction processing failed.

Because this project is a porting project, most of the source programs come from another project of the company. According to XX and XXXX, the configuration can be used. It is easy to say, it is like three days to go online, and five days to complete. I relaxed my vigilance and listened to these statements, and the results were conceivable.

First, there is no document for the project: throwing a file package, including code, customization, and database tables. This is all. You can see it for yourself. The ghost knows that I should use these things as a ball. Comparison: By comparing tools, you can find the difference yourself. It seems that I am really ill. Who has the medicine?

2. No change description:

The core has changed and there is no record; the front has changed and there is no record. When dealing with user authentication and pre-authorization transactions, the core returned error code does not comply with UnionPay specifications. Each packet sent will be rejected. No way. Check the UnionPay specifications one by one and find the core error code version 2.0. The verification rule is version 2.0. People looking for the core with the rules did not dare to change the core. I am told that this is the case in XX region. It should also be done here, so it is certainly no problem. My mother-in-law, Grandma Si, decides whether the business decides the design or the experience decides the design. No, it's tough. Later, I asked XX for the latest version to find that the other party had changed the version, but we still don't know. It's even more tragic, but I can't say it. Jesus. Who will save you!

Third, the bug is not recorded

The predecessors planted trees, and future generations enjoyed the cold. The core value of the Bug management system lies in this. Unfortunately, the tragedy is that when people planted trees and dug them up, they left a tree pit and I had to start from scratch. The reason for the above-mentioned Overseas transaction failure lies in the lack of a country code domain. All domestic transactions are OK. overseas transactions are directly over. Comparison, testing, and finally finding the problem, the user's face began to turn green.

4. release without testing

Untested programs are directly released. Do you dare? Whether you dare not, I dare not, but I did not. Then, the system crashes and then comes back. No, I don't want to test it. It's no environment, no encryptor, so it's a good reason. I think so too. Don't tell me to use a simulation. Don't tell me to bypass it. Maybe it's really stupid. Strong users, unreasonable requirements, and trampled processes. I have never been so fat. Jesus, stay in the trap first!