Recently, the project is basically on a pause state, so there is time to stop and summarize it.
Since the project has undergone replacement of the project manager, there are some own opinions on different management methods. Try to see project management from programmers.
First look at two questions: 1. Document a lot of programmers have the same idea, that is, it is very annoying writing documents (at least too many documents), but the project manager is most important, they will remind you throughout the day. Document, this is not right after getting the hand, it is not right, and it is blowing. The programmer hates this, but it can't show any dissatisfaction, and informant, it will naturally affect work.
2. Progress General project development will have a progress arrangement, with Project, use other things, but will be accurate to do any task to a certain period of time. The programmer works according to this, and the progress is backward. It will take a break in advance, look at the book, learn to learn. But the project management personnel ask you every day, sometimes even a few times: How is progress? Can you complete? At this time, the developer will extremely anticipate. "How to arrange it, I am clear, why is it like a reminder, I am not a slave, long working !!" But I can't speak, I can only feel in mind.
Why do this happen? Some project managers do demand, plan, estimate, etc. when the project is just beginning, busy, but with the design, coding work, their functions seem to be degraded, do not participate in design, Not to say, there is only a grades of the task, and only the documents and progress are left, and for real software, I don't ask. Don't understand the design, don't talk about the code, see if you look at the code specification, or some bugs on the interface. It doesn't care about design and how it is achieved. However, it is not possible for the document, and it is still in the format. They have thought that the project is still in its own control, and these developers are also very obsolete, they can show that he is also very busy, and made a lot of things. So I think that the root cause of this phenomenon is that project management believes that they are managed (not real participation), as long as there is documentation, there is a controllable progress, the project is in the mastery; more, they have The documentation and progress will never be able to make a true "Leisure Director", he knows the progress of others, but does not know his progress.
The solution is to be real involved in the development of the project, design, encoding, do not need a lot of energy, but it is enough to establish your prestige in the development, and you can discuss with them at someone else's problems. communicate with. You can see the nature of the problem during the review, not some fine branches. On the one hand, it has increased its role in the project. On the other hand, the development person can really become a team, eliminate the emotions, and the developer's relationship is "you" to "we", although the position and fundamental starting point still different But it can be understood and collaborate. More importantly, what is the most needed by the project? communicate with? Or is it a "standing meeting"? Instead, it is of course "command."
I have no intention to devaluate the role of project management in development, and more unintentionally degraded project management personnel, just publish a little idea if I have encountered it in the development of myself (by the way, I am complaining), I hope my Bother is not aware of those real outstanding project managers, and very hoped to see the views from project managers.
