3. Check how Project X fails from the errors made by Project G.

SlaveGLet's see how the project fails.

 

The article on the development history of the project mentions the mistakes that G has made multiple times. Let's make a simple analysis and look at the causes of the failure from the errors made by G.

 

1.GProject management and design and development, and I don't want to participate in demand research any more, but the supervisor said he was very busy and didn't have much time to research and write the requirement documents, the company had no special demand research personnel, so it had to accept it.

 

G has already held too many positions, leading to the inability to do a good job. It also needs to pick up the next thing that can't be done. This results in less time. Insufficient time will cause more problems:

1) because there is a lot of pressure on the job, in order to be able to finish it on time, it must be done in a random manner, saving the province, and the final result is that the quality is completely inadequate.

2) There is no way to make a valid summary review

3) in the long run, it will inevitably lead to psychological imbalance and boredom, from happy work to catching up with ducks.

4) if the above three points are connected together, a disgusting cycle will inevitably occur. Eventually, people will crash or projects will crash.

 

Currently, the only solution is to actively and patiently communicate with each other, to actively persuade supervisors and leaders, and to allow the company to arrange individuals to investigate requirements and share G's other work, enables GTO focus on program design and development or project management. In the above reply, many people mentioned the importance and problems of PM, and the multiple roles including G and PM will inevitably lead to project problems, ignored by X project team members, including lead supervisor and G.

 

 

2.People are afraid of comparison if they are not afraid of hard work. They can survive the hard work. However, it is totally different to have such a comparison between people.GIt's a baby from the countryside. I'm not afraid of it. It's just that you 've been busy all day long and people are sitting next to you.QQReading the news is quite uncomfortable. The most important thing is that the idle master still needs to listen to the younger brother you commanded.

 

This is a psychological factor, indicating that G's psychology is not calm. One of the reasonable solutions is probably the same as the one in 1, which allows people to share G's work, so that G can concentrate on his own strengths. In addition, it refers to the reasonable flow of personnel. For employees who cannot meet their job requirements, they should be replaced or supplemented in a timely manner. On the one hand, it will not cause dissatisfaction of other members, and on the other hand, it is also a necessary condition for project success. The central idea of agile development is people-oriented. It is difficult for a project to succeed if people are confused. Li Shu said, the hearts of the people are scattered, the team is not good, so Li Shu was arrested.

 

3. QIn terms of expression, there are some problems, that is, they cannot be understood.GYou can only give a clue after asking questions many times. This causesQPairGSome dissatisfaction and Resistance

 

This is one of the serious consequences of poor human management. G obviously lacks the kind of leadership ability to let others work for him or the company. This point has already shown in 2.

 

4. ConnectionGMr.

 

In a certain sense, G is the owner of Project X, and he takes the lead in front of the Members to express dissatisfaction with the company, which will inevitably lead a very bad impact to the project team members. This action shows that G is not mature in the management of this position and has not considered the problem in the general direction, but is just a sigh of relief. This will shake people's minds.

 

5. MSubmit the request and modify the modification, and immediately start the operation.MSir review, release in almost a week2To3(Release here refers to releasing the program to the test server for trial and review by the customer)

 

This is obviously because the project management is not well done, it is simply to hand over the project to the customer. The release of the program consumes a lot of energy. After the release, all kinds of errors and exceptions discovered by the customer may require immediate correction, which sometimes leads to multiple releases in a day, because of a few small errors, it takes time to modify, release, modify, and release.

Solution:

1. Release Based on a long period of time, but should not be too long, such as one week or two weeks. After consultation with the customer, the current release version error will be postponed to the next version.

2. Invite customer representatives to participate in the project progress meeting every week. Let the customer know the progress of the project every week and relax his mind. It is agreed that the beta version will be released once a month to allow the customer to test the experience and Relevant Problems, which will be fixed in subsequent versions.

3. Control the acquisition and change of requirements, such as requiring the customer to form written documents and submit requirements.

 

 

6.GAfter being overwhelmed by so many tasks, defect management is totally self-defeating and thus gives up.

 

G. It is sad to give up defect management because it is too late. Defect management can be said to be one of the guarantees of product quality. The long list of defect management scream to remind the project of problems. This is the most conspicuous alarm for quality problems in a project. Without defect management, it is almost difficult to supervise project quality. The lack of defect management at the beginning and later proposal and abandonment determine the inevitable failure of the project to a large extent. What is the success of a project that does not focus on quality? Even if all the functions are completed, do you dare to put them on the public network to let hackers wander around for two times?

 

 

Referring to a response to the development history of a project, I personally think that this response clearly points out that G is unqualified as a PM:

# 20th floor

By huyong

About you:
"Oh, yes, the PM problem.
The first problem is that there is no clear PM for this project.
The second problem is that the PM (that is, G) cannot exercise all PM power and is disturbed by the supervisor.
The third question, objectively speaking, is that G does not have the possibility to devote all his efforts to PM work. He also holds many other positions.

I will write another question about the existence of G. I guess it will be sent tomorrow.
"

1. If there is no clear PM, the project implementation is more difficult and likely to fail, and the company's management system is problematic.
2. PM has no real right: it indicates that your company is a rank-based or matrix Company, and employees face two direct superiors. At this time, PM is the most helpless and the only thing you can do, is to get the support of the largest leaders first, and then let the PM let the project go. Otherwise, there is a high possibility of failure. To be clear, it is also a problem of PM project communication.
3. PM is not fully engaged in work, there are reasons for PM, and there are also reasons for the company's system. If you have such a system in your company, a PM with no real right equals no PM, in fact, he is helpless and there is no way.

In the end, the project manager is required to win the project team. Communication, communication, and communication.

 

 

In conclusion, the lack of G project management capability and immature psychology are highlighted. This is a major cause of project failure. I hope that you will be able to raise more questions about G and provide corresponding correction suggestions. I am very grateful.