Transfer from:
Http://soft.yesky.com/softchannel/72342393352880128/2005032880128/20050326/1926972.shtml
The child asked Confucius asked Tires, Confucius said: "If it is possible to implement five moral character in the world, it is benevolent." Confucius said: "Qiegong, generous, believe in, agile, Shi Hui. Qian Gong is no one to bully, generous can get the masses, the confidence can get the appointment of others, agile, do things, and Shi Hui is enough to make people."
- Guide from "Modern Edition of Analects"
Software project management is a complex activity that involves planning, organization, implementation, metrics, etc., always around time, cost, range, quality and other factors. Surfaces can be seen without any individual problems can lead to difficulties, each problem can be solved, but when they are entangled, when they are accumulated together, the actions of the entire team will be slower. The challenges and tasks we face are in the actual progress and limited resource scope to find a practical feasibility to solve practical problems. Lift software project management, most of us think of some documentation based copywriting work (schedule, status report, conference plan, progress tracking record, milestone report, etc.), however, most susceptible to managers ignore But it is a very important factor in: Effective management of people's effective management and effective management of project risks.
As a company or a team, you need to achieve business objectives through employee's progress. However, if there is no incentive, the employee's morale can not be checked, and your goal will become prominent. Therefore, in a person-oriented corporate culture, carrots are almost everywhere, and showed all kinds of pleasant forms, which is bloody. Similarly, you also need some carrots to create a positive team culture, including the carrots that don't spend money (both emotional investment). Effective authorization is not only a carrot that encourages employee to enter, but it is often capable of achieving the two-pointers of employees and enterprises. On the one hand, they can meet the individual pursuit of employee's establishment, and on the other hand, it is also an inevitable choice for realizing the company's strategic plan. Otherwise, the employee will not think about it, and as a manager will also fall into the customs.
- 聽聽 聽聽 聽聽 聽聽 聽聽
Management, especially the management of people, as early as thousands of years ago, human beings began group life, forming early society, has begun to form. As an excellent manager, you must face four major elements: First, choose the right person. Second, assign them the correct job. Third, keep their enthusiasm. 4. Help team condense and always maintain team cohesiveness. As a project manager, your main work may be to create trust, open, active exchanges for the team, and effectively eliminate the isolation and conflicts between team members. As a qualified manager, your mind should always understand a truth: "Your subordinates are willing to work, not because of your personal charm, not because they like you, but because you Like them. You like, respect everyone who works for you, you care about them, care for them, their questions are your problem, their worries are your worries. Your chest is as wide as the sky, in a person truly Prove that your ability, you trust him, you let them think that you regard them as a family, this is what they like to follow you.
"This is the so-called" dedication ", so that the part is consistent with the values of the leader, so that the subordinates will die with the leaders, and will not fear any difficulties and dangers, showing the spirit of lofty dedication." The wise is not "Dark owner", in a faint manager, it is impossible to keep high-profile talents. If you don't care about others, don't take care of others, don't want them to do some unusual things for you, even if you master power There is no harmony. If you want them to change, you must understand and appreciate their past and believe in their current ability. To remember that your team members will be very intended to respond, they see your reaction will determine them. Is there confident on the status of the project and the future development. If other members accuse another member is an impulsive behavior, you will regret it for this, especially if you haven't figured out all the truths, you must have prior Consider the consequences, in theory, as long as you don't exceed the date of the decision, you will be better later, because you will get more information, if you find a wrong decision, you should be willing to make it right away. Corrupt it. In addition, the angry and humiliation in management will be infected. If the senior manager likes to swear, the low-level manager will learn according to it. If you want to use insults as a stimulus, you can make the employee to improve efficiency, then It's a big mistake, no one can do better after being insulted. You can only show the incompetence of the manager through insulting the way, not the incompetence of employees. Need to add a point, the arrogant culture in corporate culture It is also infected. If the senior manager likes Ah, the low-level manager will not only have the model, but also listen to the list, will learn to be charming. If this, the motto of the following employees will change: "Good wind with power, send me to Qingtian" In this culture, people learn only the trend of the trend, focus on capturing any opportunity to fly Huang Tengda, and will not work hard. And all, this is a project manager I know, I have learned these, I have the conditions necessary to form an excellent, cohesive core team. As a manager: You must learn to lead, believe in your own premonition, build the soul of the team, Training a nose that can identify lies.
Is salary management really use "the lowest human capital" to buy the "highest business performance" code? Is it true that the workforce of the work is really like a product in the marketing market? Of course, it ignores the following three questions: First, the labor is a special product, and it takes care of the people in the price tag. Second, people who provide labor to pursue a wage that is considered to be costly by the boss, and there is a happy career life. Third, every employee wants to share the company's business performance with the boss, because it is soaked in their emotions. If you ignore the emotions of employees in the pay management, you will count on the staff love their work. As a result, the labor relations becomes a trading relationship. On the other, it is a bargain, the kg is more than two, and there is a less porn. It is in a shortcoming, the interests, each has a picture, and it is like a vegetable food. Therefore, people-oriented remuneration management will pay attention to employee emotional needs, will use "Performance Sharing" as the theme of compensation management. Therefore, labor relations have become partnerships, the interests are connected, and the goals are consistent.
- 聽聽 聽聽 聽聽 聽聽 聽聽
Software development is a complex, creative collaborative game. As a game, it naturally has fun, so the programmer will not be tired, before the servant. First, this happiness originated in a joy of creating things. Second, this happiness comes from a sense of satisfaction that has developed something that is useful for others. Third, in the process of developing, it is the charming charm of the effect of the software that is pre-envisioned by the software. Fourth, happy sources continue to learn from the development process. Finally, the happiness source is self-developing, we can use the poets, just brought the happiness brought by our own castle. The programming is exclusive that it not only meets the desire of our inner depths, but also awakens the emotions of everyone. Unfortunately, the same as a game is also distressed: First, distress from pursuing perfectionism. Second, distress from others to set the goal, supply resources, and provide information. Third, distress comes from finding trivial bugs is a boring, repetitive activity. Fourth, people usually hope that when the project is close to the end, it can converge quickly, however, the closer is closer, the slower convergence. Finally, the distress comes from being invested in a lot of hard work, but the product is facing the danger of ignorant time. As a software developer, we have no choice, only to adapt to them, just face each day. Only 25% of the information from the leadership are known and correctly understood, from the lower feedback information, the information of equal communication can reach more than 90%. Equality to create trust, trust in promotion. Effectively conduct appropriate opinions exchange, will have a beneficial and positive impact on an organization's climate and productivity. It is the key to the market to make customers satisfaction and communicate with them.
- Guided from "Management Phase"
Management is a control game, in front of the game, you only have two options: or you are confident that you can 蠃, so we put enough energy to get everything; or you don't make this game, give up it. However, as a software project manager, you should also know that early investment, high risk will have a high return. Escape risk is fatal, because this will not have the interests of the risk, for a long time, you will face the danger of being eliminated by the market. The risk is "the possibility of losses", consisting of conditions, results, and surroundings. The difference between risks and problems is that risk is a problem that has not yet happened, and the problem is that the industry is also true risks. Yesterday's risk may be today's problem. Risk management mainly includes the following aspects:
First, risk recognition:
Patter a variety of risks from the mind imaging and screening, plus continuous risk discovery mechanisms throughout the development process to discover new risks.
Second, risk analysis:
Quantitative analysis of the likelihood and potential hazard of risk.
Third, emergency plan:
If you identify the risks, you will take emergency measures.
Fourth, risk mitigation:
In order to enable the emergency plan to be effectively implemented, the measures taken before risk transformation are true.
Fifth, continuous monitoring:
Tracking the risk of management, looking for signs of risk.
Some of the risks facing projects may be fatal, and the project will be severely lagged behind or directly discarded. Such risks are most managed, but effective management may make you conflicts with your superiors (such as time limit, for this type of risk, often exceeding your management, you can first column Assign the risk for the project, then turn them to the upper level to manage. Risk may come from technology, political, economic, resources, or other aspects, almost all, and will cause catastrophic consequences for project development, market share or reach project objectives (such as progress, budget, quality, etc.). However, in all software projects, five core risks are usually coexist, respectively, respectively:
First, lack of reasonable progress arrangements This is the most important reason that leads to the lag of the project. First, it stems from the optimism spirit that developers generally exists, we always look forward to not encountering difficulties in the implementation process, but our idea is defective, so the BUG will always be found. Second, it originated from a wrong understanding, the number of people, the number of people can be interchangeable, both of the number of people who have two times will complete the development work in half time. However, this theory is ignored with the increase in the number of people, and the corresponding burden on newcomers and people exchangers are also exchanged. In addition, there is also the burden of the task redistribution, as AliStair Cockburn Said: "The most effective way to communicate is facing" "When 3,5 people are easy to do this communication method, with the growth of the number, it is difficult to do this. The increase in communication costs and the increase in the cost of training newcomers, and the increase in task redistribution results in an increase in the cost of work interruption, which directly leads to a result: increasing people in projects behind the progress, will only make progress behind the progress.
Third, from an unprecedented estimate, managers, particularly high-level management, to meet the unreasonable progress arrangements caused by customers expectations. If the assigned time is not enough, no matter how scared the high-level leadership threat, work can not be completed on time. If people detect that managers may abuse their power to punish themselves, they will feel threatening, no sense of security. The lack of security will make people object to change, and in all successful projects, the change is one of the only elements, unless they are safe, otherwise people will not meet changes, will only follow the class, so often lose a lot The shortcomings of shortcuts, and these opportunities can originally reduce time progress. Fourth, if you don't care about the size of the product, then the progress you expect is that the air building Pavilion, the only basis is just your hopes. When estimating the size of the product, in addition to the normal time calculation, it should be added to the work of "may need to do", but also add some "may not need to do" things. The overall period of the project should not be attributed to the use of developers' inefficiencies.
Finally, the project's lag is not caused by a sudden cause, but there is no way to have a few days, but there is no way to take a day. The adverse reactions of the senior manager will definitely suppress the complete disclosure of information; instead, carefully distinguish the status report, no panicked, will not suppress the sub-level, will encourage honest progress, and this will make you in the first Master the actual progress in a time, grasp the charm, and make the right revision, so that the endlessness is helpless when you get these actual information. In addition, a reasonable schedule can also be set in project management and a challenging expected target completion time. It is expected that the target and reasonable progress are different. The desired target completion time can be set as the date of the project completed at the time of about 30%, which is very challenging, but it is not possible to force the desired goal. After all, reasonable progress arrangements are more reasonable for schedule. In addition, it is important to indicate that modern agile methodology has improved, such as XP (extreme programming), using the user material and the CRC card, the priority is divided and rapid increment iterative development, for the original development of the product or The function amount completed by the prototype after the first iteration, to calculate the function point, to estimate the function point of each CRC card, to obtain a total functional point to derive a relatively accurate progress arrangement.
Second, changes in demand
From the perspective of the project, demand always changes toward the direction of expansion. Even some things that have been done is also an expansion because it adds workload. Developers deliver users satisfaction, not just actual products, and the actual needs of users will vary with the construction and use of programs. To know, a living software must face changes, only if the dead software does not have a demand change (no one is used), we should face reality as soon as possible, not escape, in advance for them. Change is a good thing is not a bad thing. Similarly, modern agile methodology emphasizes a rapid response to demand changes, such as XP (extreme programming), using rapid increment iteration development, to develop functionally enhanced prototype software to users to quickly respond quickly Demand changes. Third, the change of personnel
In our somewhat managers, it is always assumed that developers can be replaced, and new employees can replace the old employees who are leaving, how stupid assumptions are. The maximum impact of dismissal employee or high employee replacement rate is to make the software item lose continuity. This is in the team culture holding this hypothesis, a large number of employees will leave when the project is processed, and the new employee often takes 1 to 3 months of the up time. During this time, what they can't do, There is also often the help of other old employees, thereby wasting a lot of other unnecessary time, leading to the progress of the project slower, and finally cause a lot of projects.
In addition, there is a phenomenon in China's software career, and when a project is being in progress, another project is caused by the reasons such as the forward or last deadline, and the senior manager will take someone from your team. To another project. This method of removing the Wall of the Western Wall is often the result of the two projects. Interchangeable error assumption. Blind believes that after investing a large number of people, newcomers will immediately put into new work so that the time required for project development will be shortened. In this organizational culture, it will not form a stable team. The members will only be busy with their own walls or make the walls of others, act as the role of firefighters, there are fires with fire. Mage.
Similarly, modern agile methodology is very concerned with people's ability, such as the power decentralization, coach role, and combines teams to form a strong team, so because there is a cohesive force, so Few of the big people change, they can often complete the tasks that can be completed twice the number of people. Very small teams can produce very large material productivity, sometimes, small teams can create miracles in a short period of time, and large teams can do very little. However, the small team tend to have enough policy support, causing the team to overcompass, which is caused by a pathological organizational culture. As a manager, it must be clear that it has a stable, cohesive development team is the largest wealth of the organization, not obstacles.
Fourth, the statute collapse
This situation has only two results: either, or does not happen, there will be no different levels of impact. But it really happens, it will directly destroy your entire project. At the beginning of the project, the parties need to identify the scope of demand through a series of discussions, and the collapse of the statute refers to the crash of this negotiation process. During the discussion, many times when you encounter a serious conflict, because both parties are reluctant to make, but do not want to give up this project, resulting in these conflicts to be covered. The final project moved towards a defective, unclear goal, and the problem covered is temporarily not bother you, but not forever. Although you can include a product, but you can't contain a mixed construction of a product. Therefore, eventually these issues will occur in the advanced period of the project, when most or even all budget times and money have been paid, at this time, any party is no longer fully supported, Both will be canceled. The vague marks in any specification documentation have unresolved conflicts between different system participants. As long as there are multiple participants during the development process, there must be conflict. Negotiation is easy to mediate, if the interests of the two people are completely or partially revered, pre-arranged, ready to address conflicts through mediation. Similarly, modern agile methodology has been discovered and avoided as soon as possible through the active participation of customers. Fifth, low efficiency
For project success, the quality of the project personnel, the organization and management of personnel is more important than the tools used by the tools or the technical methods used. Team quality is the biggest decision factor in the success of the project, the attention of people, incentives and cultivation are better than everything. The duties of the project management are not to work, but give people the possibility of creating work. Creativity comes from individuals, rather than organizational architectures and processes, and the central issue facing the project manager is how to design architectures and processes, and rather increase rather than suppressing people's initiative and creativity. Through the downward delegation of power, thereby producing improved quality, improved productivity, high morale, so that the authority of the center is actually strengthened. For overall, organizations will be more harmonious and prosperous. Increasing overtime time will only reduce productivity, people under pressure can not think more quickly, will also reduce productivity. The real reason for using pressure and overtime is to make people look good when the project fails.
The formal process improvement procedure requires money, spend time, and the specific process improvement work will delay the progress of the project, although it will eventually reflect the harvest of productive power, they can't disappoint the time of the process improvement. A variety of technologies improved procedures (such as CMM level) It is likely to make projects to complete these procedures, and the standard process will create enough work for excess people for excess people, so that everyone is busy. Not stop, although many are useless, this also results in low productivity. The team of personnel tends to productivity, because their team internal coupling is improved, and the meeting time, duplication of labor and invalidation will increase. The ideal personnel arrangements are designed by the small core team in most of the project, and gradually add a large number of people in the final stage of development. If there is no way to reduce the debugging time, there is no way to make the project to complete in advance, but to reduce the debugging time, it needs to increase the design time required to increase the design, because most errors come from interface defects, before encoding The formal and perfect design is made, which can greatly reduce errors. Similarly, modern agile methodology adopts attention to people, rapid iteration development, self-organizing teams and advocacy sustainable development speeds to avoid running over fast, resulting in short-term behavior, resulting in crash, thus maintaining stability Productivity.
Essence is an unfair company's way to use the company, which allows employees to afford the responsibility of failure. The goal of successful companies should be in contrast: flourishing, developed, and humanized.
- Call from "deadline"
