Internet project management-who are the victims of the project?

Internet project management-who are the victims of the project? 9-12-7

When managing website projects, I think everyone may encounter the following similar scenarios:

1. I am not responsible for this function. I did not do this class!

2. There is a problem with the TMD analysis of this requirement!

3. Why didn't I make it clear!

4. The design of this data table is problematic at the very beginning and cannot be done now!

5. How do I know this? Ask them, it's not my work!

In such a scenario, people who have done project or product management work may still remember and may also encounter problems in management.

ProgramPersonnel should have been a job that requires a lot of creativity. How have they become a job that is especially resentful?

I feel that programmers are very tired and hard to work. The work of programmers has become the stress of life.

The pressure on managers comes from customers and company bosses. The pressure on programmers comes from the project manager, the learning pressure, and the change of project requirements.

More people who have done project development have deep experiences, fearing not innovation, not new technologies, but changes in work requirements, which is a fatal pressure.

Once again and again, the customer's words are not counted, and the Sales Department promises the customer everything, and the supervisor's mind gets into the water. This demand has also been made .......

The project stakeholders are under pressure from the project progress, project feasibility, project benefits, and so on. Why is this damn project dragged on? What I did was not what I wanted!

Who are victims?

Programmer? Project management? Project stakeholders ?.....

Everyone feels like a victim. Everyone completes this task with the psychology of the victim. This is the status quo of most companies in China.

What programmers see every day is that they are working more and more, program modification frequency is getting higher and higher, and module design is getting more and more complex.

The problem that project managers see is that the worse the project is, the worse the function is, And the harder the boss looks.

In the face of such a situation, everyone is thinking about how the project failed, and has quietly summed up the project failure experience, figured out how to put this project into the next interview

Failure points are used as chips for new jobs.

It would be a miracle if such a team would not fail the project.

Don't everyone communicate? The result is no. I think there may not be one communication. When the gap is reached? It may be temporary.

What should we do?

Every role must be able to correctly understand the position of the stage. programmers should get rid of the psychology and ideas of "Victims". The emergence of problems is definitely not caused by a person or a point.

Everything has room for discussion, solutions, and methods. What needs to be improved is your own mentality. You dare to accept the challenges and face the reality.

Every programmer is responsible for what he does. The most common problems encountered during the project are not technical problems. More are the reasons for the delay in the project, individual technical level and demand changes

Project time allocation. The allocation of technology and project time is relatively controllable, but why do programmers themselves have no better grasp of the project's working time?

It is not necessary to wait until the work has expired, and then discover that there are still a bunch of jobs not done, or there is no verification of its functions at all, resulting in the failure of the entire project to go online as scheduled, as a programmer, you should review your work

Attitude: Where is the minimum responsibility of an adult? Isn't it necessary for your supervisor to decide how many lines you write every day?Code?

In the face of demand problems, I clearly understand what kind of adverse consequences this demand may cause, but I still want to take over the work! This is obviously an irresponsible attitude towards work, or is basically not a professional.

Many programmers always report this kind of "hero to save the beauty" mentality. When there is a big problem in the project, he suddenly jumps out to blame, and then says that I have a solution.

From a professional perspective, please take a look at what your mind is playing with and what hinders your career.

The same is true for our project supervisor. It is clear that this project or function requires a relatively strong technical level, but an unfamiliar person is allowed to do so, resulting in poor functional quality, customers do not accept such cases.

Too many customers or sales demand changes do not reflect the direct impact and risk assessment of the changes in a timely manner, so they have to wait until the problem arises before regret, and then ask programmers to work overtime.

From a professional perspective, please take a look at yourself. What makes the progress of the project become uncontrollable, and what makes the system functions become more fragile.

If you are not a programmer or a project manager, please get rid of the "victim" mentality.