Difference between revisions of "Network Analysis of Interlocking Directorates/Project Management/Risk Assessment"
Jump to navigation
Jump to search
Line 38: | Line 38: | ||
|- | |- | ||
| 2||Limitation on Data Extraction||Technical ||Medium||Medium||bgcolor=#fffacd|Moderate | | 2||Limitation on Data Extraction||Technical ||Medium||Medium||bgcolor=#fffacd|Moderate | ||
− | + | | align="left"| | |
*Test different ways of doing it, and develop an iterative method to acquire data. | *Test different ways of doing it, and develop an iterative method to acquire data. | ||
|- | |- | ||
| 3||Team is unfaimiliar with R-programming||Technical ||Medium||High||bgcolor=#f08080|High | | 3||Team is unfaimiliar with R-programming||Technical ||Medium||High||bgcolor=#f08080|High | ||
− | + | | align="left"| | |
*More research and learning should be done and shared within the team. | *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. | *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||bgcolor=#f08080|High | | 4||The network data may not be completed||Technical||High||High||bgcolor=#f08080|High | ||
− | + | | align="left"| | |
*Gather suitable data with appropriate size. | *Gather suitable data with appropriate size. | ||
*Iterative methodology of gathering data stages. | *Iterative methodology of gathering data stages. | ||
Line 53: | Line 53: | ||
|- | |- | ||
| 4||Schedule. Team members are busy with school work.||Non-Technical||Medium||Medium||bgcolor=#fffacd|Moderate | | 4||Schedule. Team members are busy with school work.||Non-Technical||Medium||Medium||bgcolor=#fffacd|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. | *Plan ahead and make sure that all team members are comfortable with the work load and free to meet on the dates scheduled. | ||
|- | |- |
Revision as of 21:22, 23 January 2015
Home | Project Overview | Findings & Insights | Project Management | Project Documentation | Learning Outcomes |
Project Plan | Metrics | Risk Assessment |
Risk Assessment Table
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 |
|
2 | Limitation on Data Extraction | Technical | Medium | Medium | Moderate |
|
3 | Team is unfaimiliar with R-programming | Technical | Medium | High | High |
|
4 | The network data may not be completed | Technical | High | High | High |
|
4 | Schedule. Team members are busy with school work. | Non-Technical | Medium | Medium | Moderate |
|