I wrote to XXX [serialization] Three years later-1.2 The pain and joy of project execution

Chapter 1
1.1 1.2
1.3

1.2 project execution pain and happiness
[Borrow a diagram from instructor bai]

OK. The first project meeting has been handled. On the way back to the company, I breathed a sigh of relief and suddenly came up with the words of a big leader: Prepare a PPT next time. I'm so happy to go. Please pay attention to it later. We are sure we want to do this, and it is estimated that the deployment will be launched soon. After returning to the company, I quickly pulled my partners and told me the situation. (The team of the first project mentioned above is actually two of us, handsome. I pushed myself to the front and gave myself an illusion of the identity of the Team Leader. Why is it hypothetical? Because the guy was just like me, why did he listen to me. Well, I have a solution. You can check it out)
[Plug-in: my partner was the first to appear in the game. He called him-Zookeeper. He is now playing well in other cities. Good technology and many ideas .]
Me: "zookeeper, I went to the meeting today. It's a big project, it's time-consuming, and the task is heavy. Leaders pay great attention to it. We have to do a good job ".
Growth cycle: "How long ?"
(It's too calm and professional .)
I did not say the cycle in two voices;
"Our new one-card program hasn't been done yet. It's just a design. Do the leaders know ?"
(Why are there so many problems. This guy beat me down. Do you think the logging handler is like a leader ??)
I didn't say anything. I went down and started to get hurt.

All right, make up your mind to go back to the project and start from scratch: exploration of user needs in the early stage, system architecture design, system function cases, detailed design, database design, development, testing, deployment, trial Run, maintenance... (My God, it's really complicated)
First of all, we must make a presentation PPT for this project, so we can communicate with the user next time and quickly understand the user's needs. Remember not to simply understand the needs, instead, it is necessary to guide and develop the real needs of users so as to improve the usability of the system (now many systems are overwhelmed by poor sorting of user requirements in the early stage, it is necessary to guide users on the basis of your understanding of the business to help users explore their needs. However, the final requirements must be expressed in the user's mouth and satisfied, ).
Next, I wrote a development plan and sent it to zookeeper. This time, I am a real developer, but it cannot be.

 

As I expected, a few days later, I informed the second user project meeting. OK. This time I was well prepared. It was quite good to play on the site. Of course, the PPT was also good. You will come and visit me, discuss user requirements (1000 words are omitted here, and those who are interested will discuss it below). Finally, the senior leaders are very satisfied and think our company's system is very mature, very suitable for them (I smile, haha, the system is still in the womb ). I also received high praise for my PPT, And I was praised. I am here, too. On that day, the vice president of our company in charge of this big project also went. After returning to the company, I was praised and became famous at the project meeting. Be energetic, come
On. [Plug-in: when talking about PPT, you really need to study it well. Don't be too fancy. Focus on it. Use dual-screen playback and add remarks, in this way, you will not be confused about the projection.]
Of course, there will be continuous project meetings and discussion needs in the future, which will be conducted almost once a Monday, twice a week, and then on call. It's hard, but it's always fun. In the end, I had to change the small one-card system (tens of thousands of cards) in the original big project to several hundred thousand, and finally the leaders paid great attention to it, take the system out and sign the contract. So, this project is really my first independent contract project. [I would like to thank all the leaders and colleagues who helped me during this project negotiation, as well as the leaders and Comrades of some newly recognized cooperation units. Good guys]

Besides, the system development progress has been paid attention to in the company's project. The project will also talk about the Spirit: it must be completed with quality and quantity, and be done well! Therefore, I have paid more attention to it. I took the initiative to discuss with me the system solution, Development Plan, and even the division of development work. But sadly, we have two people, and the division of labor is nothing more than me.
Soon the contract was confirmed and the system entered the development stage. Speaking of code writing, I have perfect cooperation with zookeeper, and we have two sets for the card system (there are stories here, and there are more sets later, they are all different. You can see it later, because we are professional ). I am responsible for the interface development of the device hardware. He is responsible for the business process. Two people do not need to communicate too much. After the joint debugging, there is basically no major problem. It will soon enter the inner side. Cool. However, it was not long before this happy development life was completed on the inner side, and some system problems had to be corrected. At this time, the leaders informed that the system should be put online in advance, and only one month, including procurement of servers and equipment, and on-site installation and debugging. I'm so nervous. This is really the project owner. What project company registration, device procurement list ....... I used to assume that a large company has a dedicated person to handle the heap tasks. Later I found that a dedicated person is responsible for the services, but a dedicated person does not serve me (everyone understands ). I have to handle all my tasks by myself. I have no way to handle the test changes. I have to coordinate with the manufacturer, ask for the goods, and make a list.
Do you know that the most difficult thing in the world is to ask the manufacturer to deliver the goods to you without any money. It's up and down, and it's all about coordination inside and outside, for a person like me who has never been in touch with these things, it's hard for my wife. No way. Bid your teeth, hold your teeth, find sympathy, and use various methods. During this period, there were countless problems, large and small. At that time, I thought that this was the case for such a small project. I went there and asked what would happen to tens of millions of projects. Finally, I finally understood, dedicated service! Haha
So the more difficult it is to be a project trainer, the more effective it is. Our technical control programmers should seize the opportunity to exercise and complain every day, it's useless to say that God doesn't want to see me or anything. As a program and a person, you must improve your work at the same time. At that time, money and money will be brighter.

The time has finally come for on-site debugging. But the server didn't arrive. I went there. What's the problem? I couldn't help but find a PC and use it as a server. When the server arrives, perform a migration. On-site debugging is even more difficult, because it is a newly created building, and everyone is scrambling for work. The on-site environment is poor, so there will be a power outage in a short time, and the network will be different in a short time. This guy, this system debugging. It's so bitter. Here we omit the 300-word complaint.
After debugging is complete, go to system deployment. First, coordinate with the user to bring the user's basic information, unify the format, and import the data to the database. It seems like it is a technical activity. In fact, it is not the case that such materials are included in the business systems of different companies, but also the user's OA system. This coordination is too troublesome. I ran back and forth, and my legs were broken. I didn't want to talk again when I went home every day.
After the trial run, the materials have not been fully imported on the first night of the trial run. As a result, programmers are familiar with it. Stay up late. The next morning, the trial run was successfully started. We were very happy to watch our employees use our system in novelty.
It is not a long time, because the data is organized in a unified manner, there must be something wrong in the middle, this time it is troublesome. There are thousands of people using cards, and some people cannot use cards. It seems that they have suffered unfair treatment. Hurry up, say something nice, say the system trial run, and then check the problem, fix it, and send it one by one with smiling faces. I have a deep understanding that it is really not easy to do in the service industry. You should be polite when you go out for consumption in the future. Thank you for your patience. Haha
This kind of trial run time has finally come, and it takes a long time. During this period, the user has adapted to the new system, the system is running on the right track, and the server is also present. It is also an all-night solution that deploys servers and migrates data. After that, go home and have a good sleep.
The subsequent things will not be here. Everyone has the project experience, and the subsequent things will be very generic. Of course, in the later stage of the project, the key point is to have a good relationship with the user, which is very helpful for maintenance.
The following describes how to maintain customer relationships. Generally, there are two types of customer relationships. One is the customer leader, who generally focuses on the unified maintenance of the company and generally does not care about the specific business, but those who have never asked the underground workers to respond up and say that your system is not good. What's the problem? If you get complained. That's terrible. Everyone should have experience. The other type is the specific system user. You need to maintain these people well. When you are okay, make a phone call or go to the site for inspection and talk to them, and instill in them some ideas about the use of the system, do not always say that your system is not good because of their misoperations. If there is a problem, hurry and solve it. Of course, you need to talk to them frequently about parents. Help them do their private affairs, so they will owe you a favor, and they will try their best to help you when there is a problem with the system. (In addition to money, human feelings are very useful in this year. Handling customer relationships, acceptance, maintenance contract and function addition are not a problem. Well, everything goes well. This is a high-quality customer trained by myself. It can be retained for a long time. If you have a startup idea, you must have such a customer. (Understand ?)
Well, this is the first perfect project story. To be continued... the question in the next section is "the confusion of programmers who are stepping into the beginning".

Chapter 1
1.1 1.2
1.3