HeaderSIS.jpg

IS480 Team wiki: 2016T2 ProgneSIS Risk Management

From IS480
Revision as of 21:32, 30 October 2015 by Karen.lim.2013 (talk | contribs)
Jump to navigation Jump to search
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 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 VersaFleet users to test our application due to their packed schedule. Unable to get feedback from actual users and hence affect the usability of the system. High High A Project Manager to give sponsor team's schedule 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. Major changes to be made in existing graphs and tables could potentially delay project. High Medium A Project Manager to give sponsor a dateline to respond to us.
Project Risk Delay in availability of APIs with necessary data to us, such as API with Delivery Fulfillment Rate data. Project could be potentially delayed due to a delay in development of graphs and tables which are then used for Shipper Module. High Medium A Project Manager to 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 development of aggregation algorithm for these data require 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 a 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.