If I have my own development team ...
Everyone may have heard of the project manager, in my consciousness, as long as it is simple project management training, it is called the project manager by the emperor. Some even have not trained, maybe just manage one or several items that may not be a project. Therefore, I have always thought that the project manager may nothing. A project does not need such a role.
However, when I read Tom. Di Mi's "deadline", I think we need a such project manager, my company, the project is very chaotic from the beginning, no charter, not because We did not work in accordance with the ISO9000 software management system (this system is a garbage), but our project manager has failed to handle the most important issue in the book: people's problems! After removing the management of people, the project management only has a boring document management. Perhaps any simple training can handle these documents, but there are no few people to handle the problems in the project. Most of our project managers have ignored the most important issues in this project management. Because they don't reasonably handle the problems in the project, they may be too small to deliver success on time.
If I have my own development team, I am a project manager (now just imagination, I am also a system designer). Now I have a very tight project, then, I will ...
First, the real project manager must have such a capability: 1. You can choose the right person. 2, assign them the correct job. 3, keep their enthusiasm. 4. Help team condense and keep the team's cohesiveness. Look, all of them are related to people, remove these, others are working.
For me, I want to choose the right person is a difficult thing. Maybe I still don't have a possible ability to see Dong a stranger. So I will choose a colleague who work with me, maybe we have been in a group. So I know them very well, I believe I can assign them the right job. Also, I want to keep my team together, keep their enthusiasm, don't threaten them, don't give them too much pressure, don't work overtime. My own experience tells me that pleasant mood can make their productivity improved, far more effective than the pressure of them.
However, this does not mean that we will waste time and time is the biggest damage to the project. "There are countless ways to waste a day, but there is no way to take a day." One point, there is no time, you will never make back. Therefore, from the first day of the project, we have to arrange our work. Reasonable allocation time, even if the time is not reasonably assigned.
In the beginning of the project, we don't need too many people, and the super-edited person will only bring us more trouble, more people, more time will be wasted, everyone has their own thoughts. It is very difficult to combine them to combine them, and if there is only a few people in the design phase, then these people will work very tacit. They can make this design very beautiful. It may also be completed in advance.
However, this also has problems. If only a few people participate in the design, the person added to the post-encoding, test, and document will not know about this project. In order to train them, we will waste a lot of time, maybe we have time to save time. It is better to waste more than one tenth. In order to avoid this, we need to do a very detailed document. This detailed document is not our usual design. I believe that the detailed design is useless to us, at least I have written the program. What I said is referring to the interface of the module, data structure, and module in the sub-file. Here, the interface between the modules is very important, we usually have a big project. Part is in the interface definition, and the implementation in the module is very rare, if there is a lot of implementation in your module, you can only explain a little, you are an unmanned programmer. So, in our detailed documentation, the interface between the modules is defined very well, then we can save a lot of time during the test. We can eliminate our usual calls. Because as long as the programmer is doing strictly in detail, then as long as our design is fine, it will not be wrong. Now there is an important issue, in order to ensure the success of the interface design, we must carefully consider the problem of the interface, very careful. It's as if you are already encoding, you have taken all the questions that can be considered. I think you can consider how much I have considered interface issues in the design, causing many problems that will be implicated until the coding will be discovered, and there are many modules and people that will implicate. So carefully design the module interface to ensure that he has no problem, our project is coming. After the design is over, the programmers who come in after the rena member can start coding very quickly. Don't think too much, just do it in detail, and ensure that there is no problem inside your module.
If everything is done, I think our project is successful. However, until now, we may not do it, there are many reasons. Customer reasons: They are required to deliver too much. Leaders will ask the group to overtime, keep working overtime, in their view, this is the only way to increase productivity. However, such a project is rarely successful, the team's members will be tired, and finally leave, the company will recruit new people, to train. It was tired, leaving, and then recruited. An endless death cycle, and finally the project was completely smashed. If the customer's requirements can reasonably, the leaders don't put pressure, let me arrange everything, I think maybe I will give them a surprise. But now this is a luxury .......
