| S/N
|
Risk Statement
|
Type of risk
|
Likelihood (H/M/L)
|
Impact (H/M/L)
|
Risk Rating
|
Mitigation Strategy
|
| 1 |
Lack of knowledge regarding corporate structure |
Non-Technical |
Medium |
Medium |
Moderate
|
- Refer to research papers for previous research hypothesis & results.
- Regular consultation to clarify if there is any doubt.
|
| 2 |
Limitation on Data Extraction |
Technical |
Medium |
Medium |
Moderate
|
align="left"|
- Test different ways of doing it, and develop an iterative method to acquire data.
|
| 3 |
Team is unfaimiliar with R-programming |
Technical |
Medium |
High |
High
|
align="left"|
- More research and learning should be done and shared within the team.
- If necessary, re-confirm the priority and revise project plan to get more time learning before applying the technology.
|
| 4 |
The network data may not be completed |
Technical |
High |
High |
High
|
align="left"|
- Gather suitable data with appropriate size.
- Iterative methodology of gathering data stages.
- Use different algorithm and decide the most appropriate method to acquire data and organise accordingly.
|
| 4 |
Schedule. Team members are busy with school work. |
Non-Technical |
Medium |
Medium |
Moderate
|
align="left"|
- Plan ahead and make sure that all team members are comfortable with the work load and free to meet on the dates scheduled.
|
