2014 project summary: a summary of a relatively failed project.

Recently, we will summarize some of the projects we have made this year, which basically contain all the processes of a project. First, we will provide some materials for our end-of-year summary. Secondly, we hope that we can bring more inspiration and lessons during the summary process, at the same time, I hope that you can give me some suggestions and criticism, so that I can make more progress. Thank you.

The previous blog roughly summarized a relatively successful project. If it succeeds, it will naturally fail. This project still makes me suffer, and even suffers from mobile phone phobia. When I hear a call from a mobile phone, my body starts to tremble. I hope this project can be completed earlier, otherwise, problems may occur sooner or later.

Similarly, the background of the project is briefly described. This project is also a supporting software for a product of a research institute, but the customer does not consider this project very much. At the beginning of this year, the customer asked us to begin to sort out the requirements and propose solutions. The customer's contact person was directly the Director (the Director was originally the top manager, then he was demoted to the top four for some reason, but still the Director ). At the beginning of this project, we planned to have a department manager L (Note: it is not a project manager) be in charge of both me and me. l manager is in charge of personnel management, I am responsible for technical and new personnel training (there is no way, most of the software companies are like this, almost 1/3 of people choose to change jobs after the end of the year, less C ++ developers in our company ). L The manager and I went to the customer director two times and found that the requirements were still very complex. When I started preparing training courses and writing the underlying code, we lead a new employee song X with 8 years of work experience. So this new employee replaced my role and I was put into another project. Since I only talked to the director twice, I quit the project even though I was not involved.

Let's start to describe the development process of this project. The main programmer of this project is Hu X. Hu X has worked on a project with me and graduated for one year. I planned to leave my job at the end of last year, and then I spent a lot of effort to persuade him to stay. However, it is estimated that I would like to leave. Department Manager l found 5 Java developers from his department, and added 8 developers to Hu X and Song X. a c ++ development team was successfully established. By the way, Song X has been working as an outsourcing engineer for Japanese projects. He is good at Japanese, but not c ++.

The project requirement sorting process involves the participation of manager L, Song X, and Hu X. Each time the three of them go to the customer side, listen to the requirements, and sort out the requirements. I don't know why the demand sorting process lasted for two months, and song x resigned. At this moment, Manager L has no response to this problem. Maybe he doesn't think so. The general requirements have been sorted out in early April, And then he arranged Hu X to write the basic architecture. Hu x spent half a month writing a basic architecture, and then the other five Java developers started development. In early May, I went back to the company for a few days. Then, Hu x asked me why the CPU usage at the first startup of the software would exceed 50%? I don't know about this. Let's take the code and show it to me. As a result, manager l said that this project is a confidential project and the Code cannot be passed out. I can go to Hu X's machine to view the code. Then I did not go.

During October May, Hu X called me and said that he had to leave the company immediately. He didn't want to stay in the company for a day. Ah, now, before leaving, I asked him to have a good meal. After drinking two bottles of beer, I told him that it would be nice to mix up later. Don't forget me. My commitment has been stuck in our company for at least two years.

In early June, it was the agreed delivery period for this project. The manager gave a copy of the product to the customer director. The customer Director is also very talkative. We accept things first. After our product is developed successfully, we will start to call your code together. As a result, manager l immediately disband the development team, leaving only one female programmer Qi x corresponding to some changes, and all four others left.

In July, Qi X told manager l that she was preparing to take maternity leave and may start taking the leave in July. Manager l said, OK. In August, the customer successfully developed the product and started to call our software. Qi X told manager l that I am not very comfortable now. Can someone else replace my work. L The manager ignores the problem and says it will soon end. It will certainly end at the end of August if he persists for a period of time. In early September, Qi x said that he was adding at least one person and that there were too many customer changes. Manager l said that the application would definitely end at the end of September and insisted on the application. So by the end of September, Qi x couldn't hold on any more. It may be that his body could not hold on, causing some imbalance in his mind. He had a tough fight with the customer. After the quarrel, he directly applied for maternity leave, then you will no longer be in the company. The Ministry of Personnel asked her, and she cried with tears. As a result, the Ministry of Personnel took her, and no one dared to bear this responsibility. As a result, people are lost.

Customers naturally feel aggrieved. They feel that they are Party A. Why have they been scolded by Party B? As a result, the customer finds their leaders and their leaders directly freeze all our contract processes. Then our leaders panicked. At this time, our leaders finally began to panic. He was particularly surprised how the project was not over yet. He called Manager L and asked about the situation. L The manager has been emphasizing objective reasons, so the leadership is on fire. We have six projects with them this year. Other projects are late than you. So I am miserable. The lead asked me to finish scanning !!!

I have almost no idea about this project, no handover, no documentation, almost no comments to the Code, and the logic is also chaotic. In most of the IF Statements, at least three if statements are nested. The most exaggerated one is that there are 11 if/else statements in an if statement. The customer was also a female, so I looked for her with a thick face. I can't understand the code. All the people involved in this project are gone, except the L manager. So I bought a lot of fruit to get started with the code, and ran to Qi X's house with a thick face. I claimed to visit her, but asked questions with my computer.

This project should be regarded as a relatively failed project. Due to this project, all our other project contracts were interrupted, so all the project awards were ruined. I am also very hard-pressed to plant this project, and I am the only one. Originally, I was planning to have a hot pot singing song to the New Year Program awards and year-end awards. The result is only tears.

Summarize the causes of project failure:

1) unstable project personnel. The project was established from the end of the year. This node happened to be the most mobile time for software companies. Song X, who had the most involved in the demand sorting, resigned from the project to the demand sorting, this resulted in unclear requirements. The departure of Hu X in May basically predicted that the project had basically failed. Although Hu X's architecture is not stable, after all, it is his main programming and he can solve the problem. In June, manager l directly disband the development team and let all four developers leave, while Qi X has told him that he is about to take maternity leave. Therefore, all participants in this project are lost.

2) Unclear requirements. At the beginning, the customer clearly stated that the project should be developed in two phases. The first phase is the basic version, which can meet the functions of most of their historical experience. The second phase is the joint debugging of the actual products. However, Song X's departure and l manager are not directors, so all of them think that the first phase of development is complete. However, the customer does not care about the basic edition. What they need is that the debugging can be successful on the product, leading to our misunderstanding. At the same time, due to some changes in the customer's product development process, our procedures cannot be changed in a timely manner. The change control is poor.

3) chaotic project management. First of all, Manager L is a department manager, not a pure project manager. He thinks his job is just about counting attendance information. At the same time, before the project began, there was basically no C ++ training for employees, and several Java programmers were directly found. He even said that Java and C ++ have almost the same syntax, just write it. Before Hu X, he only worked as a C ++ project, but his development experience was still lacking. Our leaders have already clearly told l manager that Hu X may leave in middle May. At the beginning of May, when the project entered the coding stage, I tried to read the code but refused my requests with confidentiality. This made me sad. When the customer proposed a change later in June, manager l directly disbanded the project team, which was shocking. At the same time, the project has no documents, no tests, and no code specifications.

4) there are major problems at the end of the project and the handover process. When Qi x explicitly proposed maternity leave at the end of June and early June in June, manager l did not agree or even care about it. Until Qi x handled her project in this extreme way and ended her work, I still felt that Qi X was not making a big mistake. There is always no way to make a woman have a big belly for a few months. Every day, she needs to drive her car for more than one hour, walk for 30 minutes, and face a lot of radiation (high radiation, full of radar) stick to work. When our leaders break down our contract process among customers, Manager L is still complaining about improper handling and poor customers. This project has no handover process and no documentation is readable. In this way, I am also sad. The only transfer process of this project was that I was forced to fail. I took the fruit I had paid for and ran to Qi X's house. I asked her to talk about it for an hour, then she was blasted out by her mother-in-law and said something in her mouth.

5) the customer may not pay special attention to this project at the beginning, until their leaders start to pay attention to it.

I don't know when this project will last. I hope it will be over soon. Then I can sing songs around the hot pot to celebrate the new year. Then write a summary, write new knowledge learned this year, and think about how to break away from such a life, or find a new direction or opportunity.

Summary of the five projects that we have participated in since 2014

2014 project summary: a successful project summary

2014 project summary: a summary of a relatively failed project.