Take over the project for O & M, and what legitimate and standardized handover documents and technical support should the former technical team provide?

What should I pay attention to as a successor Team to ensure the stable operation of projects in the future? What are the risks of such incidents, such as accounts, malicious changes, and pitfalls? Some details of a large project may need support from the former team? After the documents and procedures are handed over, is it reasonable to provide the technical advisor services based on the working hours or the limited number of times. What should I pay attention to as a successor Team to ensure the stable operation of projects in the future?
What are the risks of such incidents, such as accounts, malicious changes, and pitfalls?
Some details of a large project may need support from the former team? After the documents and procedures are handed over, is it reasonable to provide the technical advisor services based on the working hours or the limited number of times.

Reply content:

What should I pay attention to as a successor Team to ensure the stable operation of projects in the future?
What are the risks of such incidents, such as accounts, malicious changes, and pitfalls?
Some details of a large project may need support from the former team? After the documents and procedures are handed over, is it reasonable to provide the technical advisor services based on the working hours or the limited number of times.

For problems such as malicious modification, it is necessary to rely on legal agreements and conscience, as well as confidentiality agreements. In addition, the other party should be required to provide all possible host, account, password and other information and change the password. It is best to negotiate the technical support in a friendly manner and leave contact information. If you have any questions, you can ask. This will allow you to avoid detours, but will not help you solve any practical problems.
As for documents and other things, there is no need to look forward to it, and the document will never keep up with code changes. Therefore, expired documents are of no use except for you. It's inevitable to play it on your own. It's good to get used to it.
For urgent bug fixing, you do not need to understand the whole project at all. You just need to correct the problem.
During the handover, the predecessors will always proudly tell you some brilliant history and will never tell you any problems. First, they will damage your reputation. 20,001 What should you do if you let him complete the change, third, he does not know the problem at all (no one will write the code that he thinks is wrong, so the bug will only be detected by others)
Come on ~

This is conscience,All you can think.. If the development team is professional enough, you may be given detailed development documents. If you are not professional, you may not have any documents. If you want to, you can write something for your convenience. The egg team has no hair, and then it is all pitfall. The code is all about eggplant, cucumber, and tomato. You can study it. It may be nice to know about it in a few months. Good luck.