HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2018T1 analyteaka riskmanagement"

From IS480
Jump to navigation Jump to search
 
(6 intermediate revisions by 2 users not shown)
Line 11: Line 11:
  
 
| style="padding:0.1em; font-size:100%; background-color:#7D5B53; text-align:center; color:#F5F5F5" width="10%" |  
 
| style="padding:0.1em; font-size:100%; background-color:#7D5B53; text-align:center; color:#F5F5F5" width="10%" |  
[[IS480 Team wiki: 2017T1 analyteaka About Us |<font color="#F5F5F5" size=2.5 family ="Century Gothic"><b>ABOUT US</b></font>]]
+
[[IS480 Team wiki: 2018T1 analyteaka About Us |<font color="#F5F5F5" size=2.5 family ="Century Gothic"><b>ABOUT US</b></font>]]
  
 
| style="padding:0.1em; font-size:100%; background-color:#7D5B53; text-align:center; color:#F5F5F5" width="10%" |  
 
| style="padding:0.1em; font-size:100%; background-color:#7D5B53; text-align:center; color:#F5F5F5" width="10%" |  
[[IS480 Team wiki: 2017T1 analyteaka ProjectOverview Description |<font color="#F5F5F5" size=2.5 family ="Century Gothic"><b>PROJECT OVERVIEW</b></font>]]
+
[[IS480 Team wiki: 2018T1 analyteaka ProjectOverview Description |<font color="#F5F5F5" size=2.5 family ="Century Gothic"><b>PROJECT OVERVIEW</b></font>]]
  
 
| style="padding:0.1em; font-size:100%; background-color:#96766F; text-align:center; color:#F5F5F5" width="10%" |  
 
| style="padding:0.1em; font-size:100%; background-color:#96766F; text-align:center; color:#F5F5F5" width="10%" |  
[[IS480 Team wiki: 2017T1 analyteaka ProjectManagement Schedule |<font color="#F5F5F5" size=2.5 family ="Century Gothic"><b>PROJECT MANAGEMENT</b></font>]]
+
[[IS480 Team wiki: 2018T1 analyteaka ProjectManagement Schedule |<font color="#F5F5F5" size=2.5 family ="Century Gothic"><b>PROJECT MANAGEMENT</b></font>]]
  
 
| style="padding:0.1em; font-size:100%; background-color:#7D5B53; text-align:center; color:#F5F5F5" width="10%" |  
 
| style="padding:0.1em; font-size:100%; background-color:#7D5B53; text-align:center; color:#F5F5F5" width="10%" |  
[[IS480 Team wiki: 2017T1 analyteaka Documentation |<font color="#F5F5F5" size=2.5 family="Century Gothic"><b>DOCUMENTATION</b></font>]]
+
[[IS480 Team wiki: 2018T1 analyteaka Documentation |<font color="#F5F5F5" size=2.5 family="Century Gothic"><b>DOCUMENTATION</b></font>]]
 
|}
 
|}
 
<!--/MENU-->
 
<!--/MENU-->
Line 28: Line 28:
 
<!--SUB MENU-->
 
<!--SUB MENU-->
 
{| class="wikitable;style="background-color:white; color:white padding: 5px 0 0 0;" width="100%" height=50px cellspacing="0" cellpadding="0" valign="top" border="0"  
 
{| class="wikitable;style="background-color:white; color:white padding: 5px 0 0 0;" width="100%" height=50px cellspacing="0" cellpadding="0" valign="top" border="0"  
| style="vertical-align:top;width:25%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:1px">[[IS480 Team wiki: 2017T1 analyteaka ProjectManagement Schedule | <font color="#35332E"><b>PROJECT SCHEDULE</b></font>]]  
+
| style="vertical-align:top;width:25%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:1px">[[IS480 Team wiki: 2018T1 analyteaka ProjectManagement Schedule | <font color="#35332E"><b>PROJECT SCHEDULE</b></font>]]  
 
| style="vertical-align:top;width:25%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:1px"> [[IS480_Team_wiki:_2018T1_ analyteaka_metrics | <font color="#35332E"><b>METRICS</b></font>]]  
 
| style="vertical-align:top;width:25%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:1px"> [[IS480_Team_wiki:_2018T1_ analyteaka_metrics | <font color="#35332E"><b>METRICS</b></font>]]  
 
| style="vertical-align:top;width:25%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:3px solid #7D5B53; "> [[IS480_Team_wiki:_2018T1_ analyteaka_riskmanagement | <font color="#35332E"><b>RISK MANAGEMENT</b></font>]]  
 
| style="vertical-align:top;width:25%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:3px solid #7D5B53; "> [[IS480_Team_wiki:_2018T1_ analyteaka_riskmanagement | <font color="#35332E"><b>RISK MANAGEMENT</b></font>]]  
Line 38: Line 38:
  
 
<!--CONTENT-->
 
<!--CONTENT-->
 +
[[File:Analyteaka_Risk_Impact_Assessment.png|1000px|center]]
 +
 +
The risk impact assessment requires the team members to consider the impact of each risk across the various project objective areas. Based on this potential impact, the risk is assigned to one of the 5 identified scales below. 
 +
 +
{| class="wikitable" style="font:Century Gothic; background-color:#FFFFFF; width: 1000px;" align="center"
 +
|-
 +
<!--!colspan="6" style="color:#ffffff; background-color:#7D5B53;" width="50pt" | Definition of Impact Scales
 +
|-
 +
-->
 +
!rowspan="2" style="color:#ffffff; background-color:#7D5B53;" width="100pt" | Project Objective
 +
!colspan="5" style="color:#ffffff; background-color:#7D5B53;" width="50pt" | Relative/Numerical Scales
 +
|-
 +
! style="color:#7D5B53; background-color:#ffffff;"  | Very Low / 0.05
 +
! style="color:#7D5B53; background-color:#ffffff;"  | Low / 0.10
 +
! style="color:#7D5B53; background-color:#ffffff;"  | Moderate / 0.20
 +
! style="color:#7D5B53; background-color:#ffffff;"  | High / 0.40
 +
! style="color:#7D5B53; background-color:#ffffff;"  | Very High / 0.80
 +
|-
 +
 +
!style="color:#7D5B53; text-align: center; background-color:#ffffff;"| Time
 +
|style="text-align: center; background-color:#ffffff;"| Insignificant time increase
 +
|style="text-align: center; background-color:#ffffff;"| < 5%-time increase
 +
|style="text-align: center; background-color:#ffffff;"| 5% – 10%-time increase
 +
|style="text-align: center; background-color:#ffffff;"| 10% - 20%-time increase
 +
|style="text-align: center; background-color:#ffffff;"| >20% time increase
 +
|-
 +
 +
!style="color:#7D5B53; text-align: center; background-color:#ffffff;"| Scope
 +
|style="text-align: center; background-color:#ffffff;"| Insignificant scope decrease
 +
|style="text-align: center; background-color:#ffffff;"| Minor scoping areas affected
 +
|style="text-align: center; background-color:#ffffff;"| Major scoping areas affected
 +
|style="text-align: center; background-color:#ffffff;"| Scope reduction unacceptable to sponsor
 +
|style="text-align: center; background-color:#ffffff;"| Project end item is effectively useless
 +
|-
 +
 +
!style="color:#7D5B53; text-align: center; background-color:#ffffff;"| Quality
 +
|style="text-align: center; background-color:#ffffff;"| Insignificant quality degradation
 +
|style="text-align: center; background-color:#ffffff;"| Only very demanding applications are affected
 +
|style="text-align: center; background-color:#ffffff;"| Quality reduction requires sponsor approval
 +
|style="text-align: center; background-color:#ffffff;"| Quality reduction unacceptable to sponsor
 +
|style="text-align: center; background-color:#ffffff;"| Project end item is effectively useless
 +
|-
 +
|}
 +
 
[[File:Analyteaka_Risk_Probability.png|1000px|center]]
 
[[File:Analyteaka_Risk_Probability.png|1000px|center]]
 
By taking into consideration the estimated probability of occurrence as well as the potential impact from the risk impact assessment, a quantitative impact measure is obtained. Based on the team and clients risk threshold and appetite, the measures will be grouped and the appropriate action to be taken will be identified.  
 
By taking into consideration the estimated probability of occurrence as well as the potential impact from the risk impact assessment, a quantitative impact measure is obtained. Based on the team and clients risk threshold and appetite, the measures will be grouped and the appropriate action to be taken will be identified.  
Line 51: Line 95:
 
|-
 
|-
  
|style="text-align: center; background-color:#ffffff;"| 0.05
+
! style="color:#7D5B53; background-color:#ffffff;"| 0.05
|style="text-align: center; background-color:#ffffff;" | 0.10
+
! style="color:#7D5B53; background-color:#ffffff;" | 0.10
|style="text-align: center; background-color:#ffffff;" | 0.20
+
! style="color:#7D5B53; background-color:#ffffff;" | 0.20
|style="text-align: center; background-color:#ffffff;" | 0.40
+
! style="color:#7D5B53; background-color:#ffffff;" | 0.40
|style="text-align: center; background-color:#ffffff;" | 0.80
+
! style="color:#7D5B53; background-color:#ffffff;" | 0.80
 
|-
 
|-
  
|style="text-align: center; background-color:#ffffff;"| 0.90
+
! style="color:#7D5B53; background-color:#ffffff;"| 0.90
 
|style="text-align: center; background-color:#6eba66;"| 0.05
 
|style="text-align: center; background-color:#6eba66;"| 0.05
 
|style="text-align: center; background-color:#ffca16;"| 0.09
 
|style="text-align: center; background-color:#ffca16;"| 0.09
Line 66: Line 110:
 
|-
 
|-
  
|style="text-align: center; background-color:#ffffff;"| 0.70
+
! style="color:#7D5B53; background-color:#ffffff;"| 0.70
 
|style="text-align: center; background-color:#6eba66;"| 0.04
 
|style="text-align: center; background-color:#6eba66;"| 0.04
 
|style="text-align: center; background-color:#6eba66;"| 0.07
 
|style="text-align: center; background-color:#6eba66;"| 0.07
Line 74: Line 118:
 
|-
 
|-
  
|style="text-align: center; background-color:#ffffff;"| 0.50
+
! style="color:#7D5B53; background-color:#ffffff;"| 0.50
 
|style="text-align: center; background-color:#6eba66;"| 0.03
 
|style="text-align: center; background-color:#6eba66;"| 0.03
 
|style="text-align: center; background-color:#6eba66;"| 0.05
 
|style="text-align: center; background-color:#6eba66;"| 0.05
Line 82: Line 126:
 
|-
 
|-
  
|style="text-align: center; background-color:#ffffff;"| 0.30
+
! style="color:#7D5B53; background-color:#ffffff;"| 0.30
 
|style="text-align: center; background-color:#6eba66;"| 0.02
 
|style="text-align: center; background-color:#6eba66;"| 0.02
 
|style="text-align: center; background-color:#6eba66;"| 0.03
 
|style="text-align: center; background-color:#6eba66;"| 0.03
Line 90: Line 134:
 
|-
 
|-
  
|style="text-align: center; background-color:#ffffff;"| 0.10
+
! style="color:#7D5B53; background-color:#ffffff;"| 0.10
 
|style="text-align: center; background-color:#6eba66;"| 0.01
 
|style="text-align: center; background-color:#6eba66;"| 0.01
 
|style="text-align: center; background-color:#6eba66;"| 0.01
 
|style="text-align: center; background-color:#6eba66;"| 0.01
Line 125: Line 169:
 
|style="text-align: center;"| 1
 
|style="text-align: center;"| 1
 
|style="text-align: center;"| Technical Risk
 
|style="text-align: center;"| Technical Risk
|style="text-align: center;"| Majority of our team is not proficient in python, google app engine, flask and machine learning.
+
|style="text-align: center;"| Majority of our team is not proficient in python, google app engine, flask and machine learning. (Resolved)
 
|style="text-align: left;"| Spent time going through bootcamp training for python and machine learning to build on our foundation. We will also take various modules such as visual analytics, AA, EWS and networking to build on our competency.
 
|style="text-align: left;"| Spent time going through bootcamp training for python and machine learning to build on our foundation. We will also take various modules such as visual analytics, AA, EWS and networking to build on our competency.
|style="text-align: center;"| High - 0.9
+
|style="text-align: center;"| Very High - 0.9
 
|style="text-align: center;"| Very high - Potential delay in the schedule due to production delay.  
 
|style="text-align: center;"| Very high - Potential delay in the schedule due to production delay.  
 
|style="text-align: center;"| Active Management
 
|style="text-align: center;"| Active Management
Line 134: Line 178:
 
|style="text-align: center;"| 2
 
|style="text-align: center;"| 2
 
|style="text-align: center;"| Resource Management Risk
 
|style="text-align: center;"| Resource Management Risk
|style="text-align: center;"| Most of the team are not well-versed in analytics, which is the core feature of our system. As well as limited knowledge on consumer behavior and digital marketing.  
+
|style="text-align: center;"| Most of the team are not well-versed in analytics, which is the core feature of our system. As well as limited knowledge on consumer behavior and digital marketing. (Resolved)
 
|style="text-align: left;"| Spent time going through bootcamp training for analytics and consult professors on analytics. Also take courses related to digital marketing and consumer behavior.
 
|style="text-align: left;"| Spent time going through bootcamp training for analytics and consult professors on analytics. Also take courses related to digital marketing and consumer behavior.
|style="text-align: center;"| High - 0.9
+
|style="text-align: center;"| High - 0.8
 
|style="text-align: center;"| High - Could affect our production timeline and analytics result.
 
|style="text-align: center;"| High - Could affect our production timeline and analytics result.
 
|style="text-align: center;"| Active Management
 
|style="text-align: center;"| Active Management
Line 143: Line 187:
 
|style="text-align: center;"| 3
 
|style="text-align: center;"| 3
 
|style="text-align: center;"| Human Risk
 
|style="text-align: center;"| Human Risk
|style="text-align: center;"| Potential schedule clash due to the different in class timetable. Additionally, FYP with internship concurrently means we could only work on our project at night and during the weekends.  
+
|style="text-align: center;"| Potential schedule clash due to the different in class timetable. Additionally, FYP with internship concurrently means we could only work on our project at night and during the weekends. (Resolved)
 
|style="text-align: left;"| Project manager to better plan the schedule. Ensuring that everyone will have a common free slot for work (e.g 1 day block slot every week)
 
|style="text-align: left;"| Project manager to better plan the schedule. Ensuring that everyone will have a common free slot for work (e.g 1 day block slot every week)
 
|style="text-align: center;"| Medium - 0.5
 
|style="text-align: center;"| Medium - 0.5
Line 152: Line 196:
 
|style="text-align: center;"| 4
 
|style="text-align: center;"| 4
 
|style="text-align: center;"| Client Management Risk
 
|style="text-align: center;"| Client Management Risk
|style="text-align: center;"| Client unable to provide csv containing sensitive data (NRIC, name) due to privacy compliances
+
|style="text-align: center;"| Client unable to provide csv containing sensitive data (NRIC, name) due to privacy compliances (Resolved)
 
|style="text-align: left;"| Discuss with clients and capture what we need during bootstrap stage (e.g determine age, gender and race) and hash the values such that we can still analyze it without having access or storing the raw csv file.
 
|style="text-align: left;"| Discuss with clients and capture what we need during bootstrap stage (e.g determine age, gender and race) and hash the values such that we can still analyze it without having access or storing the raw csv file.
 
|style="text-align: center;"| Medium - 0.3
 
|style="text-align: center;"| Medium - 0.3
Line 160: Line 204:
  
 
|style="text-align: center;"| 5
 
|style="text-align: center;"| 5
|style="text-align: center;"| Client Management Risk
+
|style="text-align: center;"| Technical Risk
|style="text-align: center;"| Employees may not comfortable with using technology and figuring out how the application works.
+
|style="text-align: center;"| PDPA changes might affect the way our application is design and structured. (Resolved)
|style="text-align: left;"| We will conduct adequate research into scenarios and personas, multiple rounds of prototyping with sufficient client feedback. Additionally, run through a tutorial during the first launch to highlight the importance of the features and use of the application. As well as getting the support of the upper management.  
+
|style="text-align: left;"| Very high - Potential delay in the schedule due to production delay.  
|style="text-align: center;"| Medium - 0.3
+
|style="text-align: center;"| High - 0.8
|style="text-align: center;"| Low - Potential lack of adoption.  
+
|style="text-align: center;"| To structure the database with bare minimum personal data inside the database. This is to ensure in the event of PDPA regulation change we will have bare minimum requirement change. Even though, we are likely not going to get affected by the regulation during the few months of development, we have to ensure the application will last without need the need to change.
|style="text-align: center;"| Conditional Management
+
|style="text-align: center;"| Active management
 
|-
 
|-
  
|style="text-align: center;"| 6
+
 
|style="text-align: center;"| Human Risk
 
|style="text-align: center;"| Team members fall sick to the point(ie hospitalization).
 
|style="text-align: left;"| Always ensure that the wellbeing of the team members is preserved by encouraging healthy diet, exercise and work life balance. Additionally, conduct peer sharing sessions so that everyone is aware of what is being done by each other such that taking over will be easy in such situations.
 
|style="text-align: center;"| Low - 0.1
 
|style="text-align: center;"| Very low - contribution to project is affected
 
|style="text-align: center;"| Conditional Management
 
|-
 
 
|}
 
|}
 
</center>
 
</center>
 
[[File:Analyteaka_Footer_Transparent.png|1000px|center]]
 
[[File:Analyteaka_Footer_Transparent.png|1000px|center]]
 
<!--CONTENT-->
 
<!--CONTENT-->

Latest revision as of 21:55, 21 November 2018

Analyteaka Header.png


HOME

ABOUT US

PROJECT OVERVIEW

PROJECT MANAGEMENT

DOCUMENTATION



Analyteaka Risk Impact Assessment.png

The risk impact assessment requires the team members to consider the impact of each risk across the various project objective areas. Based on this potential impact, the risk is assigned to one of the 5 identified scales below. 

Project Objective Relative/Numerical Scales
Very Low / 0.05 Low / 0.10 Moderate / 0.20 High / 0.40 Very High / 0.80
Time Insignificant time increase < 5%-time increase 5% – 10%-time increase 10% - 20%-time increase >20% time increase
Scope Insignificant scope decrease Minor scoping areas affected Major scoping areas affected Scope reduction unacceptable to sponsor Project end item is effectively useless
Quality Insignificant quality degradation Only very demanding applications are affected Quality reduction requires sponsor approval Quality reduction unacceptable to sponsor Project end item is effectively useless
Analyteaka Risk Probability.png

By taking into consideration the estimated probability of occurrence as well as the potential impact from the risk impact assessment, a quantitative impact measure is obtained. Based on the team and clients risk threshold and appetite, the measures will be grouped and the appropriate action to be taken will be identified.

Impact /
Probability
Very Low Low Moderate High Very High
0.05 0.10 0.20 0.40 0.80
0.90 0.05 0.09 0.18 0.36 0.72
0.70 0.04 0.07 0.14 0.28 0.56
0.50 0.03 0.05 0.10 0.20 0.40
0.30 0.02 0.03 0.06 0.12 0.24
0.10 0.01 0.01 0.02 0.04 0.08

Risk responses involve a combination of the following activities: Avoiding, Mitigating and Accepting. Prior to the start of each phase of the project, all risks will be considered and preventive measures will be put in place as part of mitigation. Additional action will be taken in accordance to the descriptive bands that are detailed below.

Green (Conditional Management) – Green regions will involve continuing with the project as per normal. Acceptance will be the main response in this band, active steps will only be taken when indicators of the risk arising begin to present themselves.

Orange (Passive Management, Mitigating) – Yellow regions will involve continuing with the project with passive risk management. Mitigation will be the main response in this band. During each end of iteration review, we will take note of whether the risk is still a possible threat and given the circumstances at each checkpoint, we will decide whether to invoke contingency measures and subsequently, risk management measures.

Red (Active Management, Avoiding and Mitigating) – Red regions will involve continuing with the project with active risk management. Avoidance will be the main response in this band. Contingency measures will be set in place and during each end of iteration review, we will take note of whether the risk is still a possible threat and given the circumstances at each checkpoint, we will decide whether to directly invoke risk management measures

Analyteaka Risk Identified.png
S/N Risk Type Risk Detail Risk Mitigation Likelihood Impact Strategy
1 Technical Risk Majority of our team is not proficient in python, google app engine, flask and machine learning. (Resolved) Spent time going through bootcamp training for python and machine learning to build on our foundation. We will also take various modules such as visual analytics, AA, EWS and networking to build on our competency. Very High - 0.9 Very high - Potential delay in the schedule due to production delay. Active Management
2 Resource Management Risk Most of the team are not well-versed in analytics, which is the core feature of our system. As well as limited knowledge on consumer behavior and digital marketing. (Resolved) Spent time going through bootcamp training for analytics and consult professors on analytics. Also take courses related to digital marketing and consumer behavior. High - 0.8 High - Could affect our production timeline and analytics result. Active Management
3 Human Risk Potential schedule clash due to the different in class timetable. Additionally, FYP with internship concurrently means we could only work on our project at night and during the weekends. (Resolved) Project manager to better plan the schedule. Ensuring that everyone will have a common free slot for work (e.g 1 day block slot every week) Medium - 0.5 Moderate - Schedule need to be re-adjusted if there’s a delay in the execution of task. Passive Management
4 Client Management Risk Client unable to provide csv containing sensitive data (NRIC, name) due to privacy compliances (Resolved) Discuss with clients and capture what we need during bootstrap stage (e.g determine age, gender and race) and hash the values such that we can still analyze it without having access or storing the raw csv file. Medium - 0.3 Moderate - Would require a work around to analysis the data Passive Management
5 Technical Risk PDPA changes might affect the way our application is design and structured. (Resolved) Very high - Potential delay in the schedule due to production delay. High - 0.8 To structure the database with bare minimum personal data inside the database. This is to ensure in the event of PDPA regulation change we will have bare minimum requirement change. Even though, we are likely not going to get affected by the regulation during the few months of development, we have to ensure the application will last without need the need to change. Active management
Analyteaka Footer Transparent.png