HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2017T2 Asgardians Risk Management"

From IS480
Jump to navigation Jump to search
 
(One intermediate revision by the same user not shown)
Line 67: Line 67:
 
-  To take into consideration the amount of time required for technical exploration in project timeline.
 
-  To take into consideration the amount of time required for technical exploration in project timeline.
 
|-
 
|-
| 2 || Technical Risk – Software||XCode crashes during coding for XiaoYu's MacBook || Medium || Medium || B || Developers: To remember save work as progress.
 
  
|-
+
| 2 || Project Management Risk ||Various team members have different priorities and schedules in work which leads to inefficient allocation and completion of tasks.  || Low || Low || C ||Team: conduct frequent updates on individual progress. Establish weekly fixed meetings to coordinate work and establish consensus.  
| 3 || Project Management Risk ||Various team members have different priorities and schedules in work which leads to inefficient allocation and completion of tasks.  || Low || Low || C ||Team: conduct frequent updates on individual progress. Establish weekly fixed meetings to coordinate work and establish consensus.  
 
 
|-
 
|-
  
| 4 || Business Risk –  || Unfamiliarity with Singapore delivery rules and policy which may lead to IT-business misalignment and misunderstanding of the requirements  || Medium || Medium|| A || Team:Consult our sponsor and mentors at various stages to ensure that we are following the policies
+
| 3 || Business Risk –  || Unfamiliarity with Singapore delivery rules and policy which may lead to IT-business misalignment and misunderstanding of the requirements  || Medium || Medium|| A || Team:Consult our sponsor and mentors at various stages to ensure that we are following the policies
 
Project Manager: Liaise with the sponsors and key stakeholders and ensure all the team members clearly understand the scope
 
Project Manager: Liaise with the sponsors and key stakeholders and ensure all the team members clearly understand the scope
 
Developers:Alarm the Project Manage for any foreseen delay
 
Developers:Alarm the Project Manage for any foreseen delay
 
|-
 
|-
| 5 || Client Management Risk ||Sudden change request by client may lead to last minute change to our project schedule || Low|| High || A ||Team: conduct frequent updates with our client, get any change request as early as possible.
+
| 4 || Client Management Risk ||Sudden change request by client may lead to last minute change to our project schedule || Low|| High || A ||Team: conduct frequent updates with our client, get any change request as early as possible.
 +
|-
 +
 
 +
| 5 || Data Management Risk ||Unforeseen event / accident may lead to lost of work data and important project data. || Medium || High || A ||Team: Do version control and change control, have at least 3 working environment ( development, production , testing , and operation etc), each environment to have back up file and version control, suggested soft ware using google file stream or drop box.  
 
|-
 
|-
  

Latest revision as of 07:51, 9 April 2018

Asg icon2.jpg


Asg home.png   HOME

 

Asg AboutUs.png   ABOUT US

 

Asg ProjectOverview.png   PROJECT OVERVIEW

 

Asg ProjectManagement.png   PROJECT MANAGEMENT

 

Asg ProjectDocumentation.png   DOCUMENTATION

 


Asg risk2.jpg



S/N Risk Type Risk Event Likelihood Impact Risk Category Mitigation Plan
1 Technical Risk – Software Lack of knowledge of using swift for various data management functionalities (access location via map) Medium Medium B Developers:To spend about 2 weeks to pick up with Swift and X-code courses online and approach mentors to help us learn it.

Project Manager - To take into consideration the amount of time required for technical exploration in project timeline.

2 Project Management Risk Various team members have different priorities and schedules in work which leads to inefficient allocation and completion of tasks. Low Low C Team: conduct frequent updates on individual progress. Establish weekly fixed meetings to coordinate work and establish consensus.
3 Business Risk – Unfamiliarity with Singapore delivery rules and policy which may lead to IT-business misalignment and misunderstanding of the requirements Medium Medium A Team:Consult our sponsor and mentors at various stages to ensure that we are following the policies

Project Manager: Liaise with the sponsors and key stakeholders and ensure all the team members clearly understand the scope Developers:Alarm the Project Manage for any foreseen delay

4 Client Management Risk Sudden change request by client may lead to last minute change to our project schedule Low High A Team: conduct frequent updates with our client, get any change request as early as possible.
5 Data Management Risk Unforeseen event / accident may lead to lost of work data and important project data. Medium High A Team: Do version control and change control, have at least 3 working environment ( development, production , testing , and operation etc), each environment to have back up file and version control, suggested soft ware using google file stream or drop box.