Software development, human management
- Book review "deadline"
Windy.j
I remember to have a period of time, I am fascinated by ufo, mysterious civilization, four-dimensional space, etc., walk on the road, there is no time around, I will always worry: I will not care about the four-dimensional space, and then many The strange thing, when I came out, dozens of years have passed, everyone doesn't know me?
Although this is not happening again, it will also have forgotten, but when I see the "deadline", I can't help but have a beautiful eye: I am unemployed. Kidnapping, get an incredible work, go to a picturesque world, where will happen what kind of story, oh, think about it is shunt ...
How to manage the software development team, obviously the core of this book wants to elaborate, in the novel, Totopkins has an unique insights: Choose the right person, assign the correct job to them, maintain their enthusiasm Help team condense and keep their cohesiveness. Here, the most important thing is people, and teams, rather than those "literacy" in many long boring management courses: Gantt chart, Porter, status report, communication specification, conference plan, time card, progress tracking record , Project milestones report, quality management procedures ... that is not management, management is human.
Choosing the right person, then the person is important, Totopkins began to pick his project manager and managers, what kind of people are suitable for project managers? It is those who respect the team, pay attention to the team, and pay attention to the team members. A candidate creates the best working environment for his team, a candidate highly praised his team and maintains the integrity of the team, a candidate adopts a half anonymous mechanism Listening to the subordinates, Marco said to maintain the enthusiasm of the subordinates; and that one thought that he was a team's soul, members were the "Batton General Worshi" in the infantry, and he was in the recruitment.
The project manager is a person, team member is a person, protecting your team, don't let them suffer from external harm, this is an important part of management, and Tuprkins encountered people like Berolock, he doesn't understand software development. I don't understand the progress of the project, and I don't care about the project team. He will only say how much the cost I spend on your body, so you have to work overtime, release the date of the product, you have to submit a project report, you have to do Process improvement. This is a command, not management. Under such stress, Totkkins still insist on protecting his team, hiding them to buildings, guarantees a good working environment, does not have to follow the process of the dead plate, isolation pressure. Through the "Qianxian" email, he answered our question:
n Why can only increase 6% of the pressure on programmers?
People under N pressure cannot think more quickly.
We can't forget, the programmer is also a person. When we encounter a variety of problems in the past projects, customers' demand changes frequently, from leaders, customers, sales staff to end the pressure of the project as soon as possible, use a strong way Increase the human hand, plan latency, long-term growth, long maintenance process, and even long-term business trips in the field, leave the family, this time, there is no sense of accomplishment and exhaustion to make the best programmers lose enthusiasm. What is going to mention here is that there is a project period to be too long. Every Monday is going to be a foreign land. In that time, I even got a "Sunday insomnia (fear) symptom", oh, poor procedure Do you have similar experiences? Good management will also mediate conflicts within the team: "Difficulties in negotiations, mediation", "Remember, we are all standing on the same side;" Remember, we are all opposed to our problem ". Also, when the team or member encounters difficulties, the manager needs to relieve their hardships. "The team's Osman can't stand it!" "When I told him that when you don't have to do a manager, you should really see him. The face. At that moment, he was like a young man ... ", liberated them from the unrelated meeting:" I think they will open this will be meaningless ... So, I let them leave three "
In the days of Morovia, there is another vivid and true little story, Totuskins has been busy solving the problem for his team, summarizing him in software development management in the daily diary. Get experience, although his A team failed, but B and C team completed the "impossible task", can't say, this is a very optimistic attitude, but is it more important to visit more The team in the project, people in the project will be closed for success? If there is no way, there is no tool to be a "silver bomb" to solve the problem of software engineering, is the key is the person in the project implementation? Slightly a bit unfortunately, there is no specific details of the team in the book, for example, where they are sitting, the process of work, or some of the programmers have completed the work, he will sing songs happy, did not see these . Of course, there is a more detailed introduction to these details and specific operations.
There are still many other valuable perspectives, such as functional points, metrics, and intuitive modeling, etc., when I lay in bed, after I finished reading, I can't say it, this is really a refreshing Experience.
When I came out from the four-dimensional space of Morovia, if you ask me, what is the management in the software development, I will tell you, understand them, love them, and love you, care about them, help them; When you want to implement a measure, think about it, this measure is more convenient for yourself, or can help your team solve the problem and improve efficiency.
Because the team is your strength, "they will only follow you because they love you."
