Talk about the project management stuff.

In our development team, every person with a project has become a good employee.
It is no coincidence that leading others will understand how to be led, saying that "employees who have not been bosses are not good employees." Five years ago, when I heard this sentence, I didn't understand it, until I did the project leader and realized it.

Today I want to talk about my own management project after some experience. The overall score was a few chunks.

Personnel Management:

The biggest problem for people is three:
The first place to put your own arrangements before the collective arrangements
from 1.0 to 3.0 development time is relatively long, do the project is a bit annoying, the task of the morning will not arouse the interest of everyone to develop, these work and do not do for themselves, everyone more hope to learn through the way of video, naturally lax development. Each system leader is also busy with this piece of business, Seldom go to each member of the group. Everyone is like a knot point, not connected. Overall, the sense of the project is not strong. We do not know the real learning and experience is actually from the project.

No.2 Lack of confidence
Some people feel that their progress is slow, always want to concentrate on the video to improve their level. This is a psychological snag, and will continue for a long time, the confidence is not enough at the same time with other people in the development process to understand the issue of the problem is not understood the key, really can not let go. For this situation, I feel like 3.1, to a quick version, so that more people first look at the pig run, and then eat pork, perhaps a good way.

No.3 communication is not smooth.
Communication between people should be friendly and concise, and people should be responsible for what they say. But in fact, we are always very difficult to put a positive attitude, will be mixed with personal emotions, often blame others, the anger is big, on the good temper of people angry. Oh!
I asked the Golden Court very seriously, why do I have a bad attitude when he will listen to not contradict me?
He said, he stood in my perspective, I said the right, he improved, there is nothing to contend with.
Most of the time I looked at him, I think, how the technology is not important, a person's state of the general people are really not compared to him!

Another kind of communication is about the project itself, some things do not know how to do the oral account, such as the first to do external interface or internal business or parallel development, to have a plan to implement in sequence, more communication should be implemented to the document, to ensure that we have "documents" can be followed, "documents" must be based on "documents" must

The purpose of communication is to progress together, we must share the progress, we always have the technology is not, always want to learn from others, they understand also want to take the time to speak to others, is to eliminate the awareness of small farmers. Zhou rang has been doing very well.

Time Management:

The biggest problem with the use of time is the lack of control to work overtime.
During the development of the 1.0-2.0 system, almost every Thursday was overtime during the day. I can not assess the efficiency of the time, because in the early stage, to study and learn a lot of things, functional development is not completely imperfect is understandable.

3.0 when the overtime was added, the people who had been in the class were strongly against it. 3.0 during the development period, because of the exhibition and follow-up things so that the whole class is almost lost the enthusiasm of development. To Baoding to graduate students only slightly improved, Baoding 10 days back, development and fell into the trough. Then there was a flurry of research, some hoping Some people slowly withdraw from the development of the circle.

3.1 have to say overtime to go crazy, high efficiency? I recommend valuing life and working overtime, regardless of height.
If the project plan can be arranged properly, where is the need to work overtime. Even if the arrangements are complete and complete, the extension is justified.

Project plan:

The plan was badly disrupted.
The plan is for the change, it is normal to appear biased. But there is the front of the director of the guidance, if we can be more modest, clever, borrow someone else's head hit badly beaten to grow their experience. Listen to suggestions, reduce some suggestions to the situation that do not know how to choose.

Task management:

The project leader should be forward-looking. scheduling tasks is purposeful.
There are always some things that do not work hard, this is because the project leader is not forward-looking, so every important decision to have planning and approval, any more than half a day of the job must be seriously treated, because the company costs are not allowed to reinvent.

Interface Management:

Each system proposed interface to have a unified format, to clarify what their own interface, according to what to check what, return what, return what type, to use professional language to describe clearly, the most direct is to write a method that has not been implemented, plus the comment description is what business. Like UML diagrams, with these you can avoid the words , the key lies in the description is unclear. The implementation is countless verbal dealings, delays in development time.

When invoking the interface of the system developers, found that the basic interface to provide a problem, the problem includes the data can not be detected, there is a return value but not to be timely and the relevant responsible person to contact, and a check in the end, if not transferred directly using false data to continue their own development, Then we'll block out the way to discover the various possibilities of this interface. We have such a phenomenon, the interface module is a responsible, this interface is a B development, using the interface is C, when C found that the interface has a problem can be to the head of the system D reflect, by D and interface to provide the person responsible for e-contact. Such a process without good management to form a loop, will cause the interface to become the result of a dead interface. AB feel that the interface is not a problem, C feel the interface has a problem, de does not know. So the fake data is always used. In order not to delay the progress of developer C, it should be handled by two persons in charge.

Code Management:

The biggest problem with code is the lack of maintenance of public code, each of whom has a problem, and does not want to tidy up the public part.

2.0 at the bottom of the package of the public JS, is common.jsp, pagetools.jsp and searchbox.jsp. This encapsulates some common methods and styles, which are fixed to call some methods or use some fixed names, such as the DataGrid is called Queryarea. Each system references these pages to be eligible for these names. And then only the basic system implemented this public style, is the so-called Baidu box. To 3.1 when everyone wrote the page, use this style to not fall, It will affect the style of the other pages. The result is that the page styles developed by each developer are no longer uniform, time-consuming and laborious to change their code, and that the public-introduced code cannot be reused without improvement.

If time is tight, preserving the original style is one of the reasons. These problems can be solved in the optimization, there is no collective perspective to consider, this is a problem.

A good development team atmosphere should be positive, the project leader to lead everyone together with the same spirit of cooperation, angel-like beautiful mood.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

Talk about the project management stuff.