Reader's letter (1)-the project manager. Do not be superstitious about the system!

 

[Reader's letter]

I am a developer of XX who is working in the C # direction. I have learned a lot about cnblogs. We are a start-up company, and it is difficult to step by step. There are not many people, but they have high requirements for everyone. After all, it is impossible to keep a bunch of programmers for backup to save costs. Currently, I am working as a project manager, Project Manager + programmer.

I always think that our project management is unscientific and unreasonable. For a project, I used documents to build a development framework, assign tasks, and schedule, then let's take a look at how everyone is doing.

I think this project management mode is unreasonable. Can you ask about the project management methods of some large enterprises. In addition, we are all document-only. Task allocation is document.

 

----------- Welcome to visit Lao Sun's Weibo http://t.sina.com.cn/laosunisme for interactive exchange -----------

 

[Answer]

First of all, I would like to emphasize that as a project manager, do not trust the system too much. This is especially true for small entrepreneurial companies.

To be honest, for small enterprises, the project management systems and methods of large enterprises are not suitable because they do not have the corresponding conditions. In this case, let's take a look at "coming out of the software Workshop".

It is not recommended that you become a project manager in a small business, if you want to develop something. Because only when the time is ripe can the standardized management mode play a positive effect.

So when is a standardized management mode suitable? -- Measure the following items:

1. Is the company on track?

2. Is the company's business stable?

3. How is the personnel quality and stability?

4. Is the company's technical direction clear?

Obviously, it takes some time to explore and try. The company is not formal, its business is not formal, its personnel is not formal, and its technology is not formal. How can we normalize it? More importantly, these issues are not a concern of the project manager. If the project manager does not instruct the project manager to standardize the system, it is easy to fail to implement the system specifications of large companies, failure is your responsibility. We must clarify these 1.1 issues.

Maybe you will ask: "Is there a simple way to judge whether the standardization of the system is promoted ?"

In my opinion, check if you have any trusted technical assistants. If you do not have a technical assistant, you should not consider any management. Cultivating a trusted technical deputy is the top priority.

Of course, if the existing project management is not scientific or unreasonable, appropriate measures should be taken to solve the problem. At this time, do not try to make a package plan. The success that can be seen step by step is suitable for your current situation. We recommend that you list all the problems and start from the best solution and the most effective solution. That is better than anything else.

All in all, the project manager must be down-to-earth and not superstitious about the system!