Difference between revisions of "IS480 Team wiki: 2016T2 ProgneSIS Risk Management"
Jump to navigation
Jump to search
Line 43: | Line 43: | ||
| style="font-family:Century Gothic; font-size:100%; border-bottom:1px solid #354458; border-left:1px solid #354458; border-right:1px solid #354458; background-color:#FFFFFF; " width="10%" | | | style="font-family:Century Gothic; font-size:100%; border-bottom:1px solid #354458; border-left:1px solid #354458; border-right:1px solid #354458; background-color:#FFFFFF; " width="10%" | | ||
− | < | + | ==<div style="background: #7f7f7f; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Risk Matrix</font></div>== |
− | < | + | |
+ | {| class="wikitable" style="margin: auto;width:60%; text-align:center; background: white;" | ||
+ | ! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | Impact | ||
+ | ! style="background: #7f7f7f; color: white; font-weight: bold; width:150px" | Likelihood | ||
+ | |} | ||
+ | {| class="wikitable" style="margin: auto;width:60%; text-align:center; background: white;" | ||
+ | ! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | Level | ||
+ | ! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | High | ||
+ | ! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | Medium | ||
+ | ! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | Low | ||
+ | |- | ||
+ | |! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | High | ||
+ | |A | ||
+ | |A | ||
+ | |B | ||
+ | |- | ||
+ | |! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | Medium | ||
+ | |A | ||
+ | |B | ||
+ | |C | ||
+ | |- | ||
+ | |! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | Low | ||
+ | |B | ||
+ | |C | ||
+ | |C | ||
+ | |- | ||
+ | |} | ||
+ | |||
+ | ==<div style="background: #7f7f7f; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Risk Management</font></div>== | ||
+ | |||
+ | {| class="wikitable" style="margin: auto;width:90%; text-align:center; background: white;" | ||
+ | ! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | Risk Type | ||
+ | ! style="background: #7f7f7f; color: white; font-weight: bold; width:250px" | Risk Description | ||
+ | ! style="background: #7f7f7f; color: white; font-weight: bold; width:250px" | Impact | ||
+ | ! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | Likelihood | ||
+ | ! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | Impact | ||
+ | ! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | Category | ||
+ | ! style="background: #7f7f7f; color: white; font-weight: bold; width:250px" | Mitigation Plan | ||
+ | |- | ||
+ | |Technical Risk | ||
+ | |Team is unfamiliar with technology used (barcode scanning, charting, etc) | ||
+ | |Project will be potentially delayed due to incorrect estimates. The quality of the system might not be as satisfactory as there might be more bugs. | ||
+ | |High | ||
+ | |High | ||
+ | |A | ||
+ | |Lead developer will research and discuss with the team. Project Manager to allocate more time to this task. | ||
+ | |- | ||
+ | | Technical Risk | ||
+ | | Servers – Client is unable to provide access to local server during development phase | ||
+ | | Application may not be compatible with the client’s server | ||
+ | | High | ||
+ | | Medium | ||
+ | | A | ||
+ | | Team to deploy on OpenShift during development phase. | ||
+ | Team to know the client's server's specifications and research on deployment prior to deployment to client's server. | ||
+ | |- | ||
+ | | Project Management Risk | ||
+ | | Failed to factor in minor coding tasks due to lack of experience. The schedule was planned closely to the BRD and it focuses on the macro functionalities of the whole system | ||
+ | | Project will be potentially be delayed because minor coding tasks was not planned for. | ||
+ | | Medium | ||
+ | | Medium | ||
+ | | B | ||
+ | | PM has to work closely with the lead developer to bridge the gap between the business functions and the technical components. | ||
+ | |- | ||
+ | | Project Management Risk | ||
+ | | Client changes requirements on an ad hoc basis | ||
+ | | Project schedule will be affected | ||
+ | | Medium | ||
+ | | Medium | ||
+ | | B | ||
+ | | Team to evaluate changes on a case to case basis based on change management. | ||
+ | |- | ||
+ | | Project Management Risks | ||
+ | | Unable to get NP nursing students to test due to constraints in Ngee Ann Polytechnic’s academic calendar | ||
+ | | Unable to get genuine feedback from students and hence affect the usability of the system | ||
+ | | High | ||
+ | | High | ||
+ | | A | ||
+ | | PM to reschedule project to finish Student's Portal functions before the students are unavailable. | ||
+ | |- | ||
+ | |} | ||
+ | |||
<!--Content End--> | <!--Content End--> |
Revision as of 20:39, 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 (barcode scanning, charting, etc) | Project will be potentially delayed due to incorrect estimates. The quality of the system might not be as satisfactory as there might be more bugs. | High | High | A | Lead developer will research and discuss with the team. Project Manager to allocate more time to this task. |
Technical Risk | Servers – Client is unable to provide access to local server during development phase | Application may not be compatible with the client’s server | High | Medium | A | Team to deploy on OpenShift during development phase.
Team to know the client's server's specifications and research on deployment prior to deployment to client's server. |
Project Management Risk | Failed to factor in minor coding tasks due to lack of experience. The schedule was planned closely to the BRD and it focuses on the macro functionalities of the whole system | Project will be potentially be delayed because minor coding tasks was not planned for. | Medium | Medium | B | PM has to work closely with the lead developer to bridge the gap between the business functions and the technical components. |
Project Management Risk | Client changes requirements on an ad hoc basis | Project schedule will be affected | Medium | Medium | B | Team to evaluate changes on a case to case basis based on change management. |
Project Management Risks | Unable to get NP nursing students to test due to constraints in Ngee Ann Polytechnic’s academic calendar | Unable to get genuine feedback from students and hence affect the usability of the system | High | High | A | PM to reschedule project to finish Student's Portal functions before the students are unavailable. |