The "three sides and six beats" of Project Management "!

"Three sides" refer to plans, implementation, and modifications. "Six beats" refer to shoot your head, shoot your shoulders, shoot your chest, shoot your desk, shoot your ass, and shoot your thigh! The "three sides and six beats" is very vivid and deeply thought-provoking!

The "three-way six-shot" is not original. I first heard it from my leaders. I think it is very interesting, very vivid, and very practical. Next we will introduce what is "Six beats" in project management and some of my experiences. Then we will introduce "three sides" and my experiences.

 

Author: Zhang chuanbo

Www.umlonline.org

 

First shot: shoot your head

When the customer leader and the software company leader are together, "Shoot his head" determines a project, so the project is about to begin, and your troubles are coming soon.
The main problem with "shoot your head" is that you don't have to figure out why you want to implement this project. If you don't consider the feasibility and final effect, you will be able to immediately launch the project.

My feelings:
As a project manager, you are often unable to intervene in the process of "shoot your head". I'm afraid it is unlikely that your leader will be able to shoot a bit better next time. What you can do is to clarify the background of the project and the motivation of your leaders and customer leaders for doing this project?
To succeed in a project, you must satisfy the ideas of both your leaders and customers. Of course, the ideas of both leaders may not be clear. This may make you passive, but it also gives you the opportunity to "control" These things. Although this project was originally scheduled by "shoot your head, however, you can fully communicate with the leaders of both parties in the future, and gradually clarify what is unclear in the leadership's head (of course, extremely difficult), so that the project has a chance to succeed.

Second shot: Shoulder pat

When leaders arrange project work for you, they often say something like this: how important this project is to the company, you are a very important person in the company, you cannot succeed in this project ...... pat you on the shoulder, that is, set your kindness and trust. Sometimes, you may even have dinner with the project team to express your gratitude and trust.

My thoughts:
We are not stupid in software development. I think these steps are disgusting. When you encounter such a situation, you must be hypocritical about the third shot, which is even more disgusting! But if I were a leader, how would I arrange my project work? Will it be the same effort to make these disgusting appearances?

Third shot: chest shot

Some friends may think that the leaders really attach great importance to you, and "shoot your chest" without hesitation is guaranteed to be okay!
Some friends are smart. He knows that this project cannot be put off (unless you want to leave), but he also knows that the task is arduous and he will be shooting his chest, if you want to increase manpower and extend the construction period, you will often get some compromises from the boss.
I am a stupid one. I will directly tell the leaders about some major problems of this project. After I have learned about some projects, I may even say that this project cannot be successful. When I do this, I often make leaders unhappy, feel that I am not obedient, and think that I have no confidence in this project.

My thoughts:
It is really difficult to be a person. I am not a casual person. I can list the specific problems of the project and explain that I have been seriously thinking about it. If there is a problem, I naturally have to work hard. If there is no problem, the problem is actually even bigger, I don't know what leaders think? It's really painful to pat your chest!

Fourth shot: Pat the table

The progress of the project is not satisfactory. The leaders beat the table and swear!
The leader can beat the table and give you a sense of deterrence, so that you can work harder.
Some leaders are also very powerful and will hold back their anger. He knows that you can only rely on you now, and "Clean Up" you only after the project is finished!

My thoughts:
Using the factory model to manage software projects is actually a silly practice. Software Projects are full of creativity. Boring and high pressure often make the project team not to think about how to make it simpler and work less, but to get tired and rework. While the boss sees you working hard to work overtime, although the job is not successful, at least the boss will be comfortable. How boring and strange this is!
If you have a strong leader, hold down your anger for the moment and continue to treat you with courtesy ". Someone will take the opportunity to ask for a raise. It is okay to ask for a raise of 90% at this time. But wait until the project is opened, and it may be terrible.

Fifth shot: Shoot ass

I am not a slave society, and I am not selling it to you for life. If I don't fight for the East, I can beat the West. You can throw me. Why can't I! Let's leave Lao Tzu. You need to take care of your project!

My thoughts:
Regardless of the east or west, the family is actually a ghost. You just jumped from one fire pit to another. Do not pat your ass easily. Think about whether you are worth staying! If everything is not perfect, it is even more difficult for you to go out to work. From the perspective of your career planning, is it worthwhile for you to continue to work for this project? Of course, remember that a person must have basic professional ethics. If he is insensitive, I will not be unjust!

Sixth shot: thigh shot

The project manager was moved away, and no one managed the project.

My thoughts:
So early on, why? However, many leaders repeatedly repeat "Six beats". It is really hard for them to be leaders!

"Three sides" mean planning, implementation, and modification.

Many projects often rush to get started without comprehensive planning, and there are too many unclear factors due to tight project schedules. under high pressure, the project team often takes a step by step while making modifications. The final project effect will not be very good, not only the project team is suffering, but also the customer's interests will be hurt. The final result is "double-win!

In fact, many projects may not be able to escape the "three sides" Fate, because when a project is launched, the demand is uncertain, and the technology is often uncertain, but the construction period is limited, the project's budget may also be restricted. Under the framework of "two limits and two uncertainties", it is difficult to avoid "three sides. Almost none of the projects I have done can obtain comprehensive and accurate requirements from the very beginning, nor can I develop long-term and perimeter plans at the initial stage of the project, minor version iterations are my usual practice. In fact, agility has the "three sides" feature. Instead of "One step at a time", agility has a long-term strategic plan, and gradually approaches our goal through small versions, you can also predict changes while maintaining your flexibility.

So my thoughts on "Three sides" are: "three sides" does not mean a low level. The key is whether you are agile "three sides" or passive "three sides "?

 

Author: Zhang chuanbo
Www.umlonline.org/school/