"Flexible Management" in "Software Engineering"

It should be noted that I am not a project manager yet. Or it is not a formal project manager. My project management experience is entirely out of my hobbies and concerns for this industry. I do not guarantee that my point of view has a theoretical basis, but this is a summary of my experience over the past few years. Do not read this article if you are an outstanding player. Thank you!

---------------------------------------------------------------

Cause

In fact, I am stupid, so I did not write the article at will. There must be a reason to write an article. The same is true for writing this article. This post original in csdn: http://community.csdn.net/Expert/TopicView1.asp? Id = 3541151

For qingrun, friends who often go to the csdn soft work edition must have heard of it. It can be said that in theory or practice, it is definitely on top of me. But recently, softwares are not as calm as they used to be. Due to such a rule, they have attracted the attention of many people. (I don't know how many people will come to softwares to pay attention to them ?). I have read the version rules proposed by qingrun and his article "Newbie, Newbie, you don't have to be crazy!", Many of his experiences are profound and absolutely supported. <== Please note that although this article is caused by this, it does not target anyone or anything. Stop here.

However, I suddenly thought of the word "Flexible Management" after reading the severe softwarehouse version rules and the overly strict replies from some netizens ". As a result, I wrote my feelings about flexible management (note that it is just a feeling, not a theoretical thing ).

Let's first look at the term "Taylor Management". I don't want to explain this word too much. It is just a thing-based management model. Equate people in an enterprise with other resources in the enterprise. All rules and regulations are used as restrictions. The first industrial revolution, or several years later, laid the foundation of industrial civilization.

One day in the last century, such a profession and a person suddenly appeared. They have their own culture and philosophy. They face machines with no feelings and perform operations that others seem boring and abstract. But they put their feelings into it, and they make their work full of life. They believe in people-oriented thinking ". It also involves doing what you like, such as sleep or working in the middle of the night.

"Flexible Management" was not initially proposed in software enterprises, but I can't find any other industry that is more suitable for using this management method than the software industry. Programmers are creative, planning, rational, and emotional in their work. In such an interesting job, no one wants to make their work as boring and boring as the beans in midnight (not including Japanese counterparts here, and domestic colleagues working for the Japanese ). Almost all successful software project managers believe that too many constraints will reduce the productivity of programmers (not as I said, let's take a look at the management art mentioned in some foreign software engineering books. At the same time, I also have some experience: A company's system is not appetizing, resulting in low morale and reduced productivity ). Many successful project managers prefer to manage programmers in a user-friendly way, such as allowing them to eat chocolate, drink cola, wear casual clothes or wear cool sunglasses during work hours. At the same time, they will give their team a loud name, such as the full moon or Firefox, or any name you can think of or think. Even when you enter their space, you will also be asked to enter the password: lunch box, lunch box, lunch box. Generally, programmers will come up with various names to relax and make their work interesting. Team Managers also need to adapt to such subordinates and use human words to manage their work. When you place various rules on such a group of interesting people, they are required to strictly execute them like accurate machines ............

(Play games with colleagues and try again later ~)

(After playing the game, after dinner, continue to write ~)

When you set various rules for such a group of interesting people, when you require them to be as strict as accurate machines, your first mistake has already started (a disaster begins when you make the first mistake ). You do not allow them to talk during work hours, prohibit them from moving around at work hours, or require them to "Work hard" 8 hours a day in a suit in front of a computer. Everyone is treated as a part of an enterprise's machine, and the entire system looks like an orderly process ...... Are we still in 18xx years? Or 19xx years? While you use the standard "Taylor Management Model" to manage teams organized by programmers, their creativity and enthusiasm are also erased. You can no longer see the excitement, excitement, or inspiration in their eyes. Finally, some people get tired of leaving the "strict" team one day. One, two, three ...... At last, the entire team is only available for you to formulate strict rules and regulations and strictly enforce them. It seems that management becomes less important for a team.

Writing a program is not a simple task. It is not just a casual chewing gum that can be done by listening to music. Programmers are self-disciplined, but this does not mean that they can accept any restrictions you impose on them. "Flexible Management" plays an excellent role in giving full play to the self-discipline of programmers. You don't need to use a whip or a stick to hold your responsibilities behind them. When you find that their work is away from the normal direction, kindly remind: "Hey, dude, this does not seem a good omen. Why don't you try ......" It may be more effective.

The more I write, the more I run my questions. "Flexible Management" is something I want to know. Do you have any new ideas in the future.

--------------------------------------------------------------------

Don't scold me, don't ask me concepts. For the reply, I only want to see your thoughts or ideas on flexible management. That's all!