HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
Line 103: Line 103:
 
|Project Risk
 
|Project Risk
 
|Delay in getting business information such as cost and revenue composition.
 
|Delay in getting business information such as cost and revenue composition.
|Project will be potentially delayed due to a major changes to be made in existing graphs and tables.
+
|Project will be potentially delayed due to major changes to be made in existing graphs and tables.
 
|High
 
|High
 
|Medium
 
|Medium
Line 110: Line 110:
 
|-
 
|-
 
|Project Risk
 
|Project Risk
|Delay in availability of APIs to us such, with necessary data such as Delivery Fulfillment Rate
+
|Delay in availability of APIs with necessary data to us, such as API with Delivery Fulfillment Rate data.
 
|Project will be potentially delayed due to a delay in development of graphs and tables which are then built upon for Shipper Module.
 
|Project will be potentially delayed due to a delay in development of graphs and tables which are then built upon for Shipper Module.
 
|High
 
|High
Line 126: Line 126:
 
|-
 
|-
 
|Project Management Risk
 
|Project Management Risk
|A team member is unable to continue development due to health or personal reasons.
+
|A team member is unable to continue development due to health or personal reasons and is the only member who can develop a specific function.
 
|Project will be potentially delayed due to a halt in progress.  
 
|Project will be potentially delayed due to a halt in progress.  
 
|High
 
|High
 
|Low
 
|Low
 
|B
 
|B
|Project Manager to to work with Technical Lead is ensure that there is at least two members capable of a development work.  
+
|Project Manager to to work with Technical Lead and ensure that there is at least two members capable of specific development work.
 
|-
 
|-
 
|Project Management Risk
 
|Project Management Risk
 
|Uneven distribution of workload due to differences in development capabilities.
 
|Uneven distribution of workload due to differences in development capabilities.
|Poor team dynamics might affect productivity and cooperation, potentially causing a delay in project.
+
|Poor team dynamics might arise and affect productivity and cooperation, thereby potentially causing a delay in project.
 
|Medium
 
|Medium
 
|Medium
 
|Medium
Line 147: Line 147:
 
|Low
 
|Low
 
|C
 
|C
|Conduct user testing with prototypes prior to development.
+
|Conduct user testing with paper prototypes prior to development and get client's approval before proceeding with development.
 
|-
 
|-
 
|}
 
|}
  
 
<!--Content End-->
 
<!--Content End-->

Revision as of 21:18, 30 October 2015

Progensis.png
Team Prognesis Icon Home.png

HOME

  Team Prognesis Icon AboutUs.png

ABOUT US

  Team Prognesis Icon Overview.png

PROJECT OVERVIEW

  Team Prognesis Icon ProjectManagement.png

PROJECT MANAGEMENT

  Team Prognesis Icon Documentation.png

DOCUMENTATION

 
Project Schedule Schedule Metrics Task Metrics Bug Metrics Risk Management Change Management

Risk Matrix


Impact Likelihood
Level High Medium Low
High A A B
Medium A B C
Low B C C

Risk Management


Risk Type Risk Description Impact Likelihood Impact Category Mitigation Plan
Technical Risk Team is unfamiliar with technology used (react.js, node.js, mocha, chai, etc) Project will be potentially delayed due to inaccurate estimates of time required for development. Higher probability of more bugs. High High A Lead developer will lead research and discuss with the team. Project Manager to allocate more time to this task.

Developers to spend time doing tutorials before beginning with development.

Project Management Risk Unable to get users of logistics SMEs to test our application due to their packed schedule. Unable to get genuine feedback from actual users and hence affect the usability of the system. High High A Project Manager to inform sponsor team's availability to conduct user testing in advance so that sponsor has sufficient lead time to arrange user testing.
Project Risk Delay in getting business information such as cost and revenue composition. Project will be potentially delayed due to major changes to be made in existing graphs and tables. High Medium A Team give sponsor datelines so that sponsor has sufficient time to gather information and provide them to us.
Project Risk Delay in availability of APIs with necessary data to us, such as API with Delivery Fulfillment Rate data. Project will be potentially delayed due to a delay in development of graphs and tables which are then built upon for Shipper Module. High Medium A Team give sponsor datelines so that sponsor has sufficient time to gather information and provide them to us.
Project Risk Unable to connect to third party API and hence unable to extract data necessary for development of graphs and tables. Project will be potentially be delayed as the aggregation algorithm of these data to display relevant information to user need more time. High Medium A Team to work closely with Sponsor and seek help from his developers in early iterations to ensure successful API connection.
Project Management Risk A team member is unable to continue development due to health or personal reasons and is the only member who can develop a specific function. Project will be potentially delayed due to a halt in progress. High Low B Project Manager to to work with Technical Lead and ensure that there is at least two members capable of specific development work.
Project Management Risk Uneven distribution of workload due to differences in development capabilities. Poor team dynamics might arise and affect productivity and cooperation, thereby potentially causing a delay in project. Medium Medium B Project Manager to work closely with the lead developer to allocate more time for lead developer to train other developers.
External Risk Client is unable to clearly articulate requirements for application. Possible mismatch in application and user expectations. Medium Low C Conduct user testing with paper prototypes prior to development and get client's approval before proceeding with development.