HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2016T2 Unition Risk Management"

From IS480
Jump to navigation Jump to search
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
<!--------------- Header ---------------------->
 
<!--------------- Header ---------------------->
[[File:Logo.png|200px|center]]
+
[[File:Unition logo.png|450px|center]]
  
  
Line 32: Line 32:
 
<!---------------END of sub-header ---------------------->
 
<!---------------END of sub-header ---------------------->
 
<!--MAIN CONTENT-->
 
<!--MAIN CONTENT-->
{|style=" width="100%" cellspacing="0" border="0" |
+
{| class="wikitable" style="text-align:center; background: white; margin: 1px;"
| style="font-family:Baron Neue Bold; font-size:120%; border-bottom:1px solid #ADD8E6; text-align:left; background-color:#FFFFFF; " width="10%" |
 
{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000000; padding: 0; cellspacing="0" cellpadding="0" valign="top" border="0""
 
|-valign="top"
 
{| style="text-align: center; width: 100%;"
 
 
|-
 
|-
 +
! style="color:#FFFFFF; background-color:#ACD2EC;" width="500pt" | Risk Type
 +
! style="color:#FFFFFF; background-color:#ACD2EC;" width="500pt" | Risk Description
 +
! style="color:#FFFFFF; background-color:#ACD2EC;" width="800pt" | Consequence
 +
! style="color:#FFFFFF; background-color:#ACD2EC;" width="400pt" | Likelihood
 +
! style="color:#FFFFFF; background-color:#ACD2EC;" width="400pt" | Impact
 +
! style="color:#FFFFFF; background-color:#ACD2EC;" width="400pt" | Risk level
 +
! style="color:#FFFFFF; background-color:#ACD2EC;" width="800pt" | Mitigation plan
  
|valign=top width=33%|
 
<font color="#002060" size=5><b>Risk Management</b></font>
 
{| class="wikitable" style="text-align:center; background: white; margin: 0px;"
 
 
|-
 
|-
! style="color:#ecf0f1; background-color:#002060;" width="500pt" | Risk Description
+
|Technical Risk
! style="color:#ecf0f1; background-color:#002060;" width="500pt" | Category
+
|Project team has no prior knowledge of Android mobile app and need to learn to use Android Studio
! style="color:#ecf0f1; background-color:#002060;" width="800pt" | Impact
+
|Schedule may potentially be delayed due to time spent on learning and our initial deliverables might be buggy
! style="color:#ecf0f1; background-color:#002060;" width="800pt" | Mitigation Strategy
+
|High
 +
|High
 +
|A
 +
|We will have researching and learning sessions before we begin our actual coding tasks and adopts code we learn strategy.
 +
|-
 +
|-
 +
|Project Management Risk
 +
|Requirements may change in the mid or after few iterations
 +
|Delay the current process of development and project schedule will be affected
 +
|Medium
 +
|High
 +
|A
 +
|Prior agreement with sponsor that major changes will not be addressed after confirmation on the agreement • Team to evaluate changes and to discuss with both sponsor and supervisor to obtain the best case scenario
 
|-
 
|-
|The team is new to android development
+
|-
 +
|Technical Risk
 +
|Failed to connect sponsor's WordPress database with our Android application
 +
|To further research on other possible solutions or to get advice from supervisor • Discuss with the sponsor on the possibility of the our application using independent database.
 
|High
 
|High
|Schedule may potentially be delayed due to time spent on learning and our initial deliverables might be buggy
+
|Medium
|We will have researching and learning sessions before we begin our actual coding tasks and adopts code as we learn strategy.
+
|A
 +
|Find out a stable way to get data from WordPress database. Get sponsors agreement to build a separate database if failed to use their data eventually
 +
|-
 +
|-
 +
|Technical Risk
 +
|Difficulties to map all functions on ShenCARE website to mobile app to fulfil the requirement
 +
|The team may not deliver a product meet sponsors satisfaction
 +
|Medium
 +
|Medium
 +
|B
 +
|We will clearly state the scope of our project that we agreed with our sponsors. The project manager will also monitor the progress of the project closely to ensure that we stick to the agreed scope.
 
|-
 
|-
 
|-
 
|-
|Trying to fit all functions that are found on shenCare website into the mobile application
+
|Project Management Risk
 +
|Unable to find enough users to test the application
 +
|Can not get sufficient feedback from users to improve current application  
 
|Medium
 
|Medium
|The team might not be able to finish the promised deliverables on time
+
|Medium
|We will clearly state the scope of our project that we agreed with our sponsor. The project manager will also monitor the progress of the project closely to ensure that we stick to the agreed scope.
+
|B
 +
|Contact sponsors and seek for their help to attract more target users to test our project
 
|-
 
|-
 
|-
 
|-
|Juggling our academic workload and FYP when there are difficult tasks in a particular iteration
+
|Technical Risk
 +
|Sponsor's Wordpress site being down
 +
|Team will not be able to utilise required plugins from the wordpress site to perform application functions
 
|Medium
 
|Medium
|There might be delay in schedule
+
|Medium
|Th team will research online and seek advise from friends and seniors on how to best handle the difficult tasks
+
|B
 +
|Contact sponsors to inform them on the possible reasons why the site was down and to see their developer's assistance to bring up the site ASAP
 
|-
 
|-
 +
|-
 +
|Project Management Risk
 +
|Team members unavailable during some development periods due to illness or unforeseen urgent issue
 +
|Can not get sufficient feedback from users to improve current application
 +
|Low
 +
|Medium
 +
|C
 +
|Deputy person in the specific role take the task first, if not able to complete the task split to other members
 
|-
 
|-
 +
|-
 
|}
 
|}

Latest revision as of 10:41, 28 February 2016

Unition logo.png


Home   About Us   Project Overview   Project Management   Documentation


Project Schedule Metrics Risk Management
Risk Type Risk Description Consequence Likelihood Impact Risk level Mitigation plan
Technical Risk Project team has no prior knowledge of Android mobile app and need to learn to use Android Studio Schedule may potentially be delayed due to time spent on learning and our initial deliverables might be buggy High High A We will have researching and learning sessions before we begin our actual coding tasks and adopts code we learn strategy.
Project Management Risk Requirements may change in the mid or after few iterations Delay the current process of development and project schedule will be affected Medium High A Prior agreement with sponsor that major changes will not be addressed after confirmation on the agreement • Team to evaluate changes and to discuss with both sponsor and supervisor to obtain the best case scenario
Technical Risk Failed to connect sponsor's WordPress database with our Android application To further research on other possible solutions or to get advice from supervisor • Discuss with the sponsor on the possibility of the our application using independent database. High Medium A Find out a stable way to get data from WordPress database. Get sponsors agreement to build a separate database if failed to use their data eventually
Technical Risk Difficulties to map all functions on ShenCARE website to mobile app to fulfil the requirement The team may not deliver a product meet sponsors satisfaction Medium Medium B We will clearly state the scope of our project that we agreed with our sponsors. The project manager will also monitor the progress of the project closely to ensure that we stick to the agreed scope.
Project Management Risk Unable to find enough users to test the application Can not get sufficient feedback from users to improve current application Medium Medium B Contact sponsors and seek for their help to attract more target users to test our project
Technical Risk Sponsor's Wordpress site being down Team will not be able to utilise required plugins from the wordpress site to perform application functions Medium Medium B Contact sponsors to inform them on the possible reasons why the site was down and to see their developer's assistance to bring up the site ASAP
Project Management Risk Team members unavailable during some development periods due to illness or unforeseen urgent issue Can not get sufficient feedback from users to improve current application Low Medium C Deputy person in the specific role take the task first, if not able to complete the task split to other members