Difference between revisions of "IS480 Team wiki: 2016T2 ProgneSIS Risk Management"
Jump to navigation
Jump to search
(30 intermediate revisions by the same user not shown) | |||
Line 37: | Line 37: | ||
| style="font-size:100%; border-bottom:1px solid #354458; border-right:1px solid #354458; text-align:center; background-color:#FFFFFF; " width="10%" | [[IS480_Team_wiki:_2016T2_ProgneSIS_Risk_Management | <font face="Century Gothic" color="#354458">Risk Management</font>]] | | style="font-size:100%; border-bottom:1px solid #354458; border-right:1px solid #354458; text-align:center; background-color:#FFFFFF; " width="10%" | [[IS480_Team_wiki:_2016T2_ProgneSIS_Risk_Management | <font face="Century Gothic" color="#354458">Risk Management</font>]] | ||
+ | | style="font-size:100%; border-bottom:1px solid #354458; border-right:1px solid #354458; text-align:center; background-color:#FFFFFF; " width="10%" | [[IS480_Team_wiki:_2016T2_ProgneSIS_Change_Management | <font face="Century Gothic" color="#354458">Change Management</font>]] | ||
|} | |} | ||
Line 44: | Line 45: | ||
==<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>== | ==<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>== | ||
− | + | <br> | |
{| class="wikitable" style="margin: auto;width:60%; text-align:center; background: white;" | {| 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:50px" | Impact | ||
Line 56: | Line 57: | ||
|- | |- | ||
|! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | High | |! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | High | ||
− | |A | + | |! style="background: #FF0000; color: black; font-weight: bold; width:50px" | A |
− | |A | + | |! style="background: #FF0000; color: black; font-weight: bold; width:50px" | A |
− | |B | + | |! style="background: #FFFF00; color: black; font-weight: bold; width:50px" | B |
|- | |- | ||
|! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | Medium | |! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | Medium | ||
− | |A | + | |! style="background: #FF0000; color: black; font-weight: bold; width:50px" | A |
− | |B | + | |! style="background: #FFFF00; color: black; font-weight: bold; width:50px" | B |
− | |C | + | |! style="background: #00FF00; color: black; font-weight: bold; width:50px" | C |
|- | |- | ||
|! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | Low | |! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | Low | ||
− | |B | + | |! style="background: #FFFF00; color: black; font-weight: bold; width:50px" | B |
− | |C | + | |! style="background: #00FF00; color: black; font-weight: bold; width:50px" | C |
− | |C | + | |! style="background: #00FF00; color: black; font-weight: bold; width:50px" | 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>== | ==<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>== | ||
− | + | <br> | |
{| class="wikitable" style="margin: auto;width:90%; text-align:center; background: white;" | {| 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:50px" | Risk Type | ||
Line 82: | Line 83: | ||
! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | Category | ! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | Category | ||
! style="background: #7f7f7f; color: white; font-weight: bold; width:250px" | Mitigation Plan | ! style="background: #7f7f7f; color: white; font-weight: bold; width:250px" | Mitigation Plan | ||
+ | |- | ||
+ | |Project Management Risk | ||
+ | |Uneven distribution of workload. | ||
+ | |Project will be potentially delayed due to poor team synergy leading to uncooperative team members. | ||
+ | |High | ||
+ | |High | ||
+ | |A | ||
+ | |Project Manager to ensure that members make up for the hours during iterations where they contributed lesser (in terms of hours) due to heavier commitments. | ||
|- | |- | ||
|Technical Risk | |Technical Risk | ||
− | |Team is unfamiliar with technology used ( | + | |Team is unfamiliar with technology used (react.js, node.js, mocha, chai, etc) |
− | |Project will be potentially delayed due to | + | |Project will be potentially delayed due to inaccurate estimates of time required for development. Higher probability of bugs. |
|High | |High | ||
|High | |High | ||
|A | |A | ||
− | |Lead developer will 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 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 |
− | | | + | |High |
− | | A | + | |A |
− | | | + | |Project Manager to get logistics-field users doing similar work to VersaFleet users to provide feedback for our application. |
− | |||
|- | |- | ||
− | | Project | + | |Project Risk |
− | | | + | |Delay in availability of APIs with necessary data to us, such as API with Delivery Fulfillment Rate data. |
− | | Project | + | |Project could be potentially delayed due to a delay in development of graphs and tables which are then used for Customer Module. |
− | | Medium | + | |Medium |
− | | | + | |High |
− | | | + | |A |
− | | | + | |Project Manager to give sponsor datelines so that sponsor has sufficient time to gather information and provide them to us. |
|- | |- | ||
− | | Project | + | |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. |
− | | Medium | + | |Medium |
− | | | + | |High |
− | | | + | |A |
− | | | + | |Project Manager to give sponsor a dateline to respond to us. |
|- | |- | ||
− | | | + | |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. |
|- | |- | ||
|} | |} | ||
<!--Content End--> | <!--Content End--> |
Latest revision as of 02:06, 20 February 2016
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 |
---|---|---|---|---|---|---|
Project Management Risk | Uneven distribution of workload. | Project will be potentially delayed due to poor team synergy leading to uncooperative team members. | High | High | A | Project Manager to ensure that members make up for the hours during iterations where they contributed lesser (in terms of hours) due to heavier commitments. |
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 get logistics-field users doing similar work to VersaFleet users to provide feedback for our application. |
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 Customer Module. | Medium | High | A | Project Manager to give sponsor datelines so that sponsor has sufficient time to gather information and provide them to us. |
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. | Medium | High | A | Project Manager to give sponsor a dateline to respond to us. |
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. |