"Technical background, how to do a good job as a project manager" series of "Management itch after programmers Upgrade Project Managers"

"Technical background, how to do a good job as a project manager" series of "Management itch after programmers Upgrade Project Managers"

In China, many programmers who have worked for several years and are recognized by colleagues and friends in the circle as good technical skills may consider their career development as follows: "I can become a project manager, and it is not very difficult to be a project manager ".
But if you really have a chance to bring a team, even a small team of only a few people, you will find that you must face a series of problems and troubles, the processing results of these events are basically irrelevant to the individual's technical level.
For example:
"I am overwhelmed by the pressure from the leaders every day. I am so busy that I have to vomit blood, but some of my colleagues feel that they are idle ".
"The tasks assigned to them seem to be too simple to be completed. It is a simple task ".
"It is easy to divide the work into several modules, but nothing is wrong after integration. There are always errors and I have to modify them myself ".
"The customer gave the customer a test version for demonstration. The customer's first sentence is: this is not what we want ".
"The deadline for product delivery is approaching, but software problems are endless, with hundreds of errors. How can this satisfy the customer and sign the acceptance? ".
"Working overtime every day makes people suffer from physiological clock disorders, turning people around the clock day and night. People who work on this project complain, all day angry, threatening to resign and strike ".

In the running of specific software projects, these headaches are constantly going on, and people are often overwhelmed and upset, so it is useless to keep your technical skills High. As the saying goes: "You are an iron, you can grind a few
Dingtalk ". The result of the big package is that you are exhausted and your work is not done well. As software becomes more and more complex and the demand changes, it is impossible for individuals to be hero and fight independently.
Home.

You can think of it with great pains: I must use software engineering methods and development processes to manage my team. But you really need to use the most famous CMM in your team. Even more frustrating things are coming soon.
Surface: in CMM, the light is a pile of nouns and documents, which can be understood for a long time. Moreover, these standards and guidelines are more like scoring manuals and are not operable. The project team seems to be busy all day and always have a meeting.
Annoying, but the real software is always stuck.
There are also many other project management methods and guidelines, which are difficult to operate and apply in the actual environment.
You must find the development process and framework suitable for your company's team. It must be complete and have good operability, flexibility, and a wide range of adaptation. Therefore, it is a very effective way to learn from mature and perfect companies in software project management, which allows you to quickly master various methods and skills in project management, and rose to the theoretical level.
In the software industry, Microsoft has a large number of software products and complete product lines. The success of this software giant in various markets is also obvious to all. The development and management processes of its software projects have always been the focus of interest to everyone.
I had the honor to attend a software project management training, which was delivered by a lecturer from Microsoft's China consulting department for three days. A lot of long-standing questions and questions have been answered.

The course content is MSF-microsoftsolutionsframework, a Microsoft solution framework. The so-called MSF is a set of software project management defined by Microsoft.
Complete process and method. Handouts are translated from English textbooks. The MSF version is 3.0. You may find it strange that there are still versions of this framework. Well, that's right. Microsoft's lecturer claims that
When Visual Studio. net2005 is released, it will integrate and bring msf4.0 together.
Because MSF itself is constantly adjusted and evolved based on new ideas, new ideas, and new practical project experiences in the software industry environment, and is not a dogma. For example, in the process model of version 3.0, there is a process called the deployment phase more than version 2.0.

MSF is a global product group, Consulting Service Department, Information Technology Department, and Microsoft partner of Microsoft. It analyzes and summarizes the correct experience tested in practice and compares the methods in the industry, summary, is
Guide to "people and processes. It is characterized by strong warehouse and complete guidance for the entire project process. Moreover, it is a general system. No matter what technology or project you use, you can refer to it.
.
MSF mainly includes two sets of models and three standards. The model exactly covers "people and processes": Team model and process model. Three guidelines: project management guidelines, risk management guidelines, and readiness management guidelines.

It was interesting when the lecturer talked about the team model. Five of us joined the group and conducted an impressive experiment. This is also the unique feature of this course. The lecturer does not follow the instructions of this course, but in
During the learning process, we have interspersed with multiple experiments and specific project instances, allowing everyone to understand the meaning of the theory in a temporary organization team and deepen their understanding.

This experiment is not complex. It imitates the most common structure of Project Groups in daily work. A group contains a "boss", a project manager, and multiple team members. Issued by "boss"
So that the project manager can direct the execution of his team and then view the results. Wait for 15 minutes. The "boss" reveals "Results" and the team members should make public comments. It's hard to imagine.
However, the organizational structure has so many defects!
The boss said: I thought everyone knew something that they didn't know, didn't know, and the information was completely asymmetrical.
Project Manager: Too tired to understand what the lead really wants.
Team members: they are bored and don't know what to do. I have no enthusiasm for my work and are not proactive.
The result is that the personal abilities of leaders and project managers determine the possibility of project success.
Then we began to analyze why and where the cause was, and introduced the MSF team model.
Of course, this experiment model has simplified a lot to highlight the problem, but in the actual environment, these defects actually exist.
The team model of MSF is divided into six roles: program management, development, testing, release management, user experience, and product management. Each role is equal, and there is no administrative difference between the upper and lower levels.
These roles do not have to correspond to people. When you do not have enough people, some roles can overlap and be assumed by one person. However, developers do not recommend assuming roles as roles, this is because it is necessary to keep Development closed.
When your team is large and large
A large team is divided into small teams, and then the core team is the master. It can be divided into functional teams by software functions and features, or by functions. For example, a program management role can be held by multiple people. This fully reflects the flexible and pragmatic aspect of MSF, which is highly adaptable. It can be used for small teams of several people or for large teams.
The adaptability of Agile Software Development Theory is weaker. It is widely recognized that agile software development is not suitable for teams with more than 10 members, and has higher requirements for members.

In another model-process model, the agile side of MSF is revealed again. By dividing complex projects into multiple versions for iterative development, the project difficulty is fully simplified. Each version has its own
The function scope can be viewed as a "small project". If the project is small, the complexity and difficulty will naturally decrease. Of course, the probability of success will be much higher. In addition, people related to the project can quickly evaluate the project results and decide
Determine the "next version" direction of the project.

Each project process contains a complete stage, including project conception, project plan, project development, project stability, and project deployment. From project conception to project deployment, there are many so-called links
Cheng Bei "achievements. That is, there are clear requirements for each stage and what results should be produced. These results require the joint efforts of team members to achieve, just in combination with the team model.

At any stage of the project, every team member must be successful and everyone should work in parallel. In this way, many disadvantages of traditional organization methods are avoided, such as the development is not over and testing is difficult. In this case
In the model, there is no longer a boss giving orders. The following people go to passive execution and have evolved into active participation. Everyone has something to do. Different roles in different project phases
Do not play a leading role.
There is also an important MSF principle throughout the course, which is risk. The so-called risk, simply put, is that the event may occur, but it is not sure when and where.

One of the first tasks that the team started to do was to manage risks. We simulated them in class through grouping, which is very interesting. Based on the lab requirements, everyone has a hard time thinking about the project.
Determine the possibility and consequence of the event. Even if a team member is pregnant and cannot continue working, the problem is also found. In dramatic ways, a trainee acknowledges that his team has encountered such a problem, and
I still don't know what to do.
The purpose of risk management is to take the initiative and quickly handle risks, so as to ensure the smooth operation of the project. In this way, the customer will have more confidence in us, trust us more, and the possibility of project success will be further improved.
The course is followed by a specific project execution process, such as the formulation, development, stability, and deployment of a project plan. There are many wonderful ideas and guidelines that allow you to follow suit.
This is my experience and summary After MSF training. Both theory and practice are intertwined. Without theory, there will be no rules and no stamina to do things. Without practice, the theory becomes very empty and empty. You must constantly apply the theory to project management practices to continue to grow and mature.