[Transfer]oracle Implementation Methodology learning experience

This week, our new colleagues in the Department shared the Oracle implementation methodology, focusing on the launch of the project and highlighting where Oracle is different from us. The harvest is quite abundant, the summary of a few worthy learning points:

1. The details highlight the professional! Oracle has mastered all the details of document management, from the standard naming of files to version management, highlighting professionalism everywhere. In fact, Mingyuan also has document management specifications, but our implementation of consultants in the implementation process has not been implemented in accordance with the code. In fact, good document management does not increase the workload of everyone, it is only a habit problem.

2. the gown will be put into place while the project is started! This is the second point that Oracle makes a man admire. Companies also have gown, but we often take gown as a form, and sometimes ignore it. Reflect on our implementation of the project, how many projects with the 1W signed gown? Is it true that the success of the project is tied to high-level performance? Start the project when the customer enthusiasm for the project is high, full of confidence, this time is the best time to sign gown, signed a gown, conducive to our implementation of the project with the customer high-level establishment of strong correlation relationship, for the later project promotion, the outcome of the problem is very advantageous.

3. The Happiness curve of project implementation is introduced directly at the start-up meeting. the start-up will be a very pleasant occasion for both parties, this time the objective of the user's heart change process to explain clearly, to customer expectations and satisfaction management to lay a good foundation, so that users understand the implementation of ERP process will have a painful process, but the pain will eventually usher in happiness. Naruto field Brain drum an idea, in the implementation of the project weekly report on the dynamic implementation of the happiness curve, to the customer to imply: Now everyone is very painful is normal, and it is pleasing that in the near future, happiness will come, like the stock market rebound. (This is really something to try.)

4. take advantage of the enthusiasm of the start-up, and should be timely to make some awkward words clear. For example, our "change control" mechanism. It is possible to change as a project, how we define changes and how to deal with changes when there is a change, and in this case it should be understood that the negotiations to deal with the changes will be laid in place.

5. Finally, we should also introduce our success stories more. on the one hand to let customers believe that we have the strength to build a successful project. At the same time also told customers, if the project problems can not be accepted, the problem is not necessarily in the Mingyuan body, because we in the implementation of other customers have been successful.

This is a great sharing, we deeply feel that the interaction of knowledge from outside the company can bring more different gains, and this learning is very direct and efficient. Usually we are in line with our own implementation methodology, basically do not see how other companies are implementing the project, and this sharing happens to let us see clearly the pros and cons of our strengths and weaknesses. Complements our understanding and learning of the implementation methodology. Recent departments have also introduced a number of colleagues, hoping that these colleagues can share their valuable experience.

[Transfer]oracle Implementation Methodology learning experience