SAP Those Things - Theory -9-SAP project implementation five steps

Generally speaking, a complete SAP project will go through five stages (different projects, such as complete implementation project, optimization project, promotion project, nvidia partner operation and maintenance project, each stage has its own emphasis, but according to the project management methodology, these five stages will go through, pay attention to the project stages and implementation methods are still different. The implementation method is mainly how to start, plan, execute, monitor and close the project. All the implementation methods can be used at each stage of the project, and can also be tailored at different stages. These are also the five phases of the implementation methodology that has been used for many years, and may soon be replaced by a new implementation methodology, but for now let's talk about the classic five phases.

1. Start-up and preparation phase

At this stage, our main task is to let you know that the company is going to SAP, what SAP means to you, what are the changes, this time should give you an expectation, can show you the system demonstration, is also a better way, after all, now build an IDES system is still very convenient. In fact, most of the time, SAP Outsourcing it is not that people do not have the ability to bear or cannot accept certain changes, but that such changes are too sudden, which will make people unprepared, so it becomes difficult to accept or adapt to. It is said that the world is expected to do the best is the Federal Reserve, every time before interest rate increases and interest rate cuts will be repeated, over and over again, the future may raise interest rates or interest rates, listening to the ears of people have to get a cocoon. In this way, let the market have a sufficient adjustment time, then really raise interest rates and cut interest rates, the market has been prepared, the impact on the market is relatively small, the market volatility is also small. At this stage, In addition to starting the project team members (including contact information, job responsibilities, team structure), working environment (network, printing, conference room, etc.), meeting organization (frequency, participants, reporting methods), problem solving (problem recording and tracking), project delivery (document format, content, delivery time) and other a number of things to determine. Then we will officially start the research of the project, which is mainly aimed at the current situation. In fact, I personally think it is necessary to understand the current situation, but it is not our focus. We have said that enterprises choose mature software, in fact, to a large extent, it has decided that enterprises need to adapt to some characteristics of the software and design methods, design concepts, standard processes included in the system, including operation habits and user interface. Because these things are actually very difficult to make big changes. Therefore, the main purpose of understanding the current situation is to analyze the differences with the system standard process, and how to make up and adjust these differences. Therefore, in the project preparation stage, I can actually enter into the discussion of future process and operation mode, because the current situation should be closer to the future!

2. Blueprint design stage

This stage is to determine the future business process, which actually consists of two parts, the organizational structure and the process. smart waste management In fact, in addition to these two important contents, some details also need to be considered, including forms, reports, data level things also need to be discussed, related to the development list to determine, data collection also need to be synchronized. At this stage, the enterprise user and the consultant work closely together, and the consultant should patiently explain the user's problems, and do not want to muddle through. Our experience is that if you want to fudge a problem or think it is a problem, maybe think it is not important or want to ignore it subjectively, then this problem will certainly remain a problem in the future and cannot escape. We should not be afraid to encounter problems, all the questions raised by users are reasonable, and this "reasonable" may be a question mark from the point of view of our consultant or system. However, we consultants should know that users are unlikely to deliberately embarrass us, users do not understand the system, may be from their own habits of thinking or according to the existing system, existing business needs, their own job needs to put forward the needs, these needs may not be objectively reasonable, but it is no wonder that the user, from the user's point of view is actually understandable. So we say that there is no unreasonable demand, only unreasonable response, how to respond to the user is the experience of the consultant. In a word, for the problem, do not be afraid of the user to ask questions, in a sense, the more questions the user raises, it shows that the user really attaches importance to the project, really invested, isn't it? That's good for the project! Therefore, all the problems related to the project, especially those that may affect the progress of the project, need to be recorded and feedback, and can not avoid the problem or evade the problem! Many of the problems we thought, explained clearly, may not be a problem, because sometimes everyone's perspective is different, may have a different understanding of the same problem, explained clearly, it is not a problem! I have found that many of us are afraid of problems, which may be the psychological shadow caused by China's punishment for problems since ancient times. This kind of psychology is really not conducive to innovation and development, and the real problem is that "there is no problem". I personally have an idea, for research and development and creation, we should set up a system, that is, research and development results, then reward, research and development does not produce results, there is no reward, but there is no punishment, then the enthusiasm of the research and development personnel is higher.

3. System implementation stage

This stage is mainly the work of consultants, to implement the blueprints discussed in SAP, there are two ways to achieve, one is configuration, one is development. Of course, the problems in the configuration process may also need to be reconfirmed with the user, this time will reflect the value of experienced consultants, the more experienced consultants, because they are clear about the system and business, they will have confidence in the blueprint discussed in the premise and the implementation method, and the changes in the configuration will be relatively small and the test will be smooth. If something hasn't been done before and it's not quite clear how to do it, then more configuration and testing time is needed to verify it. The implementation phase actually includes the test phase, the complete test includes unit test (UT), system integration test (SIT), user acceptance test (UAT), the use and difference of these tests please Baidu. After these tests, and the user basically accepted, then we believe that the system has reached the use stage. Oh, this is similar to an asset that is ready for use and ready for production. The plane is ready to take off. Please remember your seat belt. It will be on-line soon.

4. Prepare for the launch

The preparation stage for launching is mainly data, of course, including the transmission of permissions, system configuration, the setting of the system front desk, system backup, etc. The data is divided into static data and dynamic data. The important task in this stage is to specify feasible online strategies and plans, assign specific tasks to people, implement them effectively, and supervise the implementation of tasks from time to time to ensure the smooth implementation of the launch.

5. Online support phase

The support stage is the stage at the end of the project and the improvement of the system, and lays the foundation for the subsequent system optimization. At this time, the important work is to establish a support system to ensure that users have a channel to reflect their problems, timely feedback and record their problems. This stage also includes the improvement of project documents, delivery, knowledge transfer, project summary and other work.

The above five stages (five steps) also cross each other, sometimes not so clear. But in general, the five phases are carried out in succession, and each phase also has the main tasks of each phase, and timely completion of these tasks helps the SAP project to be implemented smoothly. In the future, I personally believe that with the popularity of agile development concepts and the increasing frequency of actual business changes (this is determined by the real environment, with the development of technology and the general surplus of supply, all walks of life will provide personalized and customized products and services, which will definitely cause more and more frequent business changes), The start-up and preparation stage and blueprint design stage will be compressed, the system implementation stage will be simplified, the online preparation stage and the online support stage will be extended, and the optimization of the system will be continuously realized through iteration, that is, the short online, long-term operation and maintenance mode will become more and more common.

Finally, how to invoke the enthusiasm of the project team in the project, make the project team maintain harmony, stability and close cooperation, and obtain customer satisfaction, is an important responsibility of the project manager. After all, there is no essential difference between SAP project and other projects (such as research and development projects, real estate development projects). Both of them are guided by a team to complete a goal from the beginning to the end, and the general theories and knowledge of project management are used in the process, and people are the most important factor. PMP has a special knowledge field called "project human resource management".