Difference between revisions of "IS480 Team wiki: 2016T2 ProgneSIS Risk Management"
Jump to navigation
Jump to search
Line 91: | Line 91: | ||
|Lead developer will research and discuss with the team. Project Manager to allocate more time to this task. | |Lead developer will research and discuss with the team. Project Manager to allocate more time to this task. | ||
|- | |- | ||
− | |Project | + | |Project Risk |
− | |Delay in getting necessary data or information due to | + | |Delay in getting necessary data or information due to sponsor's and clients' busy schedule. |
− | | | + | |Project will be potentially delayed due to major changes in development. |
|High | |High | ||
|Medium | |Medium | ||
|A | |A | ||
− | |Team to look for data | + | |Team to look for similar data as replacement. |
|- | |- | ||
|Project Management Risk | |Project Management Risk | ||
− | |Failed to factor in | + | |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 | + | |Project will be potentially be delayed as minor coding tasks were not planned for. |
− | | Medium | + | |Medium |
− | | Medium | + | |Medium |
− | | B | + | |B |
− | | | + | |Project Manager has to work closely with the lead developer to bridge the gap between the business functions and the technical components. |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|} | |} | ||
<!--Content End--> | <!--Content End--> |
Revision as of 21:47, 13 October 2015
Project Schedule | Schedule Metrics | Task Metrics | Bug Metrics | Risk 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 research and discuss with the team. Project Manager to allocate more time to this task. |
Project Risk | Delay in getting necessary data or information due to sponsor's and clients' busy schedule. | Project will be potentially delayed due to major changes in development. | High | Medium | A | Team to look for similar data as replacement. |
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 has to work closely with the lead developer to bridge the gap between the business functions and the technical components. |