Difference between revisions of "IS480 Team wiki: 2016T2 ProgneSIS Risk Management"
Jump to navigation
Jump to search
Line 99: | Line 99: | ||
|Team to look for similar data as replacement. | |Team to look for similar data as replacement. | ||
|- | |- | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|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 is ensure that there is at least two members capable of a development work. | ||
|- | |- | ||
Line 114: | Line 108: | ||
|A | |A | ||
|Project Manager to work closely with sponsor to schedule user testing. | |Project Manager to work closely with sponsor to schedule 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 Management Risk | |Project Management Risk |
Revision as of 19:31, 23 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 lead 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 Manager to to work with Technical Lead is ensure that there is at least two members capable of a development work. | ||||||||||||
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 work closely with sponsor to schedule 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 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. |