Difference between revisions of "IS480 Team wiki: 2016T2 ProgneSIS Risk Management"
Jump to navigation
Jump to search
Line 91: | Line 91: | ||
|A | |A | ||
|Lead developer will lead research and discuss with the team. Project Manager to allocate more time to this task. | |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 Risk | |Project Risk | ||
− | |Delay in getting | + | |Delay in getting business information such as cost and revenue composition. |
− | |Project will be potentially delayed due to major changes in | + | |Project will be potentially delayed due to a major changes to be made in existing graphs and tables. |
|High | |High | ||
|Medium | |Medium | ||
|A | |A | ||
− | |Team to | + | |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 to us such, with necessary data such as Delivery Fulfillment Rate | ||
+ | |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 | |Project Management Risk | ||
Line 106: | Line 123: | ||
|High | |High | ||
|A | |A | ||
− | |Project Manager to | + | |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 Management Risk | |Project Management Risk |
Revision as of 21:03, 30 October 2015
Project Schedule | Schedule Metrics | Task Metrics | Bug Metrics | Risk Management | Change Management |
|
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 Risk | 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. | 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 to us such, with necessary data such as Delivery Fulfillment Rate | 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 | 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 Management Risk | A team member is unable to continue development due to health or personal reasons. | Project will be potentially delayed due to a halt in progress. | High | Low | B | Project Manager to to work with Technical Lead is ensure that there is at least two members capable of a development work. |
Project Management Risk | Failed to factor in minor development tasks due to lack of experience. The schedule was planned as closely as possible based on sponsor's existing application which we would use to extract data for our application. | Project will be potentially be delayed as minor coding tasks were not planned for. | Medium | Medium | B | Project Manager to work closely with the lead developer to bridge the gap between the business functions and the technical components. |
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 prototypes prior to development. |