Tom. Di Mi's "deadline" is a good book. In the book, Mr. Pukins, Mr. Pukins, continuously summarized records in management and life, and accumulated 111 principles on software project management. It is now extracted to share with you. 1. High quality management four elements: 1) Choose the right person 2) To assign the correct work 3) Maintaining their enthusiasm 4) Help the team condense and maintain the team's cohesiveness (others are just a "copy") 2 , Security and change 1) Unless it is safe, people cannot meet changes 2) In all successful work (and in most other valuable work), the changes are one of the basic elements 3) Safe The lack of feelings will make people oppose changes. 4) Evasing risk is fatal, because this will make you unique to the same interest 5) People may feel that there is no sense because of direct intimidation from the objective world. However, if the managers may abuse the power to punish themselves, they will feel that there is no security. I don't have a sense of negative effect. 1) Threat is not to improve the best results. 2) If the assignment time is not enough, no matter how scared people regardless of the threat Work also can't complete 3) worse, if the target is not realized, you must honor your threat 4, the body part of the manager 1) Management involves the heart, the stomach, souls and nose 2) therefore ... Come to the leadership believe that your stomach (believe in your premonition) Building team's soul training a nose 5 that sniffing the lie, a metaphor for the management of the war 1) When the battle begins, the real work of the manager has completed 6, interview and recruitment 1) Recruitment involves all management-related body parts: heart, soul, nose and gastrointestinal (but mainly gastrointestinal) 2) Do not try to recruit alone ---- Two parenteral stomach is more stomach Two times better 3) For new employees, let them bear the same difficulty projects that have been successful, and postpone challenging targets to the next 4) Distinguisice: The person you most want to hire may still Know that other good people choose 5) more, less say 6) If you are ready, then all things will be better 7. The increase in productivity is 1) There is no "short-term productivity". 2) Productivity Increased 3) Any promise to immediately see the effects of the Estate Oil 8, Risk Control 1) By Control Risk Management 2) Create and maintain risk statistics for each project Table 3) Track the risks of rooticity, not just the end of the nasty results.
4) Evaluate the probability of each risk and possible overhead 5) For each risk, predicting the early signs of its avatar 6) Appoint a risk control company, this person should not maintain the internal "I can travel" Attitude 7) Establish a simple (possibly anonymous) channel, let the bad news can be passed to high-rise 9, prevent failure 1) Strong brings 2) Controlling failure than optimization is more effective than improving your comprehensive grade 3) Working as soon as possible 4) Unless it is necessary, don't condense a team: Go out to find a forming team to use 5) to maintain a good team (as long as they are willing), to help your successor to avoid The team coheses slowly or cannot condense the problem that is condensed together - ready to be fully, and willing to accept new work - as one of the gains of the project 7) The day of the project is wasting day and The day of harm on the final stage is the same 8) There are countless ways to waste a day ... but there is no way to take back time 10, the modeling and simulation of the development process 1) Your intuition modeling of the completion process 2) Use these models in the exchange of colleagues, in order to exchange, refine the idea of project operation 3) Use model to simulate the results of the project 4) Adjust the model 11 according to the actual results. 11, " The first day of the disease, it must be prepared to gamble ... 2) ... but this does not guarantee "sick politics" not affecting you 3) "pathological politics" may be anywhere In the most healthy organization of 4) "morbid politics" features: the desire to personal rights exceeds the organization itself 5) Even if this unreasonable goal is backed by the organization's target, it may also appear 6) The worst side effect of "morbid politics": it makes a streamlined project to be dangerous 7) Don't want to cure a sick person 8) Don't waste time, don't make yourself threatened because you try to treat the disease. 9) At the time, your only choice is to wait, wait for the problem to solve, or wait for a chance to continue to move forward 10) miracle is possible (but millions don't expect it) 12, metrics 1) Measure each product Size 2) Don't persistence in units ---- When waiting for the objective metric, first use your own subjective unit 3) From all the original data (can be calculated software characteristics) to construct metric unit 4) Original data is collected in the completed project to derive birth productivity. 5) Continuously improve your metrics until its calculation results are the best corresponding relationship with the project workload in the original database 6) A trend line of the database. Put the expected workload as a humanometric unit The value of the value is displayed 7) Now, for each item to be evaluated, the unit value of the artificial metric is calculated, and the intended working value is found on the trend line in the trend line) The interference level around the productive trend is mapping. Tolerance indication 13, process and process improvement 1) Good process and sustained process improvement is a great objective 2) They are also very natural goals: excellent technical workers will pay attention to them, whether you tell them 3) official The process improvement procedure needs to spend money, spend time; the specific process improvement work will delay project progress. Although it will eventually reflect productive gains, they cannot offset the time of flowering in process improvements. However, projects have a sufficient income from a single, correct choice method, and win back to this time Change paying time and money 5) Do not implement improvements within the range of more than one method during the project.
A variety of technologically improved procedures (for example, improvement of a CMM level) is likely to make projects than to implement these programs to complete the more than one night. 6) The risk of standard processes is that people may lose important opportunities for shortcut 7), especially for The standard process will look very rigorous because they have made enough work (useful and useless), so that everyone is busy without 14, change the way to do work, 1) If there is no big reduction The time of debugging, there is no way to complete the project in advance 2) High-speed completion projects are used in debugging. 3) High-speed completed projects are also proportional to the design time. 4) If you don't care about others, don't take care of others, don't want them to do some unusual things for you. If you want them to change, you must understand (and appreciate) their past 15. The effect of pressure is 1) The person under pressure can not think more quickly. 2) Increase overtime time will only reduce productivity 3) Short-term pressure and even Overtime may be useful strategy because they can concentrate their employees and make them the importance of work. However, long-term pressure is definitely a wrong 4) The reason why the manager will apply so much pressure, maybe because they don't know what to do, or feel discouraged because of other ways, 5) the worst guess: use pressure and The real reason for overtime is to let everyone look good at the project failure, the angry and humiliation in management will be delivered. If the senior manager likes to swear, the low-level manager will also learn (just like a child who is often smashed into a parent) 2) The insults in management are considered to be a stimulus, allowing employees to improve efficiency . In the management strategy of "carrots", insulting is the most common "big stick". However, can you do better after being insulted? 3) If the manager uses the method of insulting to stimulate employees, this shows the manager's incompetence, not the employee's incompetent 17, ambiguous specification document 1) The vague marks in the specification documentation have no difference between different system participants. Solved conflicts 2) If a specifications do not include a complete input list, it is no hope: it has not begun to indicate anything 3) No one will tell you that a specifications document is not bad. People tend to blame themselves, not blame documents 18, conflict 1) As long as there are multiple participants during the development process, there must be conflict in the process of conflict 2) creation, installing the system's business is particularly prone to conflicts 3) Most system development teams lack the ability to resolve conflicts 4) The conflict should pay attention. Conflicts are not a lack of professional ethics behavior 5) should be declared in advance: Everyone 'Win' is attached. Make sure everyone at each level will win. 6) Negotiating; Mediation Easy 7) If the interests of the two people are completed or partially rejected, pre-arrangement, ready to resolve conflicts by mediation 8) Remember: We are standing on the same side; with us Aligned, it is a problem that we have to solve 19. The role of the catalyst 1) There is such a catalyst. Such people will help teams form and condense, maintain team health and productivity, resulting in contributing to projects. Even if the "catalyst" does not do anything (in fact, usually they will do a lot less), the role of this catalyst is also important and valuable 2) mediation is a special job of "catalyst". Mediation is learning, and only a small investment can learn 3) mediation should start from a small ceremony.
