Leadership – The Terminal Solving and Emphasizing the Obstacles
How to solve and eliminate the obstacles faced by the team?
Former Huawei’s senior software engineer,
Now IT industry project manager
Has a year of IT industry project management experience
· Foreword ·
After years of work, I have done a lot of different projects in different companies. These companies include tens of thousands of people, such as Huawei, including small private enterprises having 10 people, and work in government institutions . In these different enterprises, they all form some experience of project management, and they still have a success, so they still have more confident.
However, with time, I gradually found a problem, that is, I always feel that my project management knowledge is not very systematic. Every time I have a project management knowledge, I will only pass only, and I have not brought it to the face. And deeper levels, therefore actively conducted PMP learning.
The following is that after I study PMP in the system, combined with the original actual work, some summary and sentiments sublimated, I hope to give some small help to the needs of the friends.
·Background of the project·
Background of the Project
I have encountered a project when I work in a IVD company, and I received leadership arrangements.Responsible for research and development of a fully automated chemical instrument. The instrument is mainly measuring liver function, renal, blood sugar, blood lipids. The instrument needs to operate 7 * 24 to meet the actual requirements.
During the research and development, the product engineering sample has been developed, but during the trial operation, it is found that it will stop in operation for 1 hour. This issue will naturally have a big impact on the product, and the company’s leaders are also very concerned.
So the organization of the Organization of R & D team initiated a meeting, including colleagues in various major colleagues such as machinery, hardware, software, and crafts. The result after discussion is:
The machine’s colleague said: "There is no problem with the structural parts I design";
Hardware colleagues said: "There is no problem in my board";
Software colleagues said: "We checked the code, no such problem";
The colleague of the process said: "There is no problem in the assembly process."
After discussing a circle,Discover all parties deniny their own problems. Since everyone has no problem, then the instrument "see ghost", you will not run. The entire project is turned in a pause.
In this case, I use past experience and introduce it.First question responsibility system. Since I am a software technology, I finally delivered to the customer must be a software that can be run, so the person in charge first confirmed is a software team.
The software team is the first responsible person. If the software team can prove that the problem is not a software problem, it is suspected to be hardware, mechanical or process, and then contact the hardware, machinery or process team, further problem positioning.
Although I introduced the first question responsibility system, I actually act as the ultimate leader, or with the software team to participate in all positioning activities. In this process, I use my software expert’s ability and gradually discover a lot of software, and Solved one by one.
Among them, there is a more interesting solution to the problem: the same problem may come from a number of different reasons, and be sure to find one solution.
For example, this operation is 1 hour, it is 2 ~ 3, and after 1, it is found that the problem of running 1 hour will still exist, or may run 2 hours. So don’t doubt, the previous problem may have been solved, and now there is a new reason, you can continue to solve it, don’t take yourself in, and clarify your own ideas.
Finally, after a hard software problem, it is found that the instrument still has 2 hours of downtime, and sometimes it will be down for 1 hour, and there may be a deadlock.
At this time, it is necessary to make reasonable conjecture, is it possible to be a hardware FPGA problem, I will need to use it.Communication skillsNS. I immediately found the engineers of hardware FPGA, of course, you are welcome, because the previous hardware has already firmed "hardware no problem", if only doubts, let them solve the problem, I am afraid, I can’t accept it, this is the test.Project managerThe time!
I found that the engineer of hardware FPGA was: "Brothers, can help support this issue, the software brothers have no idea", hardware FPGA engineers have heard that they are helpless, naturally willful. If you say: "Brothers, you may have problems" So the communication soft skill here is also very important.
When finding a hardware FPGA engineer to help position the problem,As a coordinator, guiding software and hardware colleagues work together towards a big solution direction.Note: The software and hardware colleagues usually focus on their own technology, very much attention to overall solutions. Therefore, under my guidance, look at the software code and process, while licking the FPGA code, ultimately, our hardware FPGA’s colleagues, found that there is a problem with an interrupted trigger time in his code, follow his own There is no problem with the design, but once and the software, there will be an error when running together!
Finally, after the hardware FPGA’s colleague modifies the code, this bug finally solved! As a leader of the project, I finally loose!
When I solve this problem, I didn’t learn PMP, but as the old will succeed in the Sand, I solved the problem with my feelings and experience. But why can I solve this problem?
After learning PMP, there was a matter, just as described above, that is, my solution, now summarizing it:
Meeting -> (First Question Responsibility System) Team Articles -> Expert Judgment -> Communication Equity -> Guidance Conference.
Through these 5 steps, I think you can also become a helping team to solve the challenge!