On the project management

 One. Business negotiations
1. Zuoren attitude
Zuoren not seem to have relationships with business negotiations, a lot of technical skill is needed is that PM is how to do a project, not be a good relationship get the well-organized person. With the rise of PM quietly in China, more and more CEOs PM behest started in business negotiation, and sales hit list together, this comparison is to try to figure out the needs of their customers PM psychology. try to figure out the psychological needs of our customers have a wide range of knowledge, depth and breadth of need, however, is still the most important Zuoren. how to lend a lower to a human gesture, the transformation from the PM and technical personnel who, it is to crucial.
reduced to a human posture needs to implement in many ways, the most important to remember: in vain, but can not measure the position. many companies in order to maintain the company's image, will be called the employees to dress nice uniform that looks like a white-collar look. However, the boss probably is not constrained. China's reform and opening up just two decades, many wealthy industrialist boss cultural level is not high, is often only when students have to sit his ass profligate parents on the bench hard accumulate wealth, they have to run around everywhere, and accumulated a wealth of business experience and money, life and society have a full understanding of the nature and form his own stable frame of mind. These people, many are dressed in old clothes and old, wearing a broken broken watches, talking all the time always bring along Three Character Classic, into the heap in Shanghai, they might you take him for a migrant workers. because to they are in social status, has been without any set off the dress to their identity, they are plenty of clout. to the PM, this is a very dangerous challenge. Although the initial intention when the project would be the other key personnel and certain understanding, however, in large projects on the words can say so many people. despised Shanghai is the most rustic, a lot of people talk about the project's time to see the performance of workers or very tacky inevitably frowned, often frown lost when the project is out of the market and money. PM must be done with people who talk to each level, in particular seems to be lower than their population level, even if it is sweeping the company's aunt. only for to be modest, unassuming, respect for others, will be respected by others, a chance to win the project. nose higher than the eyes of people who will only hit his nose flat.
2. a wealth of knowledge
light is not enough to win the respect for others projects, to be exact is the key to win the trust of each other. PM with clients generally do not need to eat and drink, it is selling their things, but the PM and the customer may be the most discussed issues. discussion it is the opportunity to match up, is a key factor. money and beauty is still the conventional stepping stone, but the way this fool know that everyone will do it. boss is only one aspect of the relationship, and now the big boss, which not? PM Why go to the same conditions one better than others?
I have a friend (PM) make a list, and found little interest in anything the other side, costs can not find a lot of energy to a breakthrough. the other side of this man very well, no shortage of money and the status of everything beautiful. He spent many days and talk to each other, gradually made their own learned each other's trust. Then he thought he found each other on the history of mathematics and astronomy there are covered by a treasured home to spend a night time search for information on the network. The next thing he did not talk about the project, only with each other talk of Copernicus, Bruno, Galileo, these people life, a full blown day. Daosuan mud as the other nodded, attitude and enthusiasm to a hundred and eighty degree turn, the next day he got the list. This is a classic wars, who will help advance thought Copernicus IT people making money? is learned by the PM and extended out from the knowledgeable and keen sense to seize the opportunity for customers to resonate. customer feels he has a very high level, but also, and they have in common, trust greatly enhanced to the project to reassure him. Now this example is not uncommon in a business negotiation. to the PM, it does not require very proficient in all aspects, it is impossible, as long as the PM for some popular topics and all aspects of astronomy, geography, history, knowledge has a rough idea, the time needed to master as soon as possible, have the opportunity to create opportunities and seize the opportunities.
3. strong communication skills
the chest but do not know how to have plenty of ink expression is relatively rare, but not absolutely not. each person's life trajectory is different, thinking affected by the environment vary. including, as we are in this class are some of the future MSE, there must be more introverted Or do not love people who express their views, these people are more passive, often difficult to undertake the important task of the negotiations. From now on, these people have to relearn how to talk, how loud arguments. communication, not just loud speak, to express their views but also found to solve problems and consolidate. In addition, the ability to communicate closely with the social experience, and the PM's experience closely. In everyday life, PM should more carefully, more thinking, when people think of a time to strive for levels deeper than others into account. Of course, there are some practical enough friends to communicate and boast the same thing as a complete, when in discussions with clients far-fetched to say something eloquent words. such people encounter do not know, not very serious or curious customer is a certain market; while the level of responsible customers who do not often find such a reliable, generally not to the list He. PM need to grasp the degree of wind is sure to blow, just bragging when to blow must be based on the field have never been involved in or do not understand what their views easily, pick their own familiar reasonable direction of the play, the right to stay on a two-handed, inscrutable to the other party feeling, the best results.
4. excellent pre team
this team is generally initiated and established by the General Manager, usually do not specify the PMP, a member of the team as SALES, PM, SA, ENGINEER team presented their higher requirements. generally carried out in a list took the time to a certain extent, PM often embarrassing discovery protocol sales representatives some of the promises to customers is almost impossible or simply can not do. This is very much the task is to win sales list, I heard the sales say the most is easy, often for a list will sacrifice a lot. In this case, and sales of natural coordination of head and fell to the PM. In prior sales and customer make commitments, PM to be proactive with the sales of communication, providing a rough The overall design framework and the technical difficulties and can consider the workload, rather than wait out the issue to be passive and sales in the front of the boss tried to shift responsibility. When in the formation of the team, PM team should be based on the quality of each person and task should be set from person to person transmission of information. excellent pre teamwork is an important guarantee for orders.
practice in business negotiations, there are all sorts of questions, PM's responsibilities and requirements for not more than can describe some detail. According to the environmental, policy, culture, relationships and other aspects of the different conditions, PM of the different growth experiences, each PM will eventually create their own views on and experience in business negotiations. But one thing is certain, this PM is the PM to become the first pass, and most important hurdle. received less than list, PM will lose the meaning of existence. and sales are different, PM's task at this stage in addition to orders, but also to collect as much as possible key customer information, and is responsible for all walks of life with each other to establish good customer relationships in order to fully mobilize resources for project implementation.
II. start-up phase
1.
the basic concepts of the project three project there are several versions elements, are different. more into the actual operation of the scope, cost and schedule, the scope of one of the most important thing. We build the project and submitted to the ultimate users of products and documents referred to as the application pieces. When the negotiations must submit the documents to establish the standards and requirements that range. Despite the war, when the inevitable business customers will continue to improve the standards and requirements, and the commitments made there will not be a penny increase. But the standard for every company to that has a bottom line, once more than the bottom line, and that surely is the loss of the project. unless it is profitable for two or to improve relations, or range of more than willing to do when the bottom line, and then in the powerful PM this case can not help it. to establish the scope of need is a PM's many years of practical experience in projects large and small, in exchange for some of the experience of using blood and tears. At this time, it can reflect the difference between PM and technical staff. cost is customer agreed to pay the money, with our input costs are not the same thing. progress would not have much description.
how the project successful? there are some key factors. personal understanding are not the same, usually including the following areas: defining goals and tasks; boss or high-level support; excellent PM and development team; adequate resources; good communication; the positive response of customers and the appropriate monitoring and feedback. here is to note the resources and high-level support. a company is always on the scale of the project also have a lot, but then large companies resources sufficient to ensure each project to build the most appropriate development team or have the best environment. this time the teams or sector resources for the inevitable battle will occur, then the inevitable friction. Zuoren this time on the PM's challenge once again. In addition to high-level emphasis on the PM program, usually in the company if the PM to get along better with colleagues can often Many people solved the problem looks very difficult. On the contrary, does not behave towards PM because of a bad karma, even if the high extreme pressure or team with other departments, others will be dragged to drag and delay the project schedule and quality. Sometimes This internal friction of the project and the PM is devastating. on the positive customer response is more critical. Generally speaking PM has been engaging large and small projects in the exhausted, we must take the initiative to require customers to meet the PM is difficult to do. However, this time, the more difficult, the more tired, more to go to the initiative. customers are often not particularly positive, proactive communication with customers and testing can find problems early. From the perspective of risk control said that the problem identified earlier, the smaller the risk of loss also smaller. a positive attitude can bring the enthusiasm of customers in the completion of the project, the client on your gratitude is often difficult to describe in words, which later received Phase III single-or do will lay a good foundation. because in negotiations with other new customers, new customers will naturally look for your customers to understand the situation, then random words and old customers on top of it to bother you of ten.
project has several important features of commercial activity, there is a consumer, the sources, participants, key factors of success, there are financial goals, there are risks.
2.
start-up phase the main task of According to PMI's explanation of natural orders into the start-up phase after the project. start-up led by PM's main task is the overall architect and systems analyst to collect detailed data as possible to establish detailed requirements as far as possible, further establishing the detailed project range, estimated resources, and establish other programs to gain access to the next stage of approval. At this stage, as in-depth needs analysis, PM also started in-house staff and resources to compete for selection to begin to form their own project team. project about to enter the planning phase.
in after collecting the data, PM, and customers began to clear the project size, cost, size, duration and other important features of the text and write the contract, while preparing for the internal, including budget, measure the standards documents, establishing the project assessment criteria. Then there is the demand analysis. due to professional reasons, we here only discuss the project needs analysis software (hereinafter referred to as needs analysis).
needs analysis the main participants are PM, the overall structure designers, system analysts, familiar with the business processes of customers. PM to guide the team this time is not the real team, we call pre-team. With the gradual deepening of demand analysis, the new team members join, start-up phase ends The team will be established when the official. on an already started project, the project needs analysis will determine the success or failure. The initial demand for the work reflected in the customer's specification or the tender documents and the attachments. This demand is generally more ambiguous, not reflect the real needs of customers. pre-team to customers according to their own experience and to communicate and guide customers into the right track. Sometimes the customer will be very rigid idea of reason, or to requirements set in accordance with his thinking to the needs of a number of obvious errors. The When team members to be patient and give customers the facts about experience, reason, or models with an intuitive graphical way to describe the demand, such as the common data flow diagrams. So, then the inevitable controversy, customers sometimes blow beard Deng Yanjing pound the table or will say, not deteriorated to the point where not clean up. as long as the PM team members try to constraints, the degree is still very easy to control.
of rapid development and iterative development, the demand for and implementation is often carried out simultaneously, the development speed is a major advantage. have the same or similar pattern of small projects, rapid development or use of iterative development is a very cost-effective approach, Extreme Programming is a popular set for this mode of thinking. However, in large and medium projects Too many different needs and modules. If not for the project are different, then the only product on the market without project. Therefore, the demand for medium and large projects to be carefully to do it. We want to discuss an issue, what should requirements analysis and overall design of how much time? waterfall development model we are familiar with are basically needs analysis, design, software development, testing stages, but what should be the first two stages of how much time is not conclusive. operation of the actual project examples show that the longer the analysis and design, needs to do more detailed design, testing, the shorter the time, rework rate is lower, the smaller the risk, cost, the more easily be controlled. and demand analysis and overall design not done in a hurry to develop the project launched early in the project when the problem is not going well, to the testing phase of the project late and relatively long incubation period, but a number of damaging the larger problems will come out, rework, extended test time. So the problem with the items piled to the post-tension, it is better to spend more time to the needs analysis and overall design. lay a solid foundation, it is easy to build a pyramid.
programmers working in Japanese companies probably are aware, Little Japan is very powerful software specification, requirements analysis, and they spend time on the overall design is usually about 40% to 50%, far exceeding the domestic software projects, but also stronger and more effective. They even detailed the overall design specification How do we determine a process to establish what kind of conditions, in other words when, how to write (if. .. else) statements are set to help programmers better. In this software specifications, the programmer is more like assembly line workers, for a module to a certain procedure or technology to become familiar with a complete repetitive work. so often in Japan and Europe will be the work of a low-level programmer, said many people unknown to the domestic programmers also copy of domestic programmers is very unfair. In China, people will copy the code, that do not understand innovation, always rely on others, staring at the table quickly after work to see a lot of programmers is that difficult for the people what kind of future. However, the good and progressive but also a lot of programmers. Since there are not any software specifications such as CMM or very little, so many of these good programmers are doing the systems analyst even the PM of living, holding programmers wages. Although these programmers will start to eat a lot of losses, but also take the initiative to eat the loss, but after a few years ago a programmer with the social status of a clear division appears . When the programmers motivated for business negotiations as the PM, when the former is also frequently change jobs each company, jumping around are not satisfied. Some side-track, and back to our topic. Japan's software specifications and CMM are surprisingly similar, at least 35% or more of them are almost exactly the same. recent economic downturn, Tokyo closed down over 160 software companies, the figure in June this year, and is still increasing. These companies have vied for Shanghai, recruitment technology staff. If you go to such a company should carefully consider the candidates, learn what they can get the specifications and quality control, but in order to become a systems analyst from the programmer or the PM, be prohibitively difficult. often go dry for a programmer for several years, that piece of their incredibly familiar, but something made for my colleagues know nothing about the next door. refused to pass Huawei is trying to CMM4 (Institute of Huawei India has passed CMM4), working in Huawei for programmers unpredictable perils described. Of course, PM or QA has been done or friends love CODING exception.
needs analysis itself, there are time allocation problem. the first pass needs analysis will take the longest time, analysts have in the customers between the various departments have almost run off his legs, said the saliva dry, is to establish an initial demand model. All the documents will be submitted to PM for review and signature, failed to fight back again. Feedback Form subsequently be submitted to the customer, the second time the third time and so much more coming up, repeated discussions and consultations with clients, repeatedly submitted documents and forms, only one purpose, explicitly demand. When the PM finally merged and established all the documents demand, the demand for the resulting document will be submitted to the customer signing the department heads. These documents will be added as an annex to the contract in order to project changes in the future, or encountered a major problem and an important basis for passing customers. be noted that , the customer is not always unreasonable, but honestly, quite helpless, most of the current projects of domestic customers to prevent their money wasted, put another way often and changing needs. a clear demand in the start-up and signed, regardless of the situation How, a detailed written document can solve a lot of verbal commitments or ill-defined document many of the problems caused.
detailed needs analysis has an additional advantage is that both are familiar with some or no attempt to areas never a decision will be whether the project criteria. Sometimes, when signing such big projects both in absolute certainty is not guaranteed to produce results, once the needs analysis phase of insurmountable technical difficulties that would give up the project. typical example is the NMD ICBM defense system. the early eighties of last century the United States engage in Star Wars, Tuokua the Soviet Union. everyone somewhat vague period of history, many people think that the Soviets when the United States on. is not entirely the case, pervasive Soviet intelligence agencies, not deceived so easily. In fact when the U.S. Department of Defense has begun to NMD system software requirements analysis, before and after the cost of hundreds of millions of dollars, spent two years just to do needs analysis, and finally found the existence of technically impossible at the time to reach the height, then the project was abandoned.
3. project start
project start to determine the project plan, work with clients to implement the first project review, confirm and pack down a number of products and services vendor orders. this time the PM will suddenly be found in endless, open three to four meetings a day is very normal thing. These meetings are meetings with clients, and vendors under the package, a team, there are of senior management. team meeting was to establish a formal team to provide the roles and responsibilities of team members, providing performance management, to the members of the project scope and objectives. with customers one of the main conference will kick-off meeting. at this meeting the PM will establish a formal channel of communication clients, comprehensive description of the project, so that project participants understand each other and establish a management system as the core of PM. there are some bits and pieces of things that even the size of office space, telephone number of the Ministry of so all contact should be established at the meeting, and keeps minutes. These are some very trivial things, it sounds like her mother ***, but it is very necessary and indispensable. about the so-called armed forces did not move Food and fodder it first.
this time, as a senior, should be made to declare the whole company, formally released to the PM The appointment of project managers and project authorities. This action although some people seem formalism, but to improve PM My morale and sense of responsibility is a big help to.
III. the planning stage
1. define the structure division structure (WBS)
after start-up phase, the project entered the planning stage, it officially entered the implementation . There may be some concept is not the right track, in fact, the reason the translation, anyway, we understand the meaning of the line, do not rigidly adhere to the literal. WBS is a set of project elements to be submitted, to organize the overall scope of the definition of projects, specifically including the content from the work , resources and cost point of view of scope of the project; establish a system of hierarchical working structure required; the project down into manageable few breakdown of this concept somewhat vague, in fact, with the Explorer in the sub-directory is the same thing. It can be said, WBS is the core of the planning stage. WBS will be assigned to submit detailed documents, including a project to their own people with the process of using the document to the customer with the modules and documentation, complete breakdown of standards and how each of these breakdown of the allocation of responsibilities to specific individuals. WBS are indented and tree type, there is no way I'm drawing here, we refer to some project management books, which are described in detail. I picked the whole article only place I feel the need to pay attention to such as non-essential, tools of the technical details or do not do details. WBS breakdown does not need to break down to the same level, the bottom is called the breakdown of work packages, the sub is based on personal responsibility and credibility, that is, Speaking of every man's task is to implement, is sure to complete; there is control for the extent of the project, the deeper level, WBS tree deeper. Since WBS is a practical thing, according to personal understanding not the same, so a project may have several correct WBS, see PM's needs and the most appropriate state of the current team selection.
WBS definition is still very troublesome. PM to convene to discuss the team, the members of the provide all the details related to the project, and the WBS tree decomposition to the second floor of three. and then take some time for members to brainstorm-type (BRAINING STORM) thinking, the formulation of the duty of the output and the corresponding record for each the completion of a standard work package. In brainstorming style of thinking, there will be a very heated debate, PM to coordinate relations, regulating climate, they can be considered from all angles next to the push to knock on the side, suggesting that members of the angle and direction of thinking and summarized. Although a lot of trouble to develop WBS is still very worthwhile. the same as needs analysis, WBS more fully prepared, the faster the progress of coding.
2. Risk management
Since it is a commercial activity, then the project risk must exist, I believe that friends read this post a lot of people have experienced the risks of large or small. Some risk is easy to solve, and some risk will undermine the benefits. No matter what kind of risks, to avoid as much as possible to avoid, it is necessary to of risk management. As the unpredictable nature of risk, risk management is very difficult, very difficult concept to make it clear, only from the perspective of some feasible to analyze, manage.
first to identify the risks. This is a very difficult high-live. PM first risk identification session was held, the meeting for the company, high-level, cross-sector experience who will attend. and then review the risks generated by the project team with key members of the list and risk communication, examine some important risk sources such as WBS, cost (time) estimates, personnel planning, procurement management. Finally, we must use the PM itself in similar projects in the previous lessons learned.
analysis to identify the following. We can a rough quantitative analysis (exact analysis is impossible.) experienced people can join the discussion, submit them to the risk classification. First, according to the likelihood of points, generally divided into high, medium and low-level , though very reluctantly, but whatever the outcome, there is a quantified; then press the outlay of the cost of points, is also a high, medium and low levels. We are three levels of these two categories are combined, meet the high possibility, costs are defined as high risk can not accept. encounter the risk had to allow customers to modify the demand or increase the risk of reserve costs, or loss once the deficit is not a little bit of it, may pay very serious. high and medium, medium, and The match is a high risk, medium and low, low and low with a low, high and low with a medium.
for the possibility of there, you need to take some means to reduce risk. so far does not have a conclusion that there is absolutely a good way, can only do its utmost to avoid. There are several ways to consider, first is the risk into the project management plan and specify the person in charge of regularly checked by external project risk, if risk occurs implementation of risk management plan; second is insurance, which is to transfer risk; third way a little bit evil, but most insurance is the customer get involved, let them participate in risk management, huh, huh, like that time to speak:)
after risk management as a project plan, PM need to update the WBS, schedule changes and update the risk management plan.
risk is usually reserved for the cost of 8%.
3.
estimate is expected From the perspective of quantitative assessment of the project, including workload, the mandate, manpower, equipment, materials, costs, financial strategy is not expected to pay attention to or quoted.
estimate is not really a one-time work in the project process, the forecast is always needed. estimates seem to have no particular need to mention where, when each PM will naturally have received the project estimate, or a change in the project to the next stage will be estimated. Predictor main function is to have a PM done the end of the hearts of the plan have no idea when the Buzhi Yu.
4.
schedule is a schedule to write long module or function, PM to arrange a date, the establishment of milestone, called the programmers can not be lazy. schedule extracted from over WBS. For PM, the schedule reasonable arrangements to control and motivate the project team morale has a significant role. For programmers, the schedule cents no doubt a nightmare.
shows a sequence diagram the general schedule, Gantt charts and milestone charts. on the back Shao Wei teacher lectures, the recommended tool is the m $ of the PROJECT, I will not use this tool, because no time to explore. I'd use the very first slide, the past month he drew with the PROJECT another milestone in a map, stop torturing me and my colleagues nervous. We usually do one side while the development UNIT TEST, In effect, because there are strong time pressure, efficiency is indeed to raise a lot than before, but we can only catch up, stumbling progress. As TEAM Azeri small, we are a few people to do personal living. I go out every morning at six, after nearly two hours of bumpy, eight more have a seat on the 15-minute lunch meal, till evening at eight work, home meal often has 11 point. more than a month I never had breakfast, have not slept more than six hours Lanjue. Although the strong pressure so that we can in a short time to master the skills as much as possible to develop more modules, but We also have a great emotional impact. Therefore, the project milestone is a double-edged sword, reasonable arrangements will not have to not only promote the efficiency and morale. the gradual decline of the morale of team members will be difficult to bring in later development project estimate the impact, progress will be greatly delayed. on the PM and team issues that we'll come back, and here I first Xianglinsao one, then skip.
milestone chart is characterized by a mandate, membership and time, task and members of the flag with the words, the time and assisted with the figures described in Chart span, the same as the very image of the ladder, at a glance. Management is very convenient, over the hook on it to make a.
task network logic diagram and logic is expressed relationship diagram, you can use the order indicated that the critical path can also be used. In fact, the various activities of 1,2,3,4 into phases, each phase includes a small activity 1.1,1.2,2.1,2.2,2.3,2.4 , 3.1,3.2,3.3,4.1,4.2 so schedule can be divided into four types, generally referred to from front to back and from back to front two. from front to back the concept is an activity must be the same or later than the point directly all activities of this activity the earliest end time of the latest time. some convoluted, we analogy: Stage 2 Stage 3 points, then 2 stages of the 4 sub-stages are also pointing to 3. Suppose the end of time is 1 2.1 12, 2.2 and ends at January 22, the end time of 1 2.3 15, 2.4 and ends at January 20, then the end of stage 2 in the latest time is 2.2, January 22, so Stage 3 of the 3 sub-phases 3.1,3.2,3.3 earliest start time can not be earlier than January 22. As for example, after we all go forward to push it, I do not give, and just hit a few 123 I'm exhausted:)
projects often need to adjust the schedule. does not change the project scope in the case, adjust the schedule there are several ways: the use of fast track means to alter the relationship between tasks; tasks into a serial parallel; changes in working methods (which may change the WBS); change the date restrictions, so that the tasks on the critical path start or end earlier. Although the method of diversification, only one in my opinion, is pressing hard for a programmer labor. How press, or a skill. As previously analyzed, needs analysis multisection time to wait for it, the pressure requirements are less likely; the testing phase is nearing completion late, Luo Liba instigate a lot of things, busy are endless, single-minded ahead of time PM / completed on time, good money, the pressure seems unlikely that time. to say brutal, the most pressure, or CODING, compression coding stage is often the focus, in short, we work hard is it, a large When the project compression programmers in the company dining Lazard is a normal thing, I believe many people have deep experience, sad things here, not to mention. just my summary, so that the future PM who are pressing Later, according to people, huh, huh. test can also be appropriate early the pressure on, when people just completed, are more lazy. domestic enterprises in general are small, there is no specific quality control departments, so often the quality assurance and testing procedures member or PM itself. In fact, quality assurance and testers ...