Five core risks of software projects
- Congenital error
- Demand expansion (demand change)
- personnel loss
- Statute collapse
- low productivity
(This classification "and" chapter and bear-13 chapter ")
First, schedule error
The first of the five major risks, if this risk is encountered, you can say that you have encountered Mission Impossbile. You pray that your Team member is Tom. Cruz is good, but unfortunately, so many handsome super people, as long as the Tom in Tom and Jerry is very thankful.
The reason for this risk often has the following:
1. Estimate the product scale
Whether it is not seriously estimated product scale, or seriously estimates, it is still a problem for scale, in all, it is estimated to estimate the product scale. May have the following reasons to cause this problem
- Attitude
Doing anything is the biggest problem, a person who is not enthusiastic, even if there is a powerful thing. How to avoid the attitude issues in the budget, you need to estimate the responsibility of the project, your own interests and project hooks, whether direct economic interests are still in the future career.
The project budget is accurate, need to reward, and do not accurately, there must be punitive measures.
Of course, the success of a project is not completely related to the plan settlers, and the planned executor has a big relationship, so before planning, the formula is obliged and the executor will communicate more, and the project will be on the project. Failed to analyze to confirm the players between the plan settlers and planners.
-lack of experience
There are often too many unknown factors in the software project, new technology, new business areas, bring risks to the project. When encountering these new things, even if there is experienced project manager, there are different degrees of experience. How to avoid this problem, you need the project manager to encounter the problem that you are not familiar with, you need to help you to help it.
It is also very important to accumulate and share at the same time. In fact, the software industry has developed to now, and the real-new field is very small. Many times just have a new field for project managers or project groups, in other departments, project groups, and company outside the company often have a good solution. How to accumulate these experiences at this time (especially the company's internal) and it is easy to share to other people is a very important link.
- Insufficient information
To develop a good plan, there is naturally enough and useful information. Know yourself, can you do it better? Be good at discovering information from all aspects, from customers, end users, from sales, pre-sales, pre-sales, pre-sales, project team members, from corporate leaders, customer leaders, etc., even from newspapers, television and other media. In a word, you have a keen sense of smell.
2, estimate is correct, but because some other reasons are revised
Maybe you make a very correct estimate, but because some reasons have to be your plan in advance.
- customer willingness
This situation is very common, especially for some items that have a very sensitive on the line. For example, financial system is best online when a billing year begins. In addition, some projects have to be completed within the term of a big person.
In this case, the poor project manager has to race the brain to compress the time schedule, whether it is increasing human hand, reduced the function. But the two often bring great risks, the more people, the more complex communication within the project team, and the people who often add additional people are not the most suitable person, on this basis, the possibility of completion of the period is increasing The smaller, even if it can meet the progress, it will still be overdue in cost. The reduction feature can be approved by the user, but it is often recognized by the customer, and the end user does not recognize that it will encounter a lot of obstacles when the project is delivered, and the worst is that if you don't have a written confirmation. The originally recognized customers often deny their commitment. Try to communicate with our customers and companies, such projects are really evil dreams for the project manager, get the customer's recognition, more resources from the company, so maybe better
- Company willingness
Pure companies are rarely willing, generally in conjunction with customers. Still old, add more communication, responding to your own difficulties, thinking about enough reasons to persuade your boss.
- Team Willingness
Maybe you have encountered a very good team, everyone wants to complete the progress in advance, want to create a miracle (if you don't oppose the completion of the miracle, ^ _ ^), then you are lucky. But note, you are Team Leader, when everyone is very fanatics, you have to calm, you have to see that everyone can stay at night, overtime, you have to see the extension of time, enthusiasm Will retreat, formulate a plan that everyone can accept.
-personal preference
If this is you - the project manager's own will, no matter what kind of reason you come, for personal professional promotion, for the interests of the project group, I advise you to give up this idea. For the personal interests, you can never get a joke with the interests of the company and the team, or say that you are gambling with your own destiny, and don't have less. Even if you consider it is for team interests, let everyone know that the problem is rising as a team's will, and the solution will be seen.
Ok, you control your own, team, company, customer's desire, get adequate information, make a plan carefully, full of everything OK, but very unfortunate, the project is still extension, things are In constant changes, any budget you make is in the case of existing situations and forecasts, once the situation changes, the budget is inaccurate, so it is more appropriate to keep a certain buffer period. . According to the "Dancing" with the bear, the actual time of the project is 50% of the probability of 1.3 times the planning time.
