Project management discussion-leave or stay is a problem!

In March and April each year, it is the peak of talent flow. For the reason, I will not talk about it here. This is not the case. Some people in the project team are leaving. After a few years of joint efforts, suddenly some people are leaving. Although they are reluctant, they have their own aspirations and cannot be forced to stay.

I have summarized the job-hopping of programmers. Generally, the importance of each indicator is shown in:

 

The following figure illustrates the impact of job hopping:

1. SalarySalary is the top priority. In general, resignation or job-hopping are aimed at salary. After all, our country does not pay attention to sense of belonging, and our social welfare and other aspects have not been able to make programmers feel comfortable, many people still want to eat mixed meals to solve the problem of food and clothing. Job-hopping is the fastest way for common programmers to raise salaries.

2. Position: Job improvement is also an important indicator for programmers to change jobs. Generally, a new employee is a basic job, such as a junior programmer. if the job is still in the next two or three years, in addition, the company has no plans for improvement. If you change jobs at this time, you will generally go to the job of senior programmers. Likewise, some will go from senior programmers to project managers and technical managers.

3. StabilityIt is also very important. Now we can see the number of people who apply for an exam for Civil Servants. Many people will also change jobs to pursue job stability. At this time, the target is a relatively large and stable company. Especially for many 30-year-olds, the pursuit of stability is the focus of their attention for the purpose of maintaining the old and the old, who puts so much pressure on our lives.

4. Interpersonal Relationship: Sometimes job-hopping is due to the complex interpersonal relationships of the project team. Some programmers do not have team awareness, which leads to continuous conflicts in the project team. If this problem occurs, you should consider it carefully, even job hopping won't produce good results, but it's still the same for other companies.

The above describes several important factors from the basic perspective, but other factors may also be decisive factors, such as job hopping for marriage and so on. The advantage of a jump is that after a jump, the salary and position may be improved, or there is more room for development. But there are also some bad aspects, such as adapting to the new environment, new interpersonal relationships, and building new connections after the jump. If the jump is too frequent, it also has an impact on my professional reputation. When I am in charge of recruitment, I will immediately drop my resume into the recycle bin if I see a person on my resume for a year. Then let's look at "stay-at-home", which means persistence. The benefits of staying-at-home: working in a familiar environment, there are a group of siblings who can get along well with each other. If the company develops well, as long as your value can be reflected, improvement is inevitable. However, in a short period of time, the salary or position may not be greatly improved. In addition, even if you want to leave, you have to wait until you have done the task successfully before leaving, rather than escaping.

It is a loss for the project team because the employees have changed their jobs. Let's talk about the composition of the project team and the phases of the project.

Project Team Composition: I divide project team members into two categories: backbone members (project managers, senior programmers) and non-backbone members (ordinary employees ). The job-hopping of key members has a great impact on the project team. for small companies, it may even lead to the end of the project. The job-hopping of non-backbone members has little impact on the project team. It is only necessary to complete the handover. Currently, non-backbone members are in the oversupply stage.

Project phase: the project is divided into the initial, middle, and later stages. In the initial stage, it is in the demand analysis and design stage, and the backbone members have a great influence. In the middle stage, a lot of work is coding. At this time, the role of common employees is also relatively large, and there is a flaw in radish, after the process is completed, someone needs to go to the top; otherwise, the progress will be affected. In the later stage, the project is basically finished, and the code workload is small. As long as it is not a mess, if the relevant handover is completed, the impact will be relatively small.

The above is a simple analysis of the process and retention, and the programmer must make his own judgment on the process and retention. The programmer should do more analysis from various aspects and weigh the advantages and disadvantages before making a decision, if you want to show your strengths and weaknesses, do not expose your weaknesses to others. Otherwise, you may fall into a strange circle of job-hopping, the formation of the habit of Job hopping is not conducive to your career development. When you have made a decision on your choice, it is no longer a problem to leave.