Team Project Risk Analysis

I. Risk of personnel

1, the team members are not interested in their own projects, development enthusiasm is low, and thus unable to achieve the required product function and performance requirements;

2. Lack of development experience and basic development basis (language, experience, tools, etc.);

3, before the end of the project, team members for various reasons to quit;

4, the team members because of long-term coexistence caused many development and life conflicts, resulting in project failure;

5, the negative team members did not transfer the project team in time, affecting the enthusiasm of other members;

6. The assignment of tasks is unreasonable;

7, the project management personnel lack of capacity;

Second, process risk

1, the project progress tracking is not accurate, resulting in the plan to keep up with changes;

2, the early work is not in place, leading to late development bottlenecks;

3, the development period did not follow the standards, resulting in project quality issues;

4, risk management analysis is insufficient, resulting in no more significant project risks found;

III. Development of environmental risks

1, development tools are not ready;

2, development tools than expected to force, developers need more time to know, learn the use of development tools;

4, the choice of development tools is not reasonable;

Iv. End-User risk

1, the end user constantly change the demand;

2, the end-user of the final delivery of the product is not satisfied, not to follow-up investment projects;

3, the end user's opinion has not been adopted, resulting in the product can not meet user requirements;

V. Design and implementation of risks

1, the design is too simple, the development does not have the corresponding function;

2, the design is too complex, leading to do some work hard, affecting efficiency;

3, design quality is low, need to re-come.

Team Project Risk Analysis