From the outstanding IT project manager to the distance of the millionaire, only 1M - How to make a good project manager

xiaoxiao2021-03-05  21

From the outstanding IT project manager to the distance of the millionaire, only 1M - How to make a good project manager

Author: Tuenhai.com MSN: king # tuenhai.com

Copyright Notice: You can reprint anything, please sure to indicate the original source and author information and this statement by hyperlink. Http://www.tuenhai.com/

Keywords: project manager training, project manager position responsibilities, project manager exam, project manager department, project manager papers, first-level project manager, project manager qualification certificate, project manager post responsibility system, how to make a good project manager, project manager's functions , The responsibility of the project manager, how to do project managers, project manager cases, project managers, senior project managers, software project managers, project managers success cases, project managers assessment methods, what is project manager, IT project manager, excellent project manager , Project manager's post report, project manager system, list of project managers, organizational form, project manager responsibility system, how to do a project manager, project manager's case manual, project manager, IBM project manager, project manager management, qualified Project manager, project management manager responsibilities, SAP project manager, international project manager, project manager qualification standard title: You are an excellent IT project manager, you are not a millionaire, why? Not you are not excellent enough, but you don't realize that you can be a millionaire. How to play a very important role in the IT project manager in IT, IT project manager. TUENHAI has been thinking, if it is me, how to be a good IT project manager? I. Is the IT project manager need very professional IT knowledge? IT project manager needs a professional IT knowledge? It is an discussion post on ITPub. "I am from hardware engineers to departmental supervisors. For project management, I think IT industry project management is different from other industries. He needs more comprehensive IT background knowledge. A project manager for ERP project, he can't complete a financial middle The business project development. At the same time, the host technology, network technology, database technology, and even backup technologies and disaster relief technologies, etc., whether the project manager needs to be responsible for him for so many professional skills. The technology contained in the project has a probably understanding. For the managers of the IT department, I think the light has a rich management knowledge and experience, you must have a very authoritative person in the professional technology, you want to let The team members trust you, not light is a problem, personal charm, a very important one for the technology, is technically let him obey you (most of China's intellectuals have such a problem, parallel You can't lead within it). "(Mingsir, http://www.itpub.net/90577 ,1.html)" I personally feel that the project manager does not necessarily understand technology, because his main job is the management of the project. At present, the domestic project manager must understand the technology is actually forced. There will be one or two technologies in many project teams. They often have the most difficult stabble, they think they are technically large. Take, the general project manager is not easy to manage them. "(Lonelywolf" I agree with the "loneliness master" upstairs, technology is essential for a project manager, and this so-called technology has been different from what we look The general technician or the technique of professional people (here is called "pure technology" here). The former should be a sublimation of pure technology, it is intrinsic, so from a real project manager How we see is mostly non-technical skills. In fact, non-technical skills are based on the establishment of professional technology after sublimation. "(Parasitic)" technology is essential for a project manager, and project managers should There is a wide range of knowledge, what is the advantages and disadvantages of the technique for projects, can you decide what technology is used, and when you give up a technology and use a more suitable technology.

"(Gzllm)" What do you think is a project manager? Managers' ability, coordination skills ... System analysts, frame designers, developers, testers, etc., they are all specific responsibilities and tasks, but these people should do the entire assessment and progress of the project. Decided? It is recommended that you can ruling yourself? If the project manager does and the technical associated decisions are much longer than the number of other people's recommended time, will there be some problems? It is not to understand all the knowledge but in macro, you must grasp the spirit of the team and Cooperation is good but fully believes that others have no big agreement? Why is it necessary to emphasize management, system ... I think the basic premise of management and rules is to build who believe in people on the team in the basis of not full trusting people? Who dares to guarantee that there is no one who has left full trust in the middle. You can guarantee that others will not hide some things or make private interests for themselves? "(Biti_Rainy)" I think the domestic project manager is often serving the project manager and system architecture The duties of the division, and some will also start the programmer. Therefore, it is necessary to determine the project manager to master the expertise in IT. Many IT colleagues around me have attached great importance to technology. This kind of emphasis on technology has formed a person who admires the technology. Project managers who have mastered professional skills will be supported. If a project manager does not have this ability, it is often questioned by programmers: "Why do you arrange this? Why do you design?", "Unreasonable, this is not right", etc. Project management will be out of control. Sometimes, in order to take care of the programmer, etc.. Project managers surely divide a project into several blocks, each piece to a person to design, program, write a document. Although it is unreasonable, what is the way? ? "(Skyweave)" One chat, a friend tells me that a successful project manager must have one of the following characters: 1. Technical authority: technical No.1 2, money bag authority: can determine the project member Income distribution 3, administrative authority: There is a position difference between the upper and lower levels 4, leadership authority: personal charm 5, bureaucratic authority: Familiar with the company "(zhongfei)" ZHONGFEI "I think many specific project implementations in the real project do not match domestic IT companies The flow rate of the technician is very large. The project manager does not have a very special place and only knows management. Who will take you, the project is dried to half, the technical personnel leave, and the project is a lot loss. I have seen it from myself, and the better project manager has: 1, if you don't understand the technology, even yourself chat, you don't understand what they mean, unless you can control the salary of the subordinates and give the subordinate salary. Otherwise, no one can listen to you (even if there is a technical manager) 2, the project manager can not be universal technology, but for the process of development, the progress of the project, and some conceptual knowledge must know, if it is integrated If the project, the project manager must be very proficient in the relevant business. This is the technical manager can't help you. At this time, there are some conceptual technologies to add a very strong business knowledge. At this time, your subordinates will definitely take you. 4. In addition to the above, it is also a good project manager to "get" customers, otherwise it is difficult to succeed.

This is what I saw in the system integration project. Anyway: I don't understand the technology, I don't understand the business, I have to laugh, you have to laugh, I can't get the money, I will have a very bad, I can't take you. "Getting" customer, the project manager is hard to do for a long time PS: I have never seen a project manager only relying on "management" to bring a project, the department manager only understands "management" and controls the salary of the subordinates. "(Shenxiangyang tumenhai) summed up: 1. IT project manager is best technical. 2. The technical expertise IT project manager has a lot of benefits in China, especially small and medium-sized research and development projects, IT project managers in a technical master There are many benefits, these benefits, the above friends are discussed in detail, I will no longer repeat. IT. Is it necessary to pay attention to project documents? In fact, if the project manager does not attach importance to project documents, it is not A qualified IT project manager. Therefore, we have to discuss whether it is not an important issue in the project document, but how to do document management in accordance with the software specification. The reason why this small title is because there are many in reality. The so-called IT project manager of scary salaries is not well known to the importance of the project document, so it is not a qualified project manager. "The documentation is undoubtedly more important than the code; but China advocates personal heroes, many people Will hope that others can know that their code is excellent, and I don't know why it is so good, this is to conflict with the purpose of writing documents, so there will be no too many people agree that the document is important than code. I think the document can let the programmer let the programmer better grasp the project, and sum up the experience after the project is completed; and if a person coding will make him feel difficult, it will only be a project, so I will not be a code, so I Think that the document is more important than the code! "(Bitter hard http://www.shecn.com/best/g7/g449.htm)" Let the project supervisor's most painful thing is: When an important member leaves the project group halfway, he found that he did not Leave any documents available. There is no banquet in the world, and members of the project team are also in dynamic adjustments, and the document is an important tool for handover between members. Many supervisors are easy to fall into the "heavy technology implementation, light document" misunderstandings. They always think that the project implementation time is urgent. In order to save time, you can write a document in the project collection phase. If the project cycle is slightly longer, the end, will members still remember the details of each implementation? Projects with no documents are ferrous as a failure project. From the perspective of process control, the implementation of quality control of the project is the most important thing to manage the management of documents. By documentation shows that each baseline, the workload of each member and the quality of the completion are minimized. "(" IT project management has "Tianqi" can be followed? "Wu Hai Jing http://www.ccw.com.cn/htm/Work/zl/xiaocao/02_7_30_2_2.asp) If Tuenhai is in professional technology, Tuenhai has Confidence has become one of the industry's best project manager. One of the reasons is that TUENHAI will never know the importance of project documents. "Document is mainly divided into internal documents and external documents.

Internal documentation includes: project development plan; demand analysis; architecture design description; detailed design instructions; component index; component components; component index; component interface and call instructions; class index; class properties and method description ; Test report; test statistics report; quality supervision report; source code; document classification version index; software installation package file. External documents mainly include: software installation manual; software operating manual; online help; system performance index report; system operation index. "(" Effective Software Quality Management "Zuro Hong http://www.iteer.net/modules/doc/article.php?storyid=383) If Tuenhai is the project manager, it will do this: 1. I will attach importance to project documents Because the project document is the main way to communicate with the boss. Project document is the main communication method of my with the boss. It is not good to communicate with the boss, or the work boss I do is not understood, my "project manager" will do it. 2. I will attach great importance to the project documentation because the project document is an important way to communicate with the subordinates. It is not good to communicate with the subordinates. The project quality is difficult to guarantee that the project failed. Even if the boss does not withdraw me, I have a face to continue the project. Manager? 3. I want to make each member of the project group (including me) to a certain extent by paying attention to the project documentation, so that the company's risk is minimized. This can be fully Show my "loyalty". Although this is also the requirements of software standards, but also to many BOSS, "loyalty" is always the first. "Loyalty" is to make the company think about the company, maximize the company. Pass Maximize the company's interests to maximize their own interests, is the smartest practice. At the same time, I will take other ways to establish my credibility and brand in the industry. The personal brand is established, it is in an invincible place. Of course , I can also make the project process completely under my personal control. Sometimes this strategy is very useful. However, in the first company, there is some people in the upper floor of the company. I am always looking at it - I don't pay attention to the project manager of the document is not a qualified project manager. Dear readers, if you are an IT project manager, Tuenhai is very hoping to get your advice. (MSN: king # tumenhai.com, URL : Tumenhai.com) II. Tuenhai, IT project manager who pays attention to communication, has written an article in the traditional industry - "a letter given to the little boss - the good communication of the chairman is For the premise of work, this article can now also search. Tuenhai not only attaches great importance to people (BOSS, subordinate) communication, but also pays attention to communication with people who don't know (such as through the online article), it can be seen that Tuenhai has always been The emphasis on communication. For the IT project manager, the most important way to communicate with the boss is the project document. If you don't pay attention to the communication with the boss, I advise you to go home early. IT project manager is an executor, execute The company's decision (or the intent of the boss). To do the executive, there are two steps: 1. Understand the company's decision (or the intention of the boss) 2. Let the boss know that you understand his intentions, and vigorously carried out.

In response to the first, to understand the intent of the boss, when developing R & D plans and demand documents, let the boss participate in and interact. This is the premise of all work in the future. For the second article, you must use the document form and the boss to fully communicate. The boss may not have time to see your project documentation, or don't understand, but this is not what you have to consider. What you have to consider is that when you care about it, you can call out the project document at any time, not to ask you. The boss is advisable to ask you, but there is a problem with you three times. As we all know, China's BOSS likes to be smart. The boss may hire your project manager through some way, and how to say how to believe in you, or all right, etc. He said that there is nothing wrong. If you don't make the boss know that your boss is absolutely "Bible" choice, it is your fault. Perhaps you want, the product is coming out, it is the best proof. I didn't say anything before this. The project documentation also went to the code to complete. Then you are too true, you are doing the software standards, can you guarantee that everyone can be caught in the drum, maybe, you don't wait for your product, you will "step". You will think that I have been strictly trained, and the product development is complete according to the software development specification. Just I will communicate with the boss after the product is completed. Then you are wrong, the purpose of the project document is to reduce product risks, for project manager, there is technical risks and communication risks. Maybe you are a strong technical person, can solve the technical risk, but because you don't pay attention to communication, let the boss feel that you have a big risk, you have taken a relatively large communication risk. From the process, communication should be before technology. Doing technology, self-conscious IT project manager often understands the importance of communication, performance is: 1. Surrounded by writing documents. This bug has been done by me, I am too lazy to write a resolution process. I solved the bug for 1 hour, and spent half an hour to write a document is not a waste of time. I am not so stupid! (Write documentation "seems to be" like "benefits, but it is useful to the company, you are gone, you can't walk less! It is necessary to get a necessary condition for the company to promote the company) 2. Project documentation , But not to the boss: His rookie how to understand the stuff written by my master, give him a white, hehe! (Do not say that the boss does not necessarily understand, even if he completely can't understand, he can't let the people who can understand, see if you are in this master!) If you are a project manager, you Project document values? Do you think is a good IT project manager? Welcome to TUENHAI Communication (Tuenhai.com). The idealized life of the Excellent IT Project Manager is how to do an excellent IT project manager. Next, we will relax, discuss the life goals of the excellent IT project manager. Coding and management may be what you like, but it is not your life goals. Everyone's life goals will be different, here TUENHAI is just talking.

I. If the salary income is ideal, don't use the "11" road in the street, or take the bus, or taxi? When traveling, you can buy high-grade cosmetics as a gift without going to study the low-end brands. It is best to have cheap, quality and good quality, no side effects (how possible, huh,!) Occasionally go to high-end entertainment venues One, not every time, "so good", "passing by his door," is not a great life! II. Work is challenging, growing faster in professional skills. If you don't enter, you will be more important than paying for personal growth. Continuous progress means a certain extent, the continued growth of salary. Third. It is good to communicate well with the company to ensure a pleasant work. The company is very smart, very large, communication has no gap, will make your own mood, and make your own to get the maximum extent. There are thousands of miles to have Bole. If you are a thousand miles, Ning can temporarily pay a little low, and we must also recognize that you are a thousand msma. From the outstanding IT project manager to the distance of the millionaire, only 1M is an excellent IT project manager. You are a technica, you have a year of IT project management experience, but you are not a millionaire, not a millionaire, why? You are an excellent IT project manager, you are impeccable in professional quality, but have you bought a car, is you buying a house in the big city, have you thought about holding a grand wedding with GF? You are an excellent IT project manager, although the salary is good, is you a millionaire or a millionaire? Any excellent IT project manager may become a millionaire within 3 years. TUENHAI is never nonsense. (You can see the article on tumenhai.com, Tuenhai is transparent online) from the outstanding IT project manager to the 10 millionaire's distance only 1m. What you have to do is, it is actually very little, nor is it so difficult: First, you are an excellent IT project manager, this is a premise. Second, you have to find a good startup in a prospect. This company may only be 500W now, and may be 500 million after three years. You have to find and join this company in a start-up period, and maximize your expertise, you also get the biggest exercise and improvement in this at the same time. Third, it is also a very important point, the company BOSS is very good. (Very open, very large, etc.) Ensure that the rights are also maximized while you make great contributions in the company. The main form of this equity is the company's shares. (It may be an option form) Because you are entrepreneurial, in your income, the proportion of salary will be negligible. Three years later, you will find that the cattle who is stronger than your professional skills is really strong, but the cow technology is really strong, but because the opportunity to enter the company is not as good as you, the cattle gets the salary, or salary. And you, you can go to "Swordsman", "Tour World", as long as you like, you can do anything you want to do. TUENHAI is lazy, technology is general, and management is also general. One day tumenhai suddenly turned, and I realized two elements of success: 1. It is very hard. (TUENHAI learning network related knowledge 10 hours a day) 2. Fully demonstrate the knowledge and skills you have in order to create an opportunity to get a business partner.

转载请注明原文地址:https://www.9cbs.com/read-36819.html

New Post(0)