Talking about the process management
I. Business Negotiation 1. The gesture of the author seems to be less related to business negotiations, many technicians believe that PM needs this matter, how to do a project, rather than will do a good job in the relationship between the four flat people. As PM has quietly raised in China, more and more PM began to participate in business negotiations under the boss of the boss, playing a single child with sales, which is really needed to figure out the psychology of customers. Try to figure out that customers need to have many knowledge, need depth and breadth, however, the most important thing is still a member. How to put down the shelf, reduce the posture of the author, is critical to the PM transformation from the technician. Reducing the posture of the author needs to be implemented from a number of aspects, most mainly to remember: people are unspeakable, and it is not possible to measure. In order to maintain the company's image, many companies will unify the staff to dress up, look like a white collar. However, the boss is mostly unconstrained. China's reform and opening up for 20 years, many rich ownership cultural levels are not high, often when college students will only sit on the bench, they are already rushing, accumulating the wealth of their parents. Rich business experience has a full understanding of money, life and society, forming a stable thinking framework. Many of these people are wearing old clothes, wearing broken watches, often bringing three characters, drilling into Shanghai people, can't do it as migrant workers. Because of the social status they live, no ornate appearance is required to settle your identity, and they are in the air. This is a very dangerous challenge for PM. Although the project will have a certain understanding of the personnel and key characters in the initial intention, there are too many people who can speak in the big project. Shanghai people are most fascinating that many people talk about the project, and the performance of migrant workers or a lot of vulgarity will not be frowned. It is often lost in the project when she frowned, which is lost in the market and money. PM must be talked with people with each level, especially if it seems to be lower than the group, even the aunt sweeping the floor. Only by making modest and cautious, do not put the shelf, respect others will receive respect for others, and have the opportunity to win the project. The nose will only strike their nose than people with high eyes. 2. The rich knowledge of the knowledge is not enough to win the project, accurately, to win the trust of the other's key characters. PM generally uses not to eat alcohol with customers, it is the sales of sales, but PM and customer discussions may be the most. When discussing the problem is the opportunity, how to vote, is a big key. Money and beauty are still routine knocking, but this fool knows how people will do. The relationship between the boss is only one aspect, and now the big boss, which does not matter? What is the PM better than others? When I made a single child, I found that the other party was not very interested in anything, and I can't find a breakthrough. The other party is very smooth, and the beauty of money is not lacking. He spent many days and other directions, and gradually got the trust of each other with his own enrollment. Later, he couldn't find that the other party's development history of mathematics and astronomy has been involved. The next day, he did not talk about the project, only talking to the other party, talking about Copernico, Bruno, Galileo, a whole day. The other party nodded, like a mud, attitude and enthusiasm came to a 180-degree turn, he got the list every other day. This is a classic war, who can think of Copernico will make money in advance? This PM relying on the sensation of the sensational feeling of learning and the keen feelings approved by Mo, let customers resonate.
Customers feel that he is also very high, and it has a common place, and the trust is greatly enhanced, and the project is given to him. Today, this example has been unrelenting in business negotiations. For PM, it is not required to be very proficient in all aspects. It is impossible thing. As long as PM has a probably understanding of some popular topics and astronomical geographical history, it can be as soon as possible Mastering, there is access to creating opportunities and grasping opportunities. 3. Powerful communication skills in the chest, there is no know how to express it, but not absolutely no. Everyone's life trajectory is different, and the impact of thinking is also different. Including some of the future MSEs we are currently in this class, there must be more introverted or don't love to express their views, which is more passive, often difficult to take the negotiation. From today, this kind of person must reach how to speak, how to debate loudly. Communication is not just loud, but found problems while expressing their own views and consolidated. In addition, the ability of communication is closely related to social experience, and is closely related to PM's knowledge. In daily life, PM should pay more attention to, think more. When others think of a level, it is deeper than others. Of course, there are also some friends who are not practical to communicate and brag as a complete thing. When I communicate with the customer, if there is something that is not marginal. This kind of person, I don't understand, less serious or curious, strong customers have a certain market; and level, responsible customers tend to feel that this kind of person is unreliable, generally will not give him a single child. PM needs to grasp this degree, and blow it is definitely blown. When you brag, you must have the foundation to blow, and you will easily express your familiar direction, choose your familiar direction. Play, properly leave one or two hands, give the other party's high-profile feelings, the best effect. 4. Excellent pre-sales team This team is generally initiated by the general manager and is usually not specified in PMP. It has put forward a relatively high demand for team members such as Sales, PM, SA, and ENGINEER. Generally, when the company will receive a single child to a certain extent, PM tend to discover the discovery agreement, some commitments to customers have almost can't do or have something to do. There are many cases, the sales task is to take the list, the sales I have heard is "no problem" or "no problem", but when I hear the customer's request and sales, I always It is a heartbeat, it is very unnatural. Sales are very hard, in order to establish customer relationships, especially blank markets is very difficult, often for a single child to sacrifice very much. In this case, and the sales of the sales will naturally fall to the head of the PM. Before sales and customers commit promises, PM should actively communicate with sales, provide rough overall design frameworks and technical difficulties, and the workload that can be considered, rather than waiting for the problem and sells each other in front of the boss. . When the team is formed, PM should be passed according to the quality and task of each person in the team. Excellent pre-sales teamwork is an important guarantee for orders. In the actual operation of business negotiations, there is a variety of problems, and PM's responsibilities and requirements are not more than the above points. According to the different circumstances of environment, policies, humanities, relationships, PM's different growth experiences, each PM will ultimately establish their own views and experiences of business negotiations. But there is a little bit of certain, this is the first custom of PM as a PM and the most important level. Picking the list, PM will lose its meaning.
Different from sales, PM's task in this stage In addition to orders, it is necessary to collect information on customer key characters and establish a good customer relationship with the person in charge of the other class to fully mobilize resources at the project implementation. II. Starting phase 1. Some basic concepts of projects have a variety of versions, and they are different. There are many scores, cost and progress in the actual operation, where the most important is the scope. We collect projects and submit to users' products and documents as submitting parts. When negotiating, it is necessary to establish the standards and requirements of the submitting part, that is, the scope. Although the unavoidable customers will continue to improve standards and requirements, they will not have a penny increase. However, this standard has a bottom line for each company. Once the bottom line is exceeded, the item is definitely a loss. Unless it is a profile for the second phase or in order to do a good relationship, it is willing to do it if it exceeds the bottom line, and it is impossible to do this in this case. Establishing a range of practical experience in PM, in a large and small project. At this time, it can reflect the difference between PM and technicians. The cost is the payment of customers, and our investment cost is not a matter. The progress is not described more. How is the project succeeded? There are also some key factors. Personal understandings are not the same, usually include the following aspects: defining work objectives and work tasks; support for bosses or high-rise; excellent PM and development team; adequate resources; good communication; for customers' positive response and appropriate Monitoring and feedback. Here you should pay attention to the support of resources and high-rise. A large-scale company always has a lot of projects, but the large-scale company resources are not enough to ensure that each project can form the most suitable development team or have the best environment. At this time, there is an inevitable resource competition between various teams or sectors, and it is inevitable. At this time, the PM's recordings once again challenged. In addition to the emphasis on the PM project, if PM usually gets along the company and colleagues, many people look very difficult to seek the problem. On the contrary, a PM that does not work will be due to poor margin, even if the high-level strong department or team cooperates, others will drag, delay the progress and quality of the project. Sometimes, this internal consumption is devastating to the project and PM. The positive response to the customer is also a key. Generally speaking, PM has been exhausted by a big and small thing in the project. To take the initiative to take the initiative to work with a very hard thing. However, this time, the more difficult, the more I feel tired, the more you want to take the initiative. Customers are often not particularly positive, active and customer contact communication and testing can find problems early. From the perspective of risk control, the sooner the problem, the smaller the risk, the smaller the loss. Active attitude can drive the enthusiasm of our customers. When the project is completed, the customer is often difficult to describe in language, which will be a good foundation for the second phase of the second phase. Because when you negotiate with other new customers, new customers will naturally find your old customers to understand the situation. At this time, the old customers will be very worried about the top ten sentences. There are several important features of business behavior, with consumer sources, participants, have a key factor in success, and have financial goals and risk. 2. The main task of the startup phase According to the interpretation of PMI, the project naturally forwards the startup phase after the order. The main task of the start-up phase PM is to lead the overall architect designer and system analyst to collect as detailed data, establish as detailed needs, further establish a detailed project range, estimate resources, establish other programs and get the next stage Approved. At this stage, with the deepening of demand analysis, PM has also begun to conduct personnel selection and resource competition in the company, and set up their own project team. The project is about to enter the planning phase.
After collecting the data, PM should begin to clarify important features such as the size, cost, specifications, and periodic conditions of the project and write it to the contract text, and prepare the internal data of the budget, measurement, and other documents, and establish an assessment criteria for the project. Next is a demand analysis. For professional reasons, we only discuss the demand analysis of software engineering projects (hereinafter referred to as demand analysis). The main participants in demand analysis have PM, overall architect designers, system analysts, and customers who are familiar with business processes. PM leadership team is not a real development team at this time, we are called the former team. With the gradual deep demand analysis, the new team members continue to join, the official team will be established when the startup phase ends. For a start-up project, demand analysis directly determines the success and failure of the project. The initial demand reflects in the customer's work instructions or bidding documents and accessories. This demand is generally relatively vague and cannot reflect the real needs of customers. The previous team should communicate with their own experience and customers and guide customers to enter the right track. Sometimes customers will do not talk about or rigid, and ask for some obvious mistakes in accordance with his thinking. At this time, team members should be patient and customer, talking about experience, reasoning, graphical or model, etc., such as common data flow charts, etc. So, the debate is inevitable, and the customer sometimes blows the beard to take the table and even say "this thing doesn't want you to do". PM In addition to participating in the needs of demand analysis, it is necessary to deal with the relationship between team members and customers, ensuring that the relationship will not deteriorate to the point where it cannot be cleaned. As long as the PM tries to constrain members in the team, this degree is still easy to control. For rapid development and superiors, demand and implementation are often synchronous, and the development speed is a great advantage. For small projects with the same or similar modes, it is a very cost-effective practice, and the popular limit programming is the thinking mode established in this regard. However, there are too many different demands and modules in large and medium-sized projects. If it is not because the project has a difference, there is only a product on the market without a project. Therefore, the demand for large and medium-sized projects should be carefully done. We want to discuss a problem, what should we spend on demand analysis and overall design? Our familiar waterfall development model is basically in demand analysis, overall design, software development, testing and other stages, however, how much time should be spent in the first two stages, but there is no conclusion. Examples of actual project operations show that the longer the analysis design, the more detailed the demand design, the shorter the test time, the lower the rework rate, the smaller the risk, the easier the cost is controlled. The demand analysis and overall design did not have a good problem in the project, and the issue of the project was unlikely to progress in the early stage of the project. The problem of some incubation periods in the post-project period and test phase but the problem of more destructive effects will highlight, causing Rework, extend the test time. Therefore, it is better to put the problem to demand analysis and overall design. The foundation is consolidated, and the pyramid is easy to make. Programmers working in Japan may all know that small Japan's software is very powerful, they spend more than 40% to 50%, far exceeding the implementation of domestic software projects, and effects It is also strong. Their overall design is even exhausted to a process how to judge, what kind of conditions are established, in other words, how to write (if ... else) statement helps programmer. Under such software specifications, the programmer is more like a worker on the assembly line, which has become a complete repetitive labor for a module or technique. Therefore, in Japan and Europe, there will often be a programmer in low-level work. Many people are unknown, and they are also unfair to domestic programmers. It is unfair to domestic programmers.
In China, only copying the code, don't understand innovation, everything rely on others, the programmer staring at the table is a lot of programs, which is generally difficult for this kind of person. However, there are many outcoming programmers. Since there is no software specification or very small in China, this kind of excellent programmers are many of the system analysts and even PM live, holding programmers' salary. Although such programmers eat a lot of losses when they start, and they have been losing to eat, but several years later will have a significant differentiation in the social status of the previous programmers. When the uploaded programmer is a business negotiation as a PM, the former is still frequently hop in various companies, and jumps to jump. Some pull it out, go back to our topic. Japan's software specification is amazingly similar to CMM, at least 35% of them are almost exactly the same. Recently, there is not a boom, and Tokyo has closed 160 software companies. This figure is in June this year and is still increasing. These companies have rushing to Shanghai and recruiting technicians. If you want to apply for such a company, you should consider it, you can learn their norms and quality control, but you want to become a system analyst or PM from programmers, Bundden is difficult. Often a programmer ink to do for several years, the piece of yourself is not very familiar, and what is done by the next colleague. Refused to China is trying to CMM4 (Huawei India Institute has passed CMM4), which is a blessing and difficulty for programmers working in Huawei. Of course, you have made PM or Qa or love Coding Friends exceptions. The demand analysis itself also has a problem with time allocation. The first time, demand analysis is the longest, and the analysts run almost the legs between the various departments of the customers, and the saliva is dry, which is to establish an initial demand model. All documents will be submitted to PM for review and sign, and unqualified reinforcement. Feedback table will be submitted to customers, the second pass, etc., etc. When the PM finally merges all documents and establishes the demand, the finally generated demand document will be submitted to the person in charge of the client's departments. These documents will be added as an attachment to the contract to change the importance of the project and the important basis for the customer. It should be noted that customers are not very unreasonable, but to tell the truth, there is a helpless, and most customers in China have changed their demand in order to not let their money white flowers. In the start-up phase, the demand is clear and signed, regardless of the end, a detailed written document can solve many of the issues of many oral promises or conceptual blurred documents. Detailed demand analysis has an additional advantage that some parties are very unfamiliar or unmanned areas will be a decision to decide whether to conduct a project. Sometimes, this big project does not absolutely seize the results in the signing, and once it is difficult to overcome the technical difficulties in the demand analysis phase, it will give up the project. A typical example is NMD Intercontinental Defense System. In the early 1980s, the United States engaged in the Star Wars Plan, dragging the Soviet Union. Everyone is somewhat vague of that history, many people think that the Soviet is in the United States. In fact, it is not completely, the Soviets' intelligence agency has no hole, not so easy to be deceived. In fact, the US Department of Defense has begun to start the demand analysis of NMD system software, and it costs billions of US rounds. It takes two years, only to do demand analysis, and finally found that there is a height that cannot be achieved at the time, then the project is give up. 3. The project launch project starts to determine the project plan, implement the first project audit with customers, confirm and order some of the products and services to the next package. At this time, PM suddenly found that there was an unfinished meeting, and three to four meetings on a day were normal.
These meetings have meetings with customers, with the following manufacturers, teams, and high-rise. The team's meeting is mainly to establish a formal team, providing the role and responsibilities of team members, providing performance management methods, providing members of the project and targets. One major meeting with customers will be the project launch meeting. At this meeting, PM will establish formal exchange channels with customers, and project participants understand each other, and establish a management system with PM as the core. There are also some zero straw things even including the size of the office space, how many phones, all contact information, etc., etc., and do the meeting records. This is some very trivial things, it is very necessary, it is very necessary. Probably the so-called three armies have not moved, and the grain is first. At this time, as the company's high-level, it should be applying to the company, officially released the project manager to appoint a book and project authorization. Although this action has some formalism in others, it has great help to improve the morale and responsibility of PM himself. 3. Planning phase 1. Define Structure Division Structure Diagram (WBS) The startup phase, the project enters the planning phase, which is also officially entered. The concept here may be a little less than the head. In fact, it is a reason for the translation. Anyway, everyone understands that it means that it does not need to be restored. WBS is a group of items to be submitted to organize the overall range of defining items, including project scope from work, resources, and cost; establish a hierarchical work structure required for a system; Several details of management, this concept is a bit blurred, in fact, in fact, the parties in the resource manager are one thing. It can be said that WBS is the core of the planning phase. The WBS will be detailed to the submitting part, including process files used by the items used to use, to give the client and description documents, complete each detail standard, and how to assign these detailed responsibilities to specific individuals. WBS has indent and tree shape, I have no way to draw here, and everyone refers to some project management books, there is a detailed introduction. My entire article only picks me what I need to pay attention to, if it is not necessary, use the technical details or tools. The details of the WBS do not need to be broken down to the same level. The lowermost detail is called work packs, the basis for subcontracting is personal responsibility and credibility, which means whether the task on each person can be implemented, is it a grasp? There is also the extent to which the project is controlled, the deeper degree, the deeper the WBS tree. Since WBS is something practical, it is different according to personal understanding, so a project may have several correct WBS, see PM needs and the best choice for current team status. The definition of WBS is still very troublesome. PM To convene a team to discuss, provide members with all the details related to the project, and decompose the WBS to the third floor. Then take a while to let the members think about brainning storm, formulate work production and corresponding person's responsibilities, and record the completion of each work package. When thinking in the brain storm, there will be a fierce argument, PM should coordinate relationships, adjust the atmosphere, push the side knock next to each angle you can take into account, prompting members' thinking angles and direction and summarizes. Although it is very troublesome, WBS is still very worthwhile. Like the needs analysis, the more the WBS is prepared, the faster the encoding progress. 2. Since risk management is business behavior, then the risks of the project must exist. It is believed that many friends who read this post have experienced or small risks. Some risks are easy to solve, some risks are greatly damaged. Whether there is any risk, avoid avoiding as much as possible, so it is necessary to manage the risk.
Due to the unpredictability of risk, risk management is very difficult, and the concept is also difficult to explain, and can only analyze from some feasible perspectives. First, you must identify risks. This is a very difficult problem. PM should first hold a risk identification meeting, which will participate in the company, high-level, cross-sectoral experienced people. Then review the risk list generated by the project team and communicate with important members, check some important risk sources such as WBS, cost (time) estimate, personnel plan, procurement management, etc. Finally, the PM itself is less learned in previous similar projects. Analysis after identification. We can conduct a rough quantization analysis (accurate analysis is impossible). Experienced people can participate in discussions together to classify the risks submitted. First, according to the possible divisions, generally divided into high, medium and low levels, although it is very boring, but there is also a quantization; then according to the cost of cost, it is also high, medium and low. We can combine the three levels of these two categories. It has also been possible to meet the risk of high cost. It is not acceptable. Has this risk has to let customers revise demand or increase risk reservation costs, otherwise it is not a little bit of loss, it is possible to pay very good. High and middle, neutralization is a high risk, medium and low, low and low match belong to low, high and low match. In response to the possibility of occurrence, some means need to be taken to reduce risks. There is no such thing as a definite way to say that there is a definite way to avoid it. There are several ways to consider that the first is to incorporate risk into the project management plan and designated the person in charge. The external personnel regularly check the project risk, once risk, execute the risk management plan; the second is insurance, this belongs to the risk The third way is a bit rape, but the most insurance is to drag the water, let them participate in risk management, huh, huh, it is good to talk :) After the risk management, PM needs to update the WBS, modify the schedule plan and Update the risk management plan. Risk reservation is usually 8% of the cost. 3. The estimated estimates are evaluated from the range of quantitative perspectives, mainly including workload, task, human, equipment, materials, costs, etc., pay attention to the prediction is not financial strategy or quote. The prediction is not a one-time job, and the estimate is always required during the entire project. It seems that there is no particular need to mention, and each PM will naturally be estimated, and it will be estimated when the project changes or enters the next stage. The estimated role is mainly made to make PM to have a bottom, and there is no need to arrange the plan. 4. The progress plan scheme is a module or function to write how long, PM arrange a date, set a milestone, and the programmer cannot be lazy. The progress plan is extracted from the WBS. For PM, reasonable scheduled schedules have a great role in project control and motivate team morale. For programmers, the progress plan is undoubtedly a nightmare. Display schedule generally has a presented sequence diagram, Gantt chart and milestone graph. Upper and Shao Wei
The teacher lecture, the recommended tool is M $ Project, I will not use this tool, because there is no time to explore. My head is very slippery. In the past one month, he used this Project to draw another milestone map, and kept tortured my nerves and colleagues. We generally have a Unit Test while developing, because there is a powerful time pressure, efficiency is much more efficient than before, but we can only set the progress of Baba. Due to the small people in Team, we are all alone. I went around at 6 o'clock every morning. After nearly two hours, I have been sitting on the seat at 8 o'clock, I have a 15-minute meal at noon, and I have been working at 8:00 pm. It is often 11 o'clock. I have never eaten breakfast for more than a month, and I have not slept too much or more. Although powerful stress allows us to master as many skills as possible in a short period of time, develop more modules, but there is a big impact on our emotions. Therefore, the project milestone is a double-edged sword, and reasonable arrangements can both promote efficiency and not to fight morale. The step-by-step fading of team members will bring difficult estimates to the development of the project, and the progress will be greatly delayed. About PM and team issues, we will talk about it, here I first swear, then skip. The landmark chart is characterized by tasks, members, and time, tasks, and messages with text logos. Time is described and assisted with graph line spans, and the ladder is as very image. It is very convenient to manage, and it is possible to finish the hook. Network logic diagrams are schematic diagrams representing tasks and logical relationships, which can be represented in a predetermined order or by critical paths. In fact, each activity is divided into 1, 2, 3, 4 and other stages, including small activities 1.1, 1.2, 2.2, 2.2, 2.3, 2.4, 3.1, 3.2, 3.3, 4.1, 4.2, etc., the schedule plan is also divided into four The species, generally only mentioned in front of the front and backwards. The past, the future concept is the latest time, the first time, the first time that must be the same or more than the active point to this activity. Some windows, we played more: 2 phase points to the 3th phase, then the 4 sub-stages in the 2 stage are also pointing 3. Suppose 2.1 end time is January
12th
, 2.2 end time is
January
22nd
, 2.3 end time is
January
15th
, 2.4 end time is
January
20th
So, the late 2nd time is 2.2
January
22nd
Therefore, the earliest start time of 3 sub-stages 3.1, 3.2, 3.3 in the 3 stage cannot be earlier than
January
22nd
. As for the backward example, everyone will go, I will not give it, just a few 123, I am exhausted :) The project often needs to adjust the progress. When do not change the scope of the project, there are several ways to adjust the progress: use fast tracking means to change the relationship between tasks; change the serial task to parallel; change the working method (possibly change WBS); change the date limit, The task on the critical path begins or ends earlier. Although the method is diversified, there is only one, it is the labor force of the desperate press programmer. How to press or have a skill. As in the previous analysis, the demand analysis hates must have multiple points to give it, the pressure demand is unlikely; the test phase is close to the completion, Luoli's thing is a lot, busy is busy, then PM is in advance / Completed on time, good collection, it seems that it doesn't like that time. To be brutal, the most compressible or coding, the coding phase is often compressed, in short, everyone is suffering, the programmer is compressed, the programmer is very normal, and the company is very normal. I believe many people There is a deep understanding, and you will not mention it here. Just, I summed it, let the future PM have the basis of the later people, huh, huh. At the time of the test, it can also be appropriately pressed appropriate, and when people just completed, they were more lazy. Domestic general enterprises are not large, there is no special quality control department, so quality assurance and testing are often programmers or PM itself. In fact, the number and quality of quality assurance and testers should be higher than programmers. In companies implemented in Japan and CMM, encoding compression is easy to implement, because those programmers are really skillful assembly workers, which are very convenient. What are the purpose of cultivating people like this, maybe it is compressed? ! IV. Control and implementation phase 1. Software development is really nothing to say, and everyone is the most unwilling to talk about it. Usually, it is enough to talk about it, and I have to suffer here. Need to remind the team's spirit and perfect document management system. SourceSafe These tools are sometimes necessary. I often see that some people say that the genius programmer does not write anything. I believe there is this genius programmer because I have encountered a few. There is also a love company. The core code of their product is this person, and the past has passed, and the surrounding code has been changed. The core algorithm has never changed, but this kid has followed Li Hong, now I missed it. But his code seems to be a bit noted, no comment for programs that will never guarantee that he is the most memorable. Moreover, it is impossible to play the world in the coding of a project. Others' companies are teamwork, and the two wisdom will win. This is still supporting the facade of a genius. In fact, the market can grab someone else, then there is no use. At the time of encoding, the technicians are disclosed, the programmer does not hide, it is good for everyone, PM must find ways to mobilize the enthusiasm of innovative thinking, create a good technical discussion atmosphere, and it is easy to attack when technically difficult. There is a question that requires a series of programmers who have not performed yet, in fact, it is time to use, what kind of development tools are used. Experienced programmers often take C or Java qualification certificates or have some experiences of one or two development tools. In fact, the boss and PM do not value this at all, what kind of tools they care are to achieve the goal as soon as possible. Take what C , Delphi, PB or Java, as long as you can do it, VFP can be used.
I will not say that I don't want to see the tool, but reminded the programmer who wants to transform into PM. The first should be treated as a tool, not by the tool set, and drilled some techniques that have not been used for a lifetime; second It is not a separate tool that is not a single tool, but the idea of popular programming, and the ability to master a strange tool in the shortest time. Only such thinking is only possible to turn into PM, otherwise it is a technical worker in a lifetime, and the most is a technical directory. 2. Change to any project, change is unavoidable, no evasion, can only be active, this should start from demand analysis. For a good project for a demand analysis, the more detailed and clear scope of the benchmark file, the less the user who is pulling the PM. The demand is not good, the scope of the baseline file is unclear, and the customer caught the empty thing is a very headache. It is often necessary to pay unnecessary sacrifice, sometimes even very fire. Demand is good, the document is clear and customer signatures, then the changes raised by the later customers beyond the scope of the contract, and additional charges are needed. At this time, I can't be soft. I don't want to deliberately earn customers 'money, but I can't develop the habits of customers' regular changes. Otherwise, after the end of life, the cost of maintenance will make PM can't eat. When the customer proposes a change request, you must establish a change request registration form and a change application form, and let the customer sign. Of course, sometimes some of the modules that are not very critical are not to talk about blisters. When they sell their faces, they still have to sell, especially when they lead their opponents, don't sell too simply. Don't let them get too easy. Demand is not good, the customer seizes the vulnerability or very unreasonable, and the trouble is big. Sometimes the argument will be very powerful, and the PM is almost communicated with the customer representative. PM is difficult to pay in both customer relationships and short-term benefits, usually compromise to customers, and eventually form a vicious circle. This situation is very difficult. In this case, this is a matter of the project, and it is almost impossible to do a major change. If you do it, you will lose money. At this time, if the PM is determined by the high-level people with the other party, it can be pressed through the other party. However, due to later, the customer representative will not be easily replaced, the other party has not changed, it must be dissatisfied, the next time I will still find trouble or talk to the second phase, I'm very moving the hands and feet, it is very good PM. Things to hurt their brains, this is no good solution, so doing things as much as possible as much as possible. Relative requirements, what WBS, risk management, plan progress is dilated, demand is done, smooth sailing. There is also a way to install pit, the favorite is very like, in front of the other party, and can't see the look, let you feel that you are really poor, then even if this time Customers are hard to change, and it will be impossible to call him again. In fact, people are hard, if possible, I still don't agree with some means, but sometimes customers are very difficult to move in a short time and will be close, in which case the PM is playing some means. Everyone has a man's way, Eight Immortals pass the sea, and all of them are god. PM needs to do in the change management, the analysis change request, evaluate the risk and modify the criterion file that may be caused. 3. Quality control large company has a quality management department (QA), and the members of QA are basically the old fox who is transiently transformed from very experienced PM, which is a powerful compete for the boss. A QA will manage multiple items, sometimes even participate in it. PM and QA have some pictures of cats and mice, which keeps some heart illuminated fake numbers through reports.
QA's work in PM is ultimately assessed: A level represents the overall control; the B-level represents the current control; Class C has a significant problem; D-class represents a major problem. If PM has a D, it is not very wonderful, not only the world-class QA will receive a report every month, and the area QA will come to talk about once a week, one meal. Getting a PM is very happy, basically no one will come. In companies with no QA, quality control can only be carried out by authorized team members, and the effect is too much. Quality Management runs through the entire project period, detailed see CMM. 4. Cost Management PM often controls costs by control progress and estimates. PM must often ask yourself, what stage is the project? How much is it? How much does it cost? What is the cost? The terminology of the earning value method, like BCWS, BCWP, ACWP, but the relationship is relatively simple, everyone should see the relevant information, this is no longer described here. In short, PM should manage costs, pay attention to save, but not to exploit the programmer, the flower is still to spend. V. End Phase 1. At the end of the project end project, PM will submit the final system scheme to the user, complete all the submission parts of the project, collect all the information of the project and end the project, complete or terminate the contract, sign the end of the project. The end of the project means that it can be charged. PM has worked so much, and I can finally be happy. I received the last payment, meaning the transfer of the submitting and the decentralization of the team. The project also transferred to the maintenance stage. However, the money does not necessarily represent the money, and we must see if the project is completed on time. In general, the project is rare in advance, but can make big money; earn a small money on time; the extension is to pay for money. One person will take the first PM for the first time. If there is no one, it will fail. Failure is nothing, all PM (note is all, not almost all) fail, but failure will become lesson and experience, and drive you to continue. In the United States, at least 40% of the projects have been stranded. Only in the project and life constantly hone, cultivate their own quality and the basic criterion of the author can become a PM that makes a lot of money. 2. At the end of the project completion meeting, it is still going to meet, but there are few more. Generally, it is necessary to open one, mainly to determine that all submission has been received, praise the outstanding individual, the external propaganda case, the logo, and the formal end of the project. At this time, it is very easy, the purpose is also clear, I have finished everyone, or have the opportunity to work together. The team is to dissolve, and the internal meeting must be open. Nothing is good, the praise is praised, how many bonuses have been sent, after all, everyone is exhausted and dried for so long. At the end of the project, please go out of the hot spring, PM, don't forget the programmers and engineers who have worked hard for you, of course, if they don't want to see your face, then you will be discounted to their passbook, just Let them go home to rest. This will only sell for you when the next project needs them. Say that the bonus will seem to be lost, in fact, you make big. 3. The customer satisfaction situation is good, history is also good, although the customer satisfaction PM is already in the heart of the project, but it is necessary to send a message to the customer's all levels of items, and the information recovered Will react customer satisfaction. In fact, there are many places that really reflect customer satisfaction.
The first is to pay the fast, if the customer is not satisfied, you are also difficult to 抠 in his teeth; the second is the second phase, the second phase is very important, because it is already a kind The project of sales costs, there is a first phase of experience, which can be said that the second phase is best earned. This feeling of this, only those who have experienced it. Six. Team Management 1. Establishing a team to select a big problem of PM headache, sometimes a very good person in other projects, excavation, may not be able to adapt. Therefore, PM still want to expand the knowledge, cultivate their own acuity, due to people, can pick a person who has helpful to the project can actually act on the project. 2. Core programmer has a core programmer. The core programmer has a very responsibility. It is time to work with ordinary programmers. It is more important to hit a major technology. Some people often complain that the programmer has high salary, I really want to ask these people to try the work of the programmer and see if they pay for the salary. As mentioned earlier, China's programmers differ from Japan and Europe, and many of them participate in systematic analysis and modeling, and this salary is really grievances for programmers working on the foot. Look at the programmers working hard in the industry, have a few do not have a white, high myopia, not old? On Friday night, I overtoc to 10:00, a technical director of next-door company specially left to tell me: "Our people, the first half of the birth will go to change money, and then the second half will take money to buy! So, must work Pay attention to work and rest! "I don't understand the truth, I don't want to override my body, but I have a choice? PM should pay special attention to the care of the core programmer, especially their life difficulties and mental conditions, sometimes, they are trying to compromise, they want to find reasons from themselves. In fact, I haven't encountered the programmer who dares to do this. Relative to PM, the programmer is an absolute vulnerable group, there is no say, almost what PM wants to do, how to change it, the programmer has to pay everything to achieve the goal. 3. Reward and punishment rewards are not to say, I believe all PMs that read my article, future PMs, programmers and future programmers know how to do it, here only punishment. Punishment seems to be very difficult, in fact, it is simple to PM. A programmer smashes the module,, buckle salary, and the expenses do not use it, it is not the responsibility before the project is not completed. An excellent PM should give him a chance. When it is nothing, let him do something else, give him to others to do it, is the biggest punishment for him. This can motivate him to go up and will not let him embarrass, he will be grateful for a lifetime, because you gave him a chance. PM picking out the person into the team and give him responsibility, he did not finish, PM itself is responsible, you should review it. 4. Management conflicts are inevitable regardless of the familiarity familiarity between members in the team. When the conflict occurs, PM should be kept in mind to handle conflicts in public, fair way, can't be done by one of them is their own little scorpion, do not have any side; do not do things when handling things. Sometimes there will be conflicts between members and PMs. Under normal circumstances, it is certainly a PM responsibility, because few members dare to eat leopard courage to resist their head boss. In addition to the self-review in time, PM must have a broad cardiagy. Never take advantage of the author to combat with yourself, otherwise all members of the team will be cold, the quality of the project will be greatly reduced.
