1. Demand risk
Demand has become the benchmark of the project, but it continues to change; Poor definition of requirements, further definition will expand the scope of the project; Add additional requirements; The vague part of product definition takes more time than expected; Insufficient demand for customer participation; Lack of effective requirements change management process.
2. Planning risks
Plans, resources and product definitions are all based on verbal instructions from customers or upper-level leaders, which are not completely consistent; The scheme is optimized, which is the "best state", but the scheme is unrealistic and can only be regarded as the "expected state";
Planning is based on the use of a specific team member, and that specific team member can't actually count on it; The product scale (the percentage of code lines, function points and previous product scale) is larger than estimated; The completion target date is advanced, but the product scope or available resources have not been adjusted accordingly; Getting involved in unfamiliar product fields takes more time than expected in design and implementation.
3. Organize and manage risks
Only management or marketing personnel make technical decisions, which leads to slow planning progress and prolonged planning time; Inefficient project team structure reduces productivity; The management took longer than expected to review the decision; Cut the budget and disrupt the project plan; The management decided not to encourage the project organization;
Lack of necessary norms leads to work mistakes and repeated work; Working hours of non-technical third parties (budget approval, equipment procurement approval, legal review, security, etc. ) It took longer than expected.
4. Personnel risks
Tasks that are prerequisites (such as training and other projects) cannot be completed on time; Poor relationship between developers and management leads to slow decision-making and affects the overall situation; Lack of incentives, low morale and reduced production capacity; Some people need more time to adapt to unfamiliar software tools and environments; In the later stage of the project, it is necessary to train new developers and gradually communicate with existing members, which reduces the work efficiency of existing members;
Conflicts among project team members lead to poor communication, poor design, interface errors and extra repetitive work; The members who didn't adapt to the work didn't leave the project team, which affected the enthusiasm of other members of the project team; ⑧ No personnel with specific skills urgently needed by the project were found.
5. Environmental risks in development
Facilities are not in place in time; Although the facilities of the project managers' alliance exist, they are not matched, such as no telephone, network cable and office supplies; The facilities are crowded, messy or damaged;
Development tools are not in place in time; Development tools are not as effective as expected, and developers need time to create a working environment or switch to new tools; The learning cycle of the newly developed tools is longer than expected, and there are many contents.