ERP project documentation-hate when thinking

Recently I heard about a controversial issue concerning the implementation of ERP projects. Let's talk about the background of this issue first. An enterprise is preparing to implement an ERP system. After a series of research and selection questions in the early stage, a software company is finally determined to cooperate. In the early stage of project implementation, everyone is happy to cooperate, the company also recognizes the project manager of the software vendor and basically implements the project according to the idea of the Project Manager.

Some changes have taken place in the project implementation process. Originally, the company was appointed as the project manager by the marketing director. However, due to its personal development, the company resigned, at this time, the company only needs to change the project manager. The company has changed to Manager Zhang of the marketing department, but Manager Zhang is not very concerned about the construction of the information system, at the same time, I also feel that if I want to coordinate other business departments to promote this system, the name is not correct and the words are not smooth. Naturally, there is not much to do on this Part; once you look at this situation, there is no way to ask the IT department to serve as the project manager. In this way, the three-Wave project manager was changed, and the Project stopped and stopped. After more than half a year, the project finally went through the acceptance phase.

Of course, there was another episode before the acceptance stage: the two consultants (one of them is the project manager) of the software vendor, who felt that the software vendor was very good. They talked to them privately, turn all the project managers of software vendors into their own; as a result, the project has not been completed yet, and the software vendors have suffered a dumb loss, and the staff has been lost, another project manager has to be sent to the project; this is good, and the Project Manager of the software vendor has changed.

Now we have to go through the acceptance process. We have a point: the software vendors of the company have not done their work properly when they did the research, and have not investigated the approval process of the financial department, this part of the process is not clear and needs to be re-researched and implemented; but software vendors feel that they are wronged, because at the earliest time, the first project manager said that the system was only used by the marketing department, and the finance department did not need to pay attention to it. The finance department also said that it was busy and only gave the Project Manager A description of the approval process, let the software vendors implement it in this mode. However, the people who say this is not necessary have gone, and the Project Manager of the software vendors has gone to the peer camp, who can prove what it was at the beginning?

Because the software company's staff were dug up and suffered a dumb loss, this time the customer was unreasonable, so he insisted that he would not re-implement this part of the content, the incident was slapped by others, and you had to pay for your own medical expenses. Instead, the other party said that his hand was hurt, and you had to pay medical fees again, which was quite irritating.

However, the current project manager of the software vendor has no evidence to support the reason for not doing anything, because even though the customer verbally promised that this could not be done, however, without the client's written signature or the written confirmation from the Financial Department, it seems that this is indeed enough. However, in this case, there are still some reasons behind the implementation of the ERP project. This is not the case, now, if you want to find evidence for yourself and prove that you are innocent, you can't find a solution.

 

This case has concluded three conclusions: 1. Do not believe what the customer says. Just nod your head when you think it out! 2. Without making a statement, it is right to sign and compress the statement. 3. frequent changes to the project manager and fierce ERP projects!