Extending the Executive Project will delay, in fact, both parties are responsible, it is difficult to completely blame one of them. So once Delay, many people's focus will be placed in "Who should be responsible" this will trigger the dispute. If you have no noisy, please pay attention to the following keywords: "Responsible" and "Responsibility". Joana: Bruce, why do you think we are delay? Bruce: Not because your user's Requirement keeps Change. Joana: How can I say this. If you have no experience in your SA, you can't understand our needs, how can you have this thing. Moreover, many simply is not the Requirement Change. I think it will be in such a dilemma now, and SA is to bear the biggest responsibility. Bruce: How do you say that it is also required? You can go to the meeting record. It's already when it is still reforming business rule. Joana: You can go over the original document we provide. Which requirement is not what we mentioned at the beginning? You don't care about reading your files yourself, or blame us for Requirement Change? Not responsible at all! Bruce: The files you have asked are as high as the mountain, of course, you will need your help to confirm. SA tells me that there is a lot of demand, in fact, when you meet, you will talk about it, you will not be the same as the file. We follow you confirm, you still say that the file is wrong. This is clearly your problem, how can we call us responsible? Joana: Which is this kind of thing? Hey, you are saying that our new honesthe is 喔. She is also a newcomer, I don't have completely enter the situation, how can you grab his words, just chasing it all the way? Bruce: Where are we. However, it is clear that User is not the same as the file. Joana: Then you should be reflected in the meeting record. Bruce: Every time I interview, there are so many things, how can it be recorded? Joana: Remember the place where it is inconsistent, requires clarification, is this not what SA should do? Otherwise, do you want me to write a record record? You even don't have a profession in the following SA, how did you PM? Do you have a sense of responsibility? Our project delay is so long, you are not nervous, you will go home every night. Because of the project delay, let our company's resources have false consumption, what is the resulting loss? Bruce: You are not reasonable, it is inexplicable. I don't quarrel with you! Goodbye ... We have heard it when we were young, and it was not right when meeting. However, in our classroom, I have never taught it. When I meet you, I will come to a matter of right. When I don't have anything, I will point to your nose, what should you do? Basically, when someone does not follow the rules of the game, some people will counterattack. You are fierce, I am more fierce than you; you are embarrassed, I am more embarrassed than you. Therefore, the meeting opened, the two sides opened the firepower and started to accuse the accusation. You are embarrassed, I will not be fully fitted; you have no way to lead, I will embark, you will be unobstructed, tired three armies. Everything in delay is very serious, usually the leadership of both parties have some problems. The results of mutual dissevities are usually two defeatings. Finally, the relationship is deteriorating, often refuses to meet with each other. If you do this, Project is unless.
In addition to mutual attack, the document is often another source of quarrel. The speech is indeed a very incapacius communication tool, but this does not represent communication using the file, there will be no problem. When I first graduated from the school, I think that the more the file should be, the better, the better. Later, the longer it, the more it is, the more you think. Excessive files are definitely the efficiency of killer. If you have experience with big companies, you may experience why I think so. Many times, you can make a big case, you can get the document, may be a hundred pages, or even thousands of pages, the record records may be calculated hundreds of times. In the face of so many information, you have to make it clear about the history of history, and you have to pick it up in the place where you are inconsistent, this is definitely a bitter. No wonder Rational also specializes in designing a Tool for managing Requirement. When you encounter such a file, if Requirement's management has a problem, it has been the focus of the two sides quarreling, usually: "This system, why do you make this? For example, this system is now functioning, which may be modified according to the 1/8 meeting, but the meeting record in 1/22, and a part of 1/8 is overthrown early. Do you think it is OK after 1/22? wrong. 1/29 meeting records may have amended 1/22 meeting to make a revision of MINOR. Wait until you have made it in accordance with 1/29, it is possible that the owner of the Lord has changed a person. He will insist on the original demand document. When a Change Request is coming, how many things are Impact? How many files have to be changed? How many procedures have to be changed? Honestly, if you don't have a good tool, there is no very good process, these issues can't answer. Of course, this is related to the Requirement Management and Change Management's Process. However, how good processs is still there is no way to solve people's problems. What about this? Even if you have a good tool, you also use a good process, people's impression, or it is difficult to change. When a person puts 1/8 of the design, carefully thinking, slowly thinking, finally in the minds of the mind, then he saw 1/22 meeting record, so he thought, deeply Sighing a breath, changed the original design in your mind, and then start modification. However, when he saw 1/29 meeting record, his impression was not good to stay at 1/8. Ok, this is not good, it is already a mess. The problem is coming, what will the system make it look? Not necessarily, there may be a 1/22 spirit, or there may be a 1/29 Request. Not to mention, Designer is watching the 1/29 meeting record, in fact, there are few paragraphs that don't understand. When in Design, don't have some small modifications. This change, it is likely to make a lot of potential bugs, leaving people in the later generations. Hey, it seems that it is far away. Anyway, quarrels with each other for the project is actually helpful. Unless you intend to fight the lawsuit, or just simply don't want the other party, it will not help. Because the focus should not be put in anyone, but what should I solve. You may be able to fight together, the skill is scared, so that customers can recognize them should be responsible.
Ok, how is it? What is your DELIVER? Still do you do? Will the clients make hair, is the project be more smooth? I can't think so. It is a common feature of the most of the project, and "Deadline will be the time of all the trends. "Before you follow the exam, everyone will stay up late to read the book to the Buddha foot is the truth. Every time I arrive, everyone will find a variety of ways to find Meet Schedule. In the face of super high pressure, as well as the ethical expectation of the project manager, the love of the love is often in such a situation, and there are unprecedented shortcuts. The phenomenon I most often saw is "Just do it, do a long and very like something. "It's hard to do, if some small problems, mostty is not easy to test in the first time. Even if it is measured, it is just a bug. When you are too late, no fish and shrimp. First seek, seek good again. Therefore, Engineer often does it seem to be a bitter, and there is a matter of the whole thing in the bones. If you have a sense of responsibility, you will also want to say that if you have passed this, I will come back to make it good. Although most people don't have this, I will change it again to a good opportunity. However, the least these people are still conscience. Some people have happily been to his life after fingering abparation. This situation is the most obvious PROJECT that completely uses WBS (Work Breakdown structure) to perform project management. If you haven't heard of WBS, I will do a simple explanation here. WBS is the work you have to do, constantly, cut to each job is a small and small, can manage. The project manager is going to do, just cut everything, cut a cut, and then send it to the ENGINEER. This approach is in principle in line with the so-called Divide and Conquer. I remember that when I wrote homework, I often wrote the first question. I wrote the second question. He wrote the third question. He brother copied. After copying, everyone is finished. Because this is in line with many people's lives, these people (especially customers) are good, so there is a quantified pointer to follow. For example, this project has a total of 100 programs to write, and now 70 have been written, so Coding has completed 70%. Once a quantified pointer is composed, the focus will be placed in this number, and if the actual progress can be replaced by such a number, it is another problem. In this way, the biggest problem is that these programs may be smooth when they are quantified by false reporting progress in pressure, and actually project truly progress. Operation, once integrated, there is a hundred. When you go further to explore the root of this problem, you will find that many programming designers will take a lot of shortcuts under time. If you take a shortcut, you will have a problem, but if one of them choose is something that looks like, the problem is great. Sometimes, Programmer is not deliberately copied, but for Design or Requirement is not clear enough, he will make a hypothesis itself. Next, I will completely forget this matter.
There is no relationship, whether delimity, or no heart, the results caused by both. For example, in someone's program, you may have written this statement. // lftaxbasicrate This variable should be used to read the data in the file. // It's too late to use the current government's tax rate. Demo will change again. LFTAXBASIICRATE = 0.05 His confidence is full, when I have time, I will change again. Tester test, because there is no discovery because there is no change in the tax rate to set the file. Next, he forgot this thing. It has been arrived at UAT. User feels very strange, how can this function still don't work? Is this function or not? Is it possible to calculate the taxable module? Is it a problem with the tax rate file? still is…. So I kicked the problem back to the Tester for the Development Team. Development Team's Tester will think first: "Which is this? There is no problem when I measure it? Is it a problem with your operation? Is it a problem with Version Control? "Then, on the test environment, the entire re-confirmation, discovery:" Ah! Damn! Really there will be a problem. "Finally, I will lose the problem back to the original author - if he is still inside this Team. You have to find out this problem, the cost of paying is high. First of all, you have to waste testers to find this problem, which may need to find a combination of many test cases. Next, you may have a lot of follow-up time, and you can find this problem in the program code. Hey, if this is deliberately missing, the parties should be able to find a problem very quickly. Maybe you will say, how can you forget your own bomb? How to spend a lot of time? That's right, even if we own, it is possible to spend a lot of time to find yourself in writing a program, in order to hurry, what is intentionally omitted. This is a man with a meal, quarreling with girlfriend, I will forget that when he didn't call her last night, what did he did what is the same. Sometimes, even if you remember clear, you can't confess. His confrontation will get more understanding at the hotel, will you get more understanding? What's more, there are many times, even if it is a parties, even if each liner has any annotation, it is not seen that he can find himself in the first time it is previously driven, and the part of the scavenger. This depends entirely on the time of finding this bug, how far is the time point of his cartridge. If he takes a short time, he may have to spend a lot of time to find some of the mines who have been buried by himself. Don't mention how big if you have already changed to another person. trouble. The final price is to change the logic of the program. Of course, this problem can be avoided through the Code Review, or Pair Programming and so on. Find some people to help you see, when you copy the shortcut, it will compare some. However, what is the Code Review? What is the Code REVIEW? What should I do? Another perfraction is perfunctory in the process. The most frequently seen the phenomenon is that DESIGN is not doing well, and the Unit Test is not completely directly to the Integration Test, and the Integration Test has not made it a good job to enter User Acceptance Test.
Basically ideas, since there is already a pregnancy in October, whether it is malformed, or even a boy, it is still going to see his Laozi. The most often heard in this time is: ÿ 丑 公 公 公 公 公 公 公It is also a knife, and the turning head is also a knife. Ÿ Early death and early birth. When many people arrive in Milestone, when MISS is originally ready to be booked, the way to face the pressure is that this work is already completed as scheduled, and then I will try my best to come. This is particularly prone to the test phase. Anyway, whether all things have been completely tested, and whether the light of the test personnel is difficult, it is difficult to see. Experienced people will look at whether the time curve of Defect converges. However, most of the Team MEMBER thinks, it will tend to be a fast knife, this time will try to convince yourself: "The software we wrote is not good, the customer has not so clear, if they come to the last moment This problem, this is not very good. It is better to know the real situation soon, so they have psychological preparation. Ok, let's start UAT. Every time I saw it in order to catch Milestone, I decided to let the user start UAT project, I feel extremely regret. Catch up with Schedule, lost quality, and trust in both parties, what did you get? Another common process is omitted, that is, the REVIEW does not do, the risk assessment is good, the project assessment is also good, not directly from the timetable, that is, three two laws. Based on my personal experience, many necessary work, once omitted, or doing uncertain, shortening trends in the short term, actually to pay for several long long-term considerations. For the Milestone, Milestone, making many things that are not conducive to the entire Project Schedule, in fact, is very unspys. The pursuit of silver elastic people has been pursuing technological advances, new inventions, new foundings, new production methods, new development technologies, have always led us to go forward. However, Project once started DELAY, many people, especially high-level executives, how much will now look forward to the innovation of science and technology, and can bring immediate and effective results. Somewhere in STATUS REVIEW Meeting. Gina: Bruce, from your Status Report, the current progress has been behindked behind. Do you have any countermeasures? Bruce: It seems that the current project has been on the track again. But if you want to catch the progress, honestly say, it is more difficult. Gina: The current situation is indeed better than before. However, we can't complement like this, and this case is already overridden, we do this, it is already a loss. If you can, you must try the original progress. By the way, I went to seminar before, I heard that there is a method called EXTreme Programming. Do you want to try it? Bruce sighed a sigh: I will find time to go to Survey. See if there is anything that can be used in our case. Gina: It's so good, I know that you have the most adventurous and brave in the spirit of innovation. For most people, bold innovation and stupidity are in the wilderness, in fact, it is very blurred. Honestly, even if we use the same development method, it will have a distinct effect on different teams.
For a team that only knows to write the main frame of the main frame, if they have to use the J2EE even the Oracle database, write the Web Application, and use OOAD to mix Extreme Programming practices. If the light is listening, I feel that this voter is simply a grave tomb, I want to come to a teacher. The introduction of new technology, the new work method is, in fact, it is best to be more appropriate to use progressive methods. Unless you create a new team, too fierce change will be easily indigestion. This is the same as you eat, and many people only consider eating the most cuisine as much as possible, but there is no way to take care of your digestive organs. Is there a way to get this toss. So after you finish eating, I immediately reported to the toilet. Is it because the food is not fresh? Most conditions are because your body can't load so much food. The introduction of new technology is the same. Unless you have created a new team, most members of this team have the experience you need. Otherwise, there are too many new work methods, new technologies in the same project, in addition to the TEAM Member itself needs to overcome, the project is actually a negative impact far more than the positive effect. I personally compare it if there is a new field to try, unless you don't care at the success, otherwise, don't try more than a new technology; in turn, if you do just a pilot project, this Project is originally Is it used to practice, Well, Have Fun. You Could try as a youow? I think the answer is yes. However, for Projects that have delay is usually ineffective. Because Project will delay, most of them are management problems, and have nothing to do with the technology. Most of the problem, most of them are not introducing a new thinking, or introducing a technological innovation, can be solved. Any new idea is usually needed to experience the organization's learning, and the continuous practice and revision in actual work will be successfully implemented. This process usually takes a long time, so I will not be able to save Delay's Project. Moreover, most of the time, manager people want to introduce, are new engineering technology, not any revolutionary management concept. New technologies, encounter old thinking, the original existence still exists, and limited time and energy take spending on these new technologies, these factors add up, usually let the Project, Delay of DELAY more serious. So every time I heard the high-end supervisor, I will come to a big revolution in the project that has already been destroyed. I will always meditate on Amitabha, I hope that God bless you, Amen. Increase the frequency of STATUS Report on your Project Review Meeting. Joana: Bruce, according to your profession, you think this time, how will schedule will delay again? Bruce: Based on the discussion of our Team Member, I think it takes a few days to give us five months before it can go online. Joana: Five months? how can that be? I have no way to accept this SCHEDULE! This Project has been an end of six months. It has been 11 months now, and you tell me about five months? ! Do you have a mistake?
The promenade of your company, also told us that you can get a case last month, and she is gone for two months. When you start picking PM, don't you say that you will give you three months? I think you have nothing to know about the situation at that time, I can accept that you estimate is not accurate. But didn't you say it for four months last month? What is the sudden situation in this period? As a result, you actually tell me that you still need five months! Joanna thought, you have these eggs. After picking this Project, you will be unlucky. It seems that my performance is like this today ... so, I will continue to say: I have no matter what you project is not good, I will help you do. I want you to sort out, everyone should work every day, that is, you want to give me a Daily Schedule. You have to prepare a Status Report every day, I have a way to follow our Senior Management Update the latest Status every day. Our two people have to sit at least once a day. REVIEW STATUS. As long as the progress is behind, you will immediately ask an Action Plan, explaining how to catch backward progress. I don't think so, we have no way to master your progress. Don't do Daily Review, this time you will still delay. Then I walked out and left a foundation of innocent Bruce. The more time you put on your write report, the less you can write the process. This seems that there is no need for IQ, you can inquire. But for many customers, they will feel that delay is because they don't have the most complete and detailed information, so that they have no way to make the most favorable disposal. As long as they have the most abundant, most real-time information, they can smoothly achieve the most favorable decisions for the project through their extraordinary talents. As long as they do such perfect decisions, the progress of the entire project will move to a bright future like a constant rotating flywheel. Ok, similar stories I often hear in the stock market. Master the most complete and most abundant information, with the teacher, you can have super high profit. So there are many people, and the information is collected in the days. Then, hurriedly follow the information he collected. Therefore, the short-term continues to enter and exit, and kills it again. In general, this kind of people earn any money unless they are the end of the owner. But for customers, they will not think so. For them, it must be because some people are lazy when they are doing things, or do not have a whole force to do things for them, the project will delay. The conclusions that can be derived directly will be, "We need to keep the latest, the most real-time Status Report can do a good job in project management. If these people are just the words of WBS believers, they are even more miserable. They usually require the project manager to cut the system into many fine Program, and then provide the Status Report by Program every day. Then, the big eyes are watching this small Program, and if each of them can be completed as scheduled. For these people, project management is a simple matter, you only need to cut your work first, then hand it over to Team Member, then just collect the progress of Team Member every day, after complex mathematical formula You can get a simple pointer, such as "87% of the entire project has been completed today. "The next job is to stare at this pointer every day, hold the leather whip one hand, and the other hand is holding red, and trying to do things in Team Member.
"Hello, today's scheduled progress is to complete the 90%, no need to go to get off work. I really have such a customer. Of course, she will feel that I am too simplified. However, for her, the profit of the project management should also contain the following three points: 1. Want to buy dinner or eat the Team MEMBER. To reward the hard work of their overtime, because they must work overtime to catch the progress. 2. To apply for the ON Site personnel to apply for their company's pass, so as not to let them go in. 3. Be cooked on the day of progress to avoid recovery within one second when high-level supervisor is temporarily inquired. When the frequency of STATUS Report increases, it means that you will spend more time a day, explaining what is currently progressing now, what is the difficulty encountered. To make the management class, you can more quickly grasp the dynamics, and more quickly solve the problems you face. However, the most difficult difficulties in the project is that there is not enough STATUS Report, which means that it is necessary to open more meetings to report the progress, and to open more will, to discuss how to catch backward progress. This will inevitably lead to less working hours, but also say that it is necessary to catch up with more classes. If Project Manager is forced to report the progress every day, then his most typical reaction is to be a Status Report every day. This will eat small fish with big fish, eat shrimp rice, and shrimp rice, you have to write to Status Report's truth. Increase the frequency of STATUS Report, in fact, the cost of the entire development is increased. Project Manager can report to a new developments today, and will certainly have a bunch of Engineer to help him collect information. You make Team Member spend more to help you prepare a wide range of progress reports, they can bet in the actual development work will definitely be relatively low. Of course, the high frequency of the frequency does not have a certain standard. For some people, the DAILY REVIEW progress is a matter of habits; for some people, a week, or a few perceived REVIEW is a normal state. There may also be different standards in different phasers. In the development phase, it may be a progressive schedule for two perception; when UAT may progress every day, it may be scheduled. Any habit of Team MEMBER or the different frequency adjustments to them, except for the "non-productive work", which is expected to be "non-productive work", which is expected to spend more than the original time. Any measures to adjust frequencies should be made after cautious thinking and adequate communication. If you come back, you know the progress every week, you know the progress of a fabrication every day, is it really so big? Creating a nervous atmosphere to scare yourself, what is the benefit? When you spend too much time to do micro-management, you will not have a thought to do real management. Increase the manpower and the incinerator backward progress? Overtime? Is there any problem? Do you want to add some helpers? That's right, this is Project Delay, the most typical thinking mode. Increase people, it is not Always is a bad thing. This may be a timely rain for the project that has a serious insufficient manpower. Increasing people can solve the problem. Many people have heard MAN-MONTH Myth, there will be an illusion that I should add people anyway. The result of directly inferred, the conclusion is: Any project can only be alone from the head. Otherwise, add anyone, will delay the schedule of the project. Of course, this is not a correct argument. So most people still want to increase people.
Just if the number of people is sufficient, even too much projects are already too many projects, it will be much greater than the positive effect. In fact, if the number of people goes to the project manager, if you don't have the strength to manage, you should find a way to add management level, otherwise it should be that the project member is right. Sometimes, add new members to greatly reduce the burden of existing members; sometimes, increase new members, will increase the burden of existing members. How to do it, it is better, and it is ingenious. This is nothing standard approach, and each case will have different conditions to consider. Although I am not an expert in this field, I share a few directions I usually consider: 1. Does the workload of existing members have exceeded their workload? If everyone looks like a heart, then don't find someone to help, it is about to be prepared. 2. How much is the inheritance of the new member? How long is it to take? If the person found, there is no way to go, but it is necessary to have a long time to teach him. At this time, I will ask this person to do some of him. Or just simply ask him to leave this Team. In addition to fearing that the main members spend too much time to teach him, the obvious work and rest is not equal to the situation. Efferson: Bruce, why Blade can serve as a senior engineer, and I am just an engineer? He is coming to our case, nothing will, teach him to hear it. We have already delay now, I have no way to write the procedure, and take care of him. I have been tired of half a dead, I have to spend time to teach him, the most exciting thing is that his position is better than me, the salary of the collar is more than me. What is the reason? Bruce: No way. Blade is a doctor graduated from the famous school, which is just Gina's favorite. Although he has no practical experience, but Nina has always feel that he will contribute to his knowledge, fake day. It's just when he studied. Efferson: This is not. We have delay so bad, and we have to bring a tuning bottle. Bruce: The words are not said to say, you try to see what you can do. Anyway, we are now inadequate, or you are looking for something to make a good thing. He wants to feel is not interested, you will leave it yourself. Efferson: Otherwise, I have to change my Message or change the GUI's work. Even if there is any situation, it will not cause too much harm. 3. Does the existing member will have an asynchronous in the short term? Will you want to leave? Transfer? Is there any other person familiar with him now? Anyone who is tied to work in hand will affect the project. So whenever someone wants to leave, it means that it is right when he is drinking coffee. The project has been long, slowly understands the real phenomenon of life: "Any one you feel 100% can be cooperated, absolutely no problem, people who will fight together with you, may be left between day. Some people are for the actions, like leave, transfer; some people will suffer accidents. It is like a change in the home, or has a serious illness, suddenly issued. The deeper your reliance on him, the greater the loss of his hit. So at least few people can be backed with each other, so that as long as you don't have 911 strike, just the entire Team is in the World Trade Building, otherwise it should be able to survive from members.
However, in Taiwan, it is insufficient manpower, it is home to meal, so that ENGINEER will make each other backup, which is simply an idiots. When I am school, I always feel that as long as I have a document, I don't have OK. As long as the person left, leave enough documents, there will be no problem. Now I understand what I have children, how much is free. At any time, take off an experienced person, even if he leaves more documents, there is no way to make up for this loss. Those who take over, often the time you have to see the file a long time, let alone if you have a situation now, you have to find the right file in a short time, this thing is much more difficult . There is no way to replace experience, of course, not all senior people have experience and intelligence. However, there is an experienced person, the moment he leaves, it is definitely that others can't replace. Many smart people are from the actual lessons, learn the intelligence and experience of survival in the dilemma. These people often determine the correct decision as long as they are intuitive. For enterprises, the only difficulty should be that if a person is intelligent, it will not be written on the face. If a person is determined to go, it is necessary to rain with the sky, the daughter is going to marry, can't stop. If you can do it, you can find someone to handle it with him. Many times, we have worked hard when important members have to leave their jobs. However, how to hand over, actually the effect is limited. It's better to think about it, how to do it can let these people will stay together. 4. Which phase is currently in the project? If it is already in the end of the project, is there a new face? Sometimes, the high-level supervisor will do nothing because there is now someone else. If you ask the project manager, do you want this person to join a project. Honestly, some things have passed that time, it is not so important. Every time I saw this last moment, I thought that I saw such a scene: men and women, after I experienced a bed, I started smoking on the bed, and when the man suddenly took Out of a sentence: "What, today is not a safe period, then I just don't wear it? "This is the same as the UAT, I assigned a SA to join this team:" You will talk about this now, will it be too late? "As far as the project is concerned, the venis, sometimes it is better than just, there is no support. Do a lot of things, the timing is very important. If a person does not have the right time, join this project, it really should be considered, and there is no need to let this person Join. Even if his ability is strong. 5. What will the newcomers will cause changes in the political relationship of the organization? Will not join a person, but it is derived to a lot of questions to deal with it? For example, Wei Jun and Shaoy are in love. Wei Jun is already inside Team, I will avoid the searching in Shao, otherwise the two bars will play in a prettyssion, let everyone chicken skin fill, this Can not stand it. If Wei Jun is not good to with You Wei, three days a small noisy, five days a big noisy, I will also avoid finding Youwei. In addition to increasing people's hands, the most often seen is overtime. Even the overtime, may help productivity, too frequent overtime, will have a negative impact on morale and actual productivity. I don't recommend that in any delay project, work overtime as a way to catch progress.
If you only need even, the short-term overtime plan may be try it. So far, the solution I have raised is not actually effective, and it is good to take a look. However, the next few methods is that I think practical programs can really happen. Replacing the project manager For a project already delay, it is a bad thing to do it. Just want to under this decision, it takes very cautious thinking. The will of the parties is especially important. In fact, there are many project managers, they can't help you. For successful people, it is necessary to take a hot saggy, so the two sides to handover, they need to be careful. If you have a few projects to be hurt, I suggest you give priority to the project that is in short supply. For many project managers, the people are insufficient, and the time is not enough. It is often a convenient meal. However, in the universal situation, there is always some of the days of the project manager, and it is more hard than others. Therefore, relatively, these people are dissatisfied, and they will be profound than others. This is highly low above the EQ of this person, in fact, there is only indirect relationship. The direct association will be the shortage of this case resource shortage, how is it serious. When a person feels isolated without helping, the inner grievances and dissatisfaction often take a considerable negative attitude towards the project. Once at this time, it should be replaced with PM. I personally suggest that the project manager can be considered in the following circumstances: 1. The relationship with the customer is already as water. 2. The project manager has begun to lose reason, unachable, and taking a very radical violent means to carry out Management 3. The project manager is obviously unable to load. There is no way to conduct appropriate management measures for existing projects. At a time point, it is definitely chess, it is possible to make the project to rebirth, and it is possible to make the project. Any new PM will have an adaptive problem. If he is with most Team Member, he has not experienced experience, it will also have a problem in tacit understanding. If he arrives, there is a potential issue that can be more than his arrival. Because the result of replacing the PM is difficult to expect, if you can do not change, it is best to be the original class, all the way. However, if the existence of the project manager, there is no way to have any positive benefits for the team, then replace the project manager in time is an essential measures. Otherwise, the problem will continue to spread, and it is difficult to pick up it. Focus on the solution, rather than responsibility home for a certain Project Review Meeting, Joana's boss Mike and Gina are attended. Mike: Bruce, can you tell me, what we will now be DELAY root cause? Bruce said very nervously: At present, we will delay's root cause, because Requirement is not clear. User presents too many Requirement in the process of development, completely no control. Joana: This statement is not fair. Because your SA change relationship ... Bruce said: We have a complete handover. I feel the biggest problem, or because the user's needs have not been determined ... Mike interrupted Bruce with Joe Anna words: It doesn't matter, you don't care. If this is root cause, Bruce, do you have any corresponding Solution? Bruce: Of course.
I think the best way is to use our current prototype to re-interview with USER. Then ask our SA to carefully write User Case and communicate well with USER. Mike interrupted Bruce again: there is no relationship. Since you already have Solution, I think you have to discuss your Action Plan with Joana, including the re-planning of the entire resource, Schedule recombet. I want to go to the next week, you can see your full Plan. Don't know Gina, do you have any view? Gina: Today, I am coming, it is a learning psychology. Sorry, our case will cause such a big trouble. We are of course a psychology that holds the prudent fear, and I am also very thank you Mike to give us a chance to redeeptify. I think Bruce is so good to be so good to follow Joana. I can take this project to a paragraph ... (Well, she continued to play the official cavity, because the official is very big, so everyone has to take nicker.)
When you criticize others' speech, do you not count your personal attack? However, in the dusk process, we will not worry about this.
So any Schedule and Scope are likely to impact the existing ideas of these people, and this is the most difficult part. The development of software projects is mostly in management and political. True technical puzzle is good, political issues are truly tricky parts. Moreover, most of the time, Scope is actually clearly recorded in the contracts in both parties, and if it is more difficult to change, it is more difficult. Therefore, in most situations, modifying Scope can only be used as one of the filings, and cannot be a primary solution. Re-order reasonable Schedule, and cooperate with moderate project assessment measures to develop, things are not as good as expected, usually very high. Self-deception should not be a strategy, although you may have a pretty lofty reason will say some "good lies", but this strategy usually has a lot of negative effects. I personally think that absolute honesty will be more appropriate, put all the questions with the truth in the sun, is the best solution. Estimate Schedule, actually following the bidding product. You want to marke with 100 pieces, someone shouted 101, will you want to add a little more? Every time you don't add code, it is actually a chance to judge. In addition to the SCHEDULE, the more it is, the more like it is, the more like it is very similar; to put forward the latest price based on the market in the market, actually very similar. The project manager is actually based on the current situation, and the entire Schedule will not be affected by the current situation, then make a decision-making. If you just simply put the performance of this Phase to the next Phase, in addition to the chance to exercise the evaluation and forecast, it also lost the possibility of adjusting your strategy with things. . Therefore, in the process of the project, it is actually necessary to perform the assessment of the project in an appropriate timing. Unlike the solution method, it is actually mainly above the attitude. Constantly assessing the project is not to find excuses, nor is it in the end of the prediction project, but what is the problem now is to get a solution, and how you should invest in the project. When the project manager began to earnestly evaluate the state of the project, the core of this is the core of the solution is how to be able to knock out of a two parties accepted. Most of the time, based on compromises, both sides can only discuss some of the short-term advantages, but for long-term harmful Solution. For example, the most common method is that we add a PHASE, first press the User's more urgent function, in this Phase. In projects already delay, the win-win program is almost absent. The best result, of course, talking about the customer and the manufacturer, what is the main goal of this project? What to reach a goal, what can you do in a limited time? And the entire project is going smoothly, how much time will it spend? After all, in the project, it is estimated that a piece of chaotic should have to make some degree of correction will comply with the actual situation. Only the two sides are sitting down and open the targets of the two sides to complete, and discuss, and redefine Schedule, and set appropriate project assessment measures, so even delay, at least within one control range. As for how to evaluate, how do you control it? I want to recommend a kind of I have not fully actually used, only from the book: "Critical Chain Project Management" (Author Note).
After I have read the relevant books, when I manage the project, I usually clear the FOCUS, gathered on the Critical Path and Resource Availability. These Concept usually can't find it in software engineering books. ※ Author Note: I really have this book called this name: Critical Chain Project Management. Just I haven't time to read it. If you are interested in how to arrange Schedule, I suggest you go to see the TOC book. Here again, it is recommended to Critical Chain written by Gau derat. But because this is this novel, so I suggest you find some related extensions. I read it myself is Project Management in the Fast Lane. The concept of inside, it is quite useful to me. :-) The conclusion once time, I received a new case, only three people were in the beginning. Later, MISS was darker. Milestone was blinded by the customer to the dog blood. I started working hard, and the day was overtime, and the whole project was ruined in her hand. Partners working with me, are also in the potential pressure I applied, very hard work. In the end, the project Meet Milestone after delay, and Deliver out some things that look like a system. But most of the Team Member walks. For me, although we seem to have something to do, it is a successful failure of Team Member, so that this project is a thorough failure. When you see a Manager, force Team Member keep working hard, hidden in his heart, is a soul that is afraid of failure. Many times, when you care about the success or failure of the project, the more you lead all your behaviors, your thinking will become narrower. How can I jump into this dilemma? Change the angle. First assume that your case is the failed, DELAY is far beyond your imagination, think about what you will do? How many strikes will the company be affected? Try to accept this fact, then think about it, do you have something that can be done, let this project out of this completely complete failure? Is there any opportunity to improve? No matter how small improvements are good. Usually, after thinking, there is a chance to look at things from a completely different point of view. DELAY is delay, how is it? Didn't be this Project Fail, as a high tuition fee for your company. So what? Once you can set it, you can have a chance to rebirth. Everyone will have different ideas for a work. Because everyone's ability and experience, the same thing is given to different two people to estimate, which rarely estimates the exact same SCHEDULE. In addition, integrate everyone's things, how much time it takes, is a more difficult to predict. In the current popular way of the industry, if you are a person who uses a traditional structured system to analyze the development system, you can use Function Point to help estimate; use UML OOAD, you can try to use USE Case Point to estimate. There is also a set of theoretical depending on these methods. If you have a system you want to develop, you can of course also use WBS to plan, just remember that the time to make everyone integrate together, but this time is usually not short. No matter which method you use, it is necessary to continue to collect this information. This will give you a chance to know.
