Difference between revisions of "Network Analysis of Interlocking Directorates/Project Management/Risk Assessment"

From Analytics Practicum
Jump to navigation Jump to search
Line 20: Line 20:
  
 
<!--Body-->
 
<!--Body-->
−
==<font face="Corbel"  color= #688e23 font-weight: bold size=5%>Risk Assessment Table==
+
==<font face="Corbel"  color= #8A740C font-weight: bold size=5%>Risk Assessment Table==
 
<font face="Corbel" size=3%>
 
<font face="Corbel" size=3%>
 
{| class="wikitable" style="margin: 1em auto 1em auto; text-align: center"
 
{| class="wikitable" style="margin: 1em auto 1em auto; text-align: center"
−
| align="center" style="background:#688e23; color:#ffffff"|'''S/N'''
+
| align="center" style="background:#8A740C; color:#ffffff"|'''S/N'''
−
| align="center" style="background:#688e23; color:#ffffff"|'''Risk Statement'''
+
| align="center" style="background:#8A740C; color:#ffffff"|'''Risk Statement'''
−
| align="center" style="background:#688e23; color:#ffffff"|'''Type of risk'''
+
| align="center" style="background:#8A740C; color:#ffffff"|'''Type of risk'''
−
| align="center" style="background:#688e23; color:#ffffff"|'''Likelihood (H/M/L)'''
+
| align="center" style="background:#8A740C; color:#ffffff"|'''Likelihood (H/M/L)'''
−
| align="center" style="background:#688e23; color:#ffffff"|'''Impact (H/M/L)'''
+
| align="center" style="background:#8A740C; color:#ffffff"|'''Impact (H/M/L)'''
−
| align="center" style="background:#688e23; color:#ffffff"|'''Risk Rating'''
+
| align="center" style="background:#8A740C; color:#ffffff"|'''Risk Rating'''
−
| align="center" style="background:#688e23; color:#ffffff"|'''Mitigation strategy/ Contingency Plan'''
+
| align="center" style="background:#8A740C; color:#ffffff"|'''Mitigation strategy/ Contingency Plan'''
 
|-
 
|-
−
| 1||Lack of knowledge regarding corporate structure||Non-Technical||Medium||Medium||Medium
+
| 1||Lack of knowledge regarding corporate structure||Non-Technical||Medium||Medium||bgcolor=#fffacd|Moderate
 
||
 
||
 
*Refer to research papers for previous research hypothesis & results.
 
*Refer to research papers for previous research hypothesis & results.
Line 37: Line 37:
 
|-
 
|-
 
|-
 
|-
−
| 2||Limitation on Data Extraction||Technical ||Medium||Medium||Medium||*Test different ways of doing it, and develop an iterative method to acquire data.
+
| 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.
 
|-
 
|-
 
| 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
Line 50: Line 51:
 
*Use different algorithm and decide the most appropriate method to acquire data and organise accordingly.
 
*Use different algorithm and decide the most appropriate method to acquire data and organise accordingly.
 
|-
 
|-
−
| 4||Schedule. Team members are busy with school work.||External ||Medium||Medium||bgcolor=#fffacd|Moderate|
+
| 4||Schedule. Team members are busy with school work.||Non-Technical||Medium||Medium||bgcolor=#fffacd|Moderate
−
|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.
 
|-
 
|-
 
|}
 
|}
 
</font>
 
</font>
 
<!--End Body-->
 
<!--End Body-->

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
  • 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
  • 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
  • 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
  • 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
  • Plan ahead and make sure that all team members are comfortable with the work load and free to meet on the dates scheduled.

Retrieved from ‘https://wiki.smu.edu.sg/ANLY482/index.php?title=Network_Analysis_of_Interlocking_Directorates/Project_Management/Risk_Assessment&oldid=1248’