Difference between revisions of "Network Analysis of Interlocking Directorates/Project Management/Risk Assessment"
Jump to navigation
Jump to search
Line 37: | Line 37: | ||
|- | |- | ||
|- | |- | ||
− | | 2||Limitation on Data Extraction||Technical ||Medium||Medium||bgcolor=#fffacd|Moderate | + | | 2||Limitation on Data Extraction||Technical ||Medium||Medium||bgcolor=#fffacd|Moderate|| |
*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. | ||
|- | |- |
Revision as of 21:16, 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/ Contingency Plan |
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 |
|