How to ensure the project progress according to plan is the focus of each project manager's work. Each project manager has different methods and means. Today I will introduce to you a way I often use,
commitment . The specific meaning is to allow the stakeholders of the project to make corresponding commitments, so as to ensure that the project to the good direction of development. Someone might say, what's the use of a promise? System, reward and punishment measures these are kingly. In fact, let's take scrum as an example to talk about how to use commitment to ensure project progress. The Agile development methodology in scrum is a number of important activities that are planned, daily scheduled, reviewed and reviewed. Project managers who have used scrum should have a deep understanding that it is not easy to open these few. The plan will be able to open like swearing, if you can open the full-court mood, everyone is trying to be effective, to achieve the purpose. The goal of the program is to make everyone realize that they will be "pigs" in the project, and everyone understands what the project is all about. If we can make the project members speak out "we can do it", the project manager is passionate and has managerial skills as a project manager. Not to mention the importance of morale to the victory of the war, but the act of shouting out what I want to accomplish in public is a promise to proclaim the world. No one is going to make this commitment a misnomer. So, once you say this, you have a bottom line in your heart. However, the promise of the plan is only a general commitment, can only guarantee a good head, and can not guarantee that the implementation process is not biased.
How will commitments be carried out in the project? How can the commitment step into the project process and ensure that everyone's initial commitment runs through the entire project execution process? Scrum has a second characteristic activity coming up, the daily meeting. People who do not understand the principle of this activity may turn this into a mere formality, making project team members drowsy and feel dispensable. In fact, there is a lot of learning. The Daily council basically says three things, what was done yesterday, what to do today, and what the problems are. These three things are basically yesterday's summary and today's plan, there is need to coordinate the resources in advance to inform. "What was done yesterday" is the progress data embodied in the project progress, and the project manager or project master organizes the data to form a project progress report. the deviation of the project schedule does not depend on the amount of daily progress deviations, but on the sum of one phase. So it is very important to control the daily progress deviation, try to correct the progress of the deviation. At the same time, "What was done yesterday" is the project members self-summary of the work results. There is a psychological phenomenon, that is, when yesterday's work efficiency is very low, did not complete the plan, in front of the project members have a sense of guilt and shame. Psychologically there will be a demand, the day to catch up with the progress, this is what we want to see the results. "What to do Today" is also very interesting. If you do a little work plan today, you will be afraid of being pointed out to make a fool of the public, so everyone will try to realistically do the planning and progress assessment. A good project master or Project manager should guide the daily meeting to achieve this effect. Only in this way can we ensure that the commitment runs through the project, reducing the direction of the project deviation. If the daily meeting is a commitment to detail, then the project review will be a formal review of the project manager's or user's commitment results. At this meeting, the project members have to come up with their own results to verify that their original commitments were fulfilled. If you can't do it, you can't accept it for a highly self-respecting programmer. So in addition to demonstrating the results of the project phase, the meeting should also be intended to compare results with commitments. retrospectives are the reasons that help project members find gaps in outcomes and commitments. Essentially helps project members correct their problems and ensure that commitments are fulfilled in the next iteration. In General, scrum has a much greater incentive to project teams than traditional project management methods. Because it will each project member launches, stands in front of everybody, uses the language to set a goal to oneself, and uses the language carries on the self-evaluation. In private can say some false big empty words, in front of the public any lie, empty talk, a big talk will be questioned, this to a certain extent to ensure that everyone to the real, to the exact close, so as to ensure that the project progress deviation too large risk reduction. Commitment In addition to the application of the project schedule management, but also can be applied to customer coordination, departmental coordination, communication and other aspects of the subordinate. Everyone will be responsible for what they say. The project manager takes advantage of this to avoid many unexpected things. Original: http://www.csdn.net/article/2014-09-08/2821580
Commitment, the big kill device in project management
