Random essay: Some of the experience with the project and the qualified Leader should have what characteristics?

In addition to the first-class software enterprise, a large part of the software project Leader (refer to the project manager, technical manager, architect, etc.) is not qualified.

Note : This is just a matter of writing people, not discussing the methodology of project management .

Many projects have these kinds of Leader:

1. Generality type

Most of the time Leader just give a general direction, to mention some of the theoretical direction of strategically advantageous position, the matter is still referred to ordinary developers to do. The end may be back to complain about the level of development staff not to meet his expectations. The final software products knock on the side of the launch, not to the expected, the responsibility of the developers head, Leader and strategically advantageous position sacrificed a gorgeous reconstruction program or two-phase program.

2. Pure Technical Type

There are a lot of such Leader, maybe from the inside of the team, or from outside, they have a common feature, love "play" technology. Such Leader may be equipped with too much "engineer temperament", may be in the management, personnel, project progress, customer relations and other issues are inconsistent or not good, believe in large Internet companies free working atmosphere, advocating "good" technology. I met a team of 20 people Leader, the company has a great expectations of the product, to use the go language to do.

3. Pure Management Type

There are also many teams of Leader, non-technical backgrounds, but purely managerial personnel. Many of them have no problems with their management skills, but for software projects, they often keep the team busy. Because the number of people in a software project is difficult to measure accurately, technical difficulty (productivity) is difficult for managers to grasp, resulting in the inability to grasp the project in full , the technical risk of the project, time risk can not be effectively controlled.

Ideally, the Leader should have at least the following qualities:

1. Technical strength, but do not love playing technology.

I believe this is enough to Pass out 90% people, contradiction? No contradiction, technical strength, just enough to assume the Leader of software projects to control the overall situation, this is no doubt. But he must have clear goals and bigger picture and know exactly what he is doing, because doing the technology and doing the project is two things entirely. To do the project do not play technology, to play the technology please go to research institutions. There are many Leader in the new project, love to use their own not understand the emerging technology, only to add a pen in their own resume, but the risk of the serious lack of understanding, and even the final effect and the ideal is far from the difference.

2. Ability to reduce complexity rather than increase complexity.

This is an extension of the last point, as a Leader, whether it is to do products or projects, technology is not a goal, technology is just the process of achieving the goal, the process, the more reliable, the easier it means the lower the cost, the less risk. Strong Leader, can be complex target needs, high decomposition, the complex development of technology, cobwebs, lead the development team step by step, steady forward.

From the perspective of the enterprise to do the product, the technology itself does not "cool" and "backward" of the points, many people on the technology two years ago, the emerging concept of the flock, such people, individuals think can only be transferred to "software development enthusiasts" to go. Proven technology means reliability, low learning costs, a proven approach, and the most important: low risk.

In terms of coding, there are many Leader respected some of the good writing, the design method, the general 10 lines of code to complete the work, reduced to 2 lines, greatly appreciated, if it is a personal project, their own happy, but for teamwork, business projects, it is not advisable. All the goals should be: increase productivity and reduce complexity. 20 years ago, the strong coding method was to save the storage cost, the operation cost, but now, the storage cost and the running cost compared with the manpower cost, already basically insignificant. It takes more than half an hour for someone to understand the cost of the code, which is much more than the storage cost of the few bytes you save, and does not include the loss of an inexperienced developer who understands the error.

3. Have a certain dedication, willing to lead you to grow

Do software project Leader is to have a great dedication, because the traditional industry also has a teacher so say, a day for division, life for the father, but in IT industry, have not seen The Apprentice this said, open a joke.

Leader to have a consciousness, painstakingly cultivate and educate the development team, help them grow, but know how to appreciate you, know hello person, not too much. But still have to do this thing, try to help the team to grow, because the more important goal is to put the project to do the product. There are a lot of methods, such as we have tried to organize the book friends, when looking for the "code Daquan" this book, two times a week, take turns, also organized PPT learning, open review and other ways, have achieved better results.

4. Strong control and control

I think a person who has no control is embarrassed and has control to talk about control. As a software project Leader, facing the complex external environment, internal environment, the test of control ability is great.

The risks of the external environment may include higher expectations of the enterprise or the customer, challenging time nodes, uncertain target requirements, and must have the ability to resolve the Leader.

The risk of the internal environment comes mainly from people, such as vacancy, the uneven level of the team.

Once I took a basic team composed of beginners, customers want the software products to achieve high design indicators, and has a strict requirements for the duration, at this time, control and control to play a fundamental role, the software is highly modular, the core functions of all by my own design, Organization team to the meeting room to watch the projector to teach them to write plug-ins, find a representative function to implement, the implementation of the method, coding style to make mandatory requirements, let them copy, ask them to achieve code style highly unified. All the details of the UI section are highly mandatory, specifically a UI DEMO, which describes the layout methods, spacing, margins, etc. of the elements on the UI. Several times a week outside of the project, at least two code Review, taking into account the actual level of team members, beginning I will be in Review help them rewrite, a line of scrutiny, tell them how to analyze, how to design, how to write, several times later, overtime must be rewritten. After a period of running-in, we gradually entered the state, forming a strong cohesion and combat effectiveness.

5. Treat people with sincerity

Although put to the 5th, but this is the most important point, this can not be done, all of these are dead letter.

As a team Leader, must be honest with the team members, can help everyone's intentions to help, for oneself is not particularly good at the problem, can not care about him, the team members of the crackdown, this is also a lot of people do not. In addition, the team members of the work situation, life situation, must have basic understanding, family life pressure is larger, whether family needs to take care of, live is far near, the company gives the treatment is low, must have a steelyard in the heart. As for how to do it, I think for an adult, there is no need to say much.

6. Other basic literacy, no longer repeat.

This essay thought where to write where, some messy, mistakes are not all the more inevitable, welcome criticism.

Small ads

Bloggers are paying attention to the relevant senior positions in Nanjing

Biography:http://121.40.198.87:8010/

Random essay: Some of the experience with the project and the qualified Leader should have what characteristics?