"Thirsty" project risk

I. Risk of personnel

1, the project team members of poor cooperative relations led to slow decision-making, the impact of the overall

2, the project team members did not devote themselves to the project, and therefore unable to achieve the required product function and performance requirements

3, lack of incentive measures, low morale, reduce production capacity

4, lack of necessary norms, increase work errors, duplication of work, reduce the quality of work lack of work basis (language, experience, tools, etc.)

5. Members of the project team leave the project team before the end of the project

6, the project team members can not effectively work together, due to the conflict between team members, resulting in poor communication, poorly designed, interface errors and additional duplication of work

7. Members of the project team who have problems are not removed from the project team, affecting the enthusiasm of other members

8. Assignment of tasks and personnel skills mismatch

9, the project management personnel to make the plan and progress failure

10, technical staff to do the job omission, poor quality, work needs to be re-

Second, process risk

1, tracking inaccurate, resulting in unpredictable project progress is lagging behind the plan

2, the early quality assurance behavior is not true, resulting in the late repetitive work

3, quality tracking is not accurate, resulting in the failure to know the quality of the progress of the problem

4, can not effectively follow the standards, resulting in insufficient communication, quality problems and duplication of work

5, risk management careless, resulting in no significant project risks found

III. Development of environmental risks

1, development tools are not in place in time

2. Development tools are not as effective as expected, developers need more time, or change tools

3. The learning period of development tools is longer than expected

4, the choice of development tools is not based on technical requirements, can not provide planning requirements of the function

Iv. End-User risk

1. End users adhere to new requirements

2, the end user is not satisfied with the final delivery of the product, the need to redesign and re-do the end-user does not buy project products, can not provide follow-up support

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

V. Design and implementation of risks

1, design is too simple, consider not careful, not comprehensive, resulting in re-design and implementation

2, the design is too complex, resulting in some unnecessary work, affecting efficiency

3, the design of low quality, resulting in the redesign and implementation of the use of unfamiliar methods, resulting in the need for additional training time

4, the product uses the low-level language to write, causes the efficiency is low

5, the modules developed separately can not be effectively integrated, need to redesign and implement

"Thirsty" project risk