From technology to management, what have I done to save myself?

I am a novice project manager, transfer project management post 1.5. Before I did the management, I was a developer. In other words, I am the most common technology transfer management.

At first, I was extremely uncomfortable with the position. Very tired, but no results. After more than a year of groping, I finally summed up some experience in the work, some routines. So I want to give the technical management of the students to talk about:
What have I done to save myself

Personal background and company background

1. So far work 4.5, that is to say, I did 3 years development, 1.5 management
2. I am a wild programmer (non-computer professional graduate)
3. I've written about Android, IOS, Web pages, Java backend, Python backend, and so on, looking like a legendary full stack programmer. But in fact, I know that I am the kind of programmer who can do nothing.
4. The company has previously made products, and later on the basis of the product transformation outsourcing to expand the scale
5. On the basis of corporate transformation, I have also transformed into a management
6. Our Project Manager is a dedicated position, responsible for project management, technical architecture, customer docking. The project manager is responsible for all issues related to the project, including technical issues.

What hands I do, it destroys the team and destroys myself.

This is probably the fault of all the people who have been transferred from technology to management. When I first started with the team, the core code was written by myself. Then look at the progress of colleagues always think of this slow, that can't. I can't see it. Chi Chi write well. Made himself very tired.

People with strong technical skills often have the opportunity to transform their management posts. So in the process of bringing a team, you always can't help yourself to do what others should do. The end result is always replacing colleagues with what they should have done.

But this behavior for managers will only make managers more and more exhausted. For the whole team, it is warm water boiled frog, step by step to bring the team into the abyss. Managers are burdened with too much work, resulting in long-term inability of the team to grow. Light causes the manager to collapse. The project collapses and teams fall apart.

What should I do:
In fact, it's much harder to influence someone to do something better than to do it yourself. And the way I deal with this problem
1. Try to resist your own hands-on mentality
2. Complex task disassembly refinement, assign tasks to clear task objectives and acceptance criteria
3. To give encouragement to colleagues when assigning tasks and to maintain full confidence in them
4. Difficult tasks, provide a certain degree of assistance or training

Think more, say more, do more

When I started to bring the team, I was busy with various project issues, writing code, communication requirements, progress reporting, and live demonstrations. Most of the time is buried in the project itself, thinking that as long as the project is done, on time delivery on the line. Doing too much, leading to less time to think, and less attention to team colleagues.

And a team leader, do more is should, more important is to think more, say more

Think about what:
1. The project stakeholders are clear, the stakeholders are unclear will lead to project management confusion, out of things do not meet the requirements
2. Whether the demand is reasonable, whether the demand can be optimized, whether the technical framework satisfies the demand
3. Whether the function is disassembled in place and whether the assignment is reasonable
4. If you are trying new technology, are you sure to make the most of the problem?
5. What is the status of team members and how to motivate them
6. The project process is reasonable, how to improve
7. How to control the project cost, how to grasp the time node, how to ensure the quality

These are all things that I think about at the moment in every project. Project managers must warn themselves:不要用战术上的勤奋掩盖战略上的懒惰

Say what:
1. Need not clear to ask
2. Needs can be optimized to say, do not muffled the big wealth, the pit is their own
3. Difficulties can not be dealt with timely reporting to the leadership, know the customer
4. Team members have questions to give correct guidance, rather than laissez-faire
5. Progress, project situation to actively communicate with customers

Not just the supervision, but the guidance.

"Is that function done?" she said. "The function is not well done"; "When will you finish this thing?"

These are the most common things I do in my daily work, and even now I'm still doing these things. Supervision urges colleagues to work! Every day like a supervisor, walk around colleagues, supervise their progress, in their ears forced jutting.

But I think that urging colleagues to work should not be the project manager, but the project process, is the rule. Everyone is clear about their roles, their duties, and the rules are bound to move forward. Instead of simply relying on the project manager to drive everyone forward.

But I am not doing this job well, and I am still in the loop of planning and supervising execution. There is only a vague idea of the rules, the process is not formed, also untested. Not to share with you.

Fire fighting ability is important, but also to prevent the

I was at the beginning of technology management, the most good thing is technology. So it has been the role of firefighters in the project.

Have a sudden situation? I'll do it myself, no one can conquer the technical difficulties? I've been developing it for a long time, and I've found that needs are misunderstood. A click to make a change of his own; In short, this is a problem, a click on his own meal, that there is a problem, click on his own meal. Always use your own technical ability to save all kinds of emergencies in the project.

As a project manager, the fire fighting ability is important, to be able to stand out at the critical moment to the tide. But more importantly, I think it is how to avoid unexpected situation. To avoid unexpected situation, we should think about how to do the risk management. Be prepared early and nip the unknown risk in swaddling clothes.

In IT project management, I think the risk exists mainly in the following points, should think about preparing to avoid risk:
1. Changes in requirements. In the development of the demand change is inevitable, but how to control the change in demand, how to manage the change in demand is our focus to consider the issue. Scalpel method, we can understand
2. Project stakeholders are unclear, resulting in divergent project requirements
3. Technical difficulties are not estimated. There will always be the development process to send a certain function can not be implemented or the implementation of high cost, mainly due to the early understanding of the needs of the lack of self or team too self-confidence caused by
4. Plan development issues. Development planning is problematic, possibly due to the wrong estimation of the team's ability to project difficulty. Program risk is usually created by the project manager himself and needs to be self-reinforcing, learning, thinking to avoid this problem
5. Organizational membership issues. Lack of development members, staff turnover, other projects need emergency support staff, team communication is not smooth can cause this problem
6. Process risk. Too much process, resulting in process work taking up too many development time, process and flexibility are a pair of conflicting concepts. How to solve the problem of process and flexibility in project management, I think it is one of the more important ability of project manager
7. Performance issues. In the development process, the most feared is the function is finished, finally found that performance is not. Lead to early development work in vain. Therefore, in the demand phase, the user volume of the software, the amount of data are to be taken into account. At the beginning of development, it is necessary to consider the performance problem in the process of programming.

Keep your Heart strong

Project management is a torture work. Although the outside said to do risk management, but the unexpected situation can not be avoided. A qualified project manager, to have Tarzan collapsed in front of the color unchanged heart.

It doesn't matter if the requirements change, the plans change, it doesn't matter what happens to the members. After all, we all know 世界上唯一不变的就是变化 , as much as we can get ourselves ready.Plan B

Blame to go, credit to go.

I believe that when you do the development, the most annoying is the kind of the blame you back, active he led the leader. In that case, I hope we will not become such a person.

Project manager, manage everything about this project. The project has a problem, for whatever reason, it must be the responsibility of the project manager. Your colleagues may not perform well on the project, and your customers may often change their needs. No matter how many reasons, is not your reason to throw the pot. A pot must be carried on its own, so 背黑锅要上 .

Do good, also want to say out. Exceed customer expectations of the project highlights, to tell the customer team excellent. The project is done well, to tell the boss of the team's excellent. Let the customer let the boss know your team is doing well, the next time they will give you more full trust. The performance of the project members of the place, not only to praise, but also to speak with the superior. You're the closest person to your team, and they're a bit of someone they don't know, but you know. So they are good places, to preach, to let other departments know, to let the superiors know. So 邀功也要上 .

In the gang, not for the brothers to stop the knife and lead the brothers to advance the eldest brother is not worth following, the brothers in your work has been wronged, can't fight a breath, the boss also do not long.

I believe that 背黑锅要上 everyone can do it in the technical background of the manager. But the technical staff is not talkative, always work, not express. So we should learn credit properly and credit for the team. I hope we can all learn邀功也要上

Don't abandon technology, it may be your life-saving medicine

After doing project management, especially as I am now a person with multiple projects in the case. Administrative work takes up a lot of time per day. This is what the job itself needs you to do, and it's understandable. What I want to say is, even so, make sure that you learn about technology.

Learn about new technologies, write open source projects, and keep learning about technology. He can always help you when you need it.

学如逆水行舟,不进则退, with everyone

Summarize

Overall, I think a novice project manager should learn the following things:
1. To learn to lead the team to grow, do not hands
2. To think more
3. To learn risk management
4. To keep your heart strong
5. Learn to Credit

Above, is what I want to share with you, many of the points, I do is not very good, still need to self-practice and efforts. I hope that all the students of technology management can adapt to their work as soon as possible.