Code

Risk factors

Description

K₁

Analysis risk of product design

System analysts don’t perform feasibility analysis which leads to biases.

K₂

Requirements change risk

Business department always raises new requirements or changes previous requirements, which leads to expanding project.

K₃

Technology change risk

Change technology because previous design cannot meet requirements, it may have an impact on development progress.

K₄

Software quality risk

Testers failed to find bugs duo to carelessness, there might be a problem after publishing software.

K₅

Communication risk

Communication mechanism doesn’t work across project teams.

K₆

Schedule risk

Failed to finish the project on schedule

K₇

Software release risk

Release plan faces problems because technology cannot support it or released software has a side effect on online business.

K₈

Project management risk

System of mechanism, progress and emergency management is incomplete.

K₉

Human resources risk

Employees especially technical experts run off.

K₁₀

Decision making risk

Make wrong decisions or failed to make decisions in time.