Difference between revisions of "IS480 Team wiki: 2016T1 IPMAN Risk Management"
Jump to navigation
Jump to search
Line 58: | Line 58: | ||
<br/> | <br/> | ||
[[Image:IPMAN_RiskManagement_Title.png|center|600px]] | [[Image:IPMAN_RiskManagement_Title.png|center|600px]] | ||
− | |||
<br/> | <br/> | ||
[[Image:IPMAN RiskManagement 1.png |center|1000px]] | [[Image:IPMAN RiskManagement 1.png |center|1000px]] | ||
<br/> | <br/> | ||
− | < | + | |
− | + | =Risks & Challenges Faced= | |
− | < | + | <center> |
+ | {| class="wikitable" style="font-family:Garamond; background-color:#FFFFFF; width: 1000px;" align="center" | ||
+ | |- | ||
+ | |||
+ | ! style="color:#ecf0f1; background-color:#07264C;" width="100pt" | Risk Type | ||
+ | ! style="color:#ecf0f1; background-color:#07264C;" width="300pt" | Risk Event | ||
+ | ! style="color:#ecf0f1; background-color:#07264C;" width="100pt" | Likelihood | ||
+ | ! style="color:#ecf0f1; background-color:#07264C;" width="100pt" | Impact Level | ||
+ | ! style="color:#ecf0f1; background-color:#07264C;" width="50pt" | Category | ||
+ | ! style="color:#ecf0f1; background-color:#07264C;" width="100pt" | Strategy Adopted | ||
+ | ! style="color:#ecf0f1; background-color:#07264C;" width="250pt" | Actions | ||
+ | |- | ||
+ | |||
+ | |style="text-align: center;"| Technical Risk | ||
+ | |style="text-align: left;"| Team was unfamiliar with project technologies such as PostgreSQL, ReactJS, Django and etc. | ||
+ | |style="text-align: center;"| High | ||
+ | |style="text-align: center;"| Medium | ||
+ | |style="text-align: center;"| A | ||
+ | |style="text-align: center;"| Mitigate | ||
+ | |style="text-align: left;"| Team members researched on the technologies and discussed the knowledge as a team. | ||
+ | |- | ||
+ | |||
+ | |style="text-align: center;"| Stakeholder Management Risk | ||
+ | |style="text-align: left;"| Team had to manage not only sponsors but also the developer team that the sponsors engaged. Both team and developer team are working on the same project at the same time which caused conflicts. | ||
+ | |style="text-align: center;"| High | ||
+ | |style="text-align: center;"| High | ||
+ | |style="text-align: center;"| A | ||
+ | |style="text-align: center;"| Mitigate | ||
+ | |style="text-align: left;"| Team came out with a communication protocol between the sponsors, developer team and team. We are using Trello and Telegram for communications and updates. | ||
+ | |} | ||
+ | </center> | ||
+ | |||
+ | |||
+ | =Potential Risks= | ||
+ | <center> | ||
+ | {| class="wikitable" style="font-family:Garamond; background-color:#FFFFFF; width: 1000px;" align="center" | ||
+ | |- | ||
+ | |||
+ | ! style="color:#ecf0f1; background-color:#07264C;" width="100pt" | Risk Type | ||
+ | ! style="color:#ecf0f1; background-color:#07264C;" width="400pt" | Risk Event | ||
+ | ! style="color:#ecf0f1; background-color:#07264C;" width="100pt" | Likelihood | ||
+ | ! style="color:#ecf0f1; background-color:#07264C;" width="100pt" | Impact Level | ||
+ | ! style="color:#ecf0f1; background-color:#07264C;" width="100pt" | Category | ||
+ | ! style="color:#ecf0f1; background-color:#07264C;" width="200pt" | Mitigation | ||
+ | |- | ||
+ | |||
+ | |style="text-align: center;"| Client Management Risk | ||
+ | |style="text-align: left;"| There may be changes in our client requirements which results in drastic changes to our schedule. | ||
+ | |style="text-align: center;"| Medium | ||
+ | |style="text-align: center;"| High | ||
+ | |style="text-align: center;"| A | ||
+ | |style="text-align: left;"| Our team will meet our client fortnightly to ensure that we produce based on our client’s requirements to reduce changes. | ||
+ | |- | ||
+ | |||
+ | |style="text-align: center;"| Project Management Risk | ||
+ | |style="text-align: left;"| Team may not have sufficient time to finish the tasks assigned due to heavy school workload. | ||
+ | |style="text-align: center;"| Medium | ||
+ | |style="text-align: center;"| High | ||
+ | |style="text-align: center;"| A | ||
+ | |style="text-align: left;"| Project Manager will ensure that the team is comfortable and able to deliver the product within the timeframe given to them | ||
+ | |- | ||
+ | |||
+ | |style="text-align: center;"| Resource Risk | ||
+ | |style="text-align: left;"| Laptop crashes during the FYP term | ||
+ | |style="text-align: center;"| Low | ||
+ | |style="text-align: center;"| High | ||
+ | |style="text-align: center;"| B | ||
+ | |style="text-align: left;"| Ensure that all the documentation is stored in cloud and codes are committed onto Git. | ||
+ | |} | ||
+ | </center> | ||
+ | |||
<!--/Content--> | <!--/Content--> | ||
+ | |||
+ | <!--Footer--> | ||
+ | [[Image:Silhouettes_wiki_background_IPMAN.png|1000px|center]] | ||
+ | <!--/Footer--> |
Revision as of 23:02, 7 August 2016
Risks & Challenges Faced
Risk Type | Risk Event | Likelihood | Impact Level | Category | Strategy Adopted | Actions |
---|---|---|---|---|---|---|
Technical Risk | Team was unfamiliar with project technologies such as PostgreSQL, ReactJS, Django and etc. | High | Medium | A | Mitigate | Team members researched on the technologies and discussed the knowledge as a team. |
Stakeholder Management Risk | Team had to manage not only sponsors but also the developer team that the sponsors engaged. Both team and developer team are working on the same project at the same time which caused conflicts. | High | High | A | Mitigate | Team came out with a communication protocol between the sponsors, developer team and team. We are using Trello and Telegram for communications and updates. |
Potential Risks
Risk Type | Risk Event | Likelihood | Impact Level | Category | Mitigation |
---|---|---|---|---|---|
Client Management Risk | There may be changes in our client requirements which results in drastic changes to our schedule. | Medium | High | A | Our team will meet our client fortnightly to ensure that we produce based on our client’s requirements to reduce changes. |
Project Management Risk | Team may not have sufficient time to finish the tasks assigned due to heavy school workload. | Medium | High | A | Project Manager will ensure that the team is comfortable and able to deliver the product within the timeframe given to them |
Resource Risk | Laptop crashes during the FYP term | Low | High | B | Ensure that all the documentation is stored in cloud and codes are committed onto Git. |