A failed project

As the saying goes: Failure is the mother of success.

As the saying goes: without summary, there will be no progress.

When I knocked on the question, it seemed that when I took over the project again, what was deeply imprinted in my mind was the error of no reason and endless modification, the launch time is postponed again and again ......

The project started one day in March, and the boss asked me to write a function to connect to the SAP system, so that we could transfer our system data to the SAP system and query and read data from the SAP system, complete coding and testing. One day in March, the boss had to take some time off and asked me to take over the management of the project. The project was scheduled to go online one week later.

I got the unclosed bug document and found that most of the problems occurred when I exchanged data with the SAP system. Many problems have not been solved for more than a month, I am worried about my own code. After careful communication and testing with SAP developers, we found that most of the problems were that the customers and product materials we transferred to the past did not exist in the SAP system, resulting in execution errors, as a result, the re-write program reads customer and product information from the SAP system. After the new data was transferred to the SAP system, some logic problems were found in the SAP system. After the change, the test finally found the problem of data processing in our system and corrected it. It took about half a month to complete this round and the project was extended for the first time.

After the time for re-launch is agreed, the customer re-tests and asks a new question. The system gets a wrong price for the return. Check the logic in the code. No problems are found. After communicating with the customer, we found that the original system did not achieve the desired effect of the customer. That is to say, if product A is sold, the quality problem is changed to product B, and the problem is changed to product C, after that, no matter how many changes are made, assuming that the product is finally replaced with product e, there is still a quality problem at the end, so we have to refund the product (BTW, a customer in the US, may not be able to get a refund in the tianchao ), in this case, the price of product A is not to be refunded (the price of product e is returned by the system. If you want to discuss with the customer whether the product can be launched first and then supplemented with this function, the answer is no. Because the old system does not have this function, it is very troublesome to manually perform each refund operation. Otherwise, there is no need to launch the new system. There is no way to continue the modification. The problem comes again. Our developers write all the business logic in a bean, and the methods in them do not know which ones are shared, it is often the case that the problem occurs here, and the problem occurs here. The project is naturally postponed.

Through the joint efforts of developers and I, the system is running normally. However, the test is not optimistic and some bugs cannot be reproduced. After discussion by the three parties, some of the reasons are that the SAP system cannot be connected. After re-discussing the launch time, the boss finally came back, and the time has reached the Middle and Late October.

Many formal data needs to be captured in the database of our system from the SAP system and the Warehouse Management System in the early stage of the launch, and there are millions of such data records, some business logic needs to be processed by Java programs. The damn PC can only process about 100,000 of data at a time ...... As a result, my daily work changes to manual parameter modification, packaging war files, and repetition. Finally, after more than a week, all the data lay in our database. At this time, the customer proposed to use the production machine test, Mg, and another problem, the project was postponed for the third time, And I collapsed.

Fortunately, the boss turned around for me and the customer and re-discussed the launch time. At this time, another blow came. In the financial crisis, the company cut the only developer of this project, leave a bunch of horrible code (as mentioned above ). Just as it is close to the end of the year, and I have not yet been able to show the above results, the boss arranged for me to be responsible for the development of another new project, saving me from the fire. In the end, this project is complete.

From this project, I have summarized some problems:

1. I did not pay attention to the demand analysis and started coding too early. It is manifested in the customer's demand for replacement until it is finally discovered. We know that the later the customer finds the higher the request modification cost;

2. Insufficient technical support for developers. It is manifested in writing all the business logic in a bean, which leads to a pull;

3. Insufficient resource allocation and insufficient cooperation from other departments. The SAP team sent an intern to cooperate with us only when the performance was determined by the SAP system test;

4. Insufficient technical support for SAP developers. Interns in the SAP group did not learn the SAP system for less than three months, and they could not discuss the problem with their group members;

5. The communication cost is too high. The performance is sometimes different from that in the United States. You can only call people when you first get to work in the morning, and all other times rely on email communication;

6. No one in the project has dealt with the SAP system. This is also the first time I have written a string to connect to the SAP system;

......

And so on. To solve these problems, we can find some solutions:

A. carefully analyze the requirements and try to postpone the coding start time;

B. Let an experienced developer bring a experienced developer to regularly hold code review to prevent nonstandard coding styles;

C. Support from management is required;

D. Same as above;

E. It's good to send me a business trip to the United States;

F. Introduce a person familiar with the interaction with the SAP system, or ask special personnel for guidance.