Difference between revisions of "IS480 Team wiki: 2016T2 Codex Risk Management"
Jump to navigation
Jump to search
(Created page with "<!--Logo--> 100px|center<br> <!--/Logo--> <!--Header--> {|style="background-color:#27546E; color:#F5F5F5; padding: 10 0 10 0;" width="100%" cellspacin...") |
|||
(9 intermediate revisions by 2 users not shown) | |||
Line 4: | Line 4: | ||
<!--Header--> | <!--Header--> | ||
− | {|style="background-color:# | + | {|style="background-color:#A6CE39; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" | |
− | | style="padding:0.3em; font-size:100%; background-color:# | + | | style="padding:0.3em; font-size:100%; background-color:#A6CE39; text-align:center; color:#FFFFFF" width="10%" | |
− | [[Image: | + | [[Image:Codex_logo.png|22px | |
link=IS480 Team wiki: 2016T2 Codex]] [[IS480 Team wiki: 2016T2 Codex | | link=IS480 Team wiki: 2016T2 Codex]] [[IS480 Team wiki: 2016T2 Codex | | ||
− | <font color="# | + | <font color="#FFFFFF" size=2><b>HOME</b></font>]] |
| style="background:none;" width="1%" | | | style="background:none;" width="1%" | | ||
− | | style="padding:0.3em; font-size:100%; background-color:# | + | | style="padding:0.3em; font-size:100%; background-color:#A6CE39; text-align:center; color:#FFFFFF" width="10%" | |
[[Image:Codex_aboutus.png|22px | | [[Image:Codex_aboutus.png|22px | | ||
link=IS480 Team wiki: 2016T2 Codex About Us]] [[IS480 Team wiki: 2016T2 Codex About Us | | link=IS480 Team wiki: 2016T2 Codex About Us]] [[IS480 Team wiki: 2016T2 Codex About Us | | ||
− | <font color="# | + | <font color="#FFFFFF" size=2><b>ABOUT US</b></font>]] |
| style="background:none;" width="1%" | | | style="background:none;" width="1%" | | ||
− | | style="padding:0.3em; font-size:100%; background-color:# | + | | style="padding:0.3em; font-size:100%; background-color:#A6CE39; border-bottom:0px solid #3D9DD7; text-align:center; color:#FFFFFF" width="12%" | |
[[Image:Codex_projectoverview.png|22px | | [[Image:Codex_projectoverview.png|22px | | ||
link=IS480 Team wiki: 2016T2 Codex Project Overview]] [[IS480 Team wiki: 2016T2 Codex Project Overview | | link=IS480 Team wiki: 2016T2 Codex Project Overview]] [[IS480 Team wiki: 2016T2 Codex Project Overview | | ||
− | <font color="# | + | <font color="#FFFFFF" size=2><b>PROJECT OVERVIEW</b></font>]] |
| style="background:none;" width="1%" | | | style="background:none;" width="1%" | | ||
− | | style="padding:0.3em; font-size:100%; background-color:# | + | | style="padding:0.3em; font-size:100%; background-color:#45812B; border-bottom:0px solid #3D9DD7; text-align:center; color:#FFFFFF" width="12%" | |
[[Image:Codex_projmgt.png|22px | | [[Image:Codex_projmgt.png|22px | | ||
link=IS480 Team wiki: 2016T2 Codex Project Management]] [[IS480 Team wiki: 2016T2 Codex Project Management | | link=IS480 Team wiki: 2016T2 Codex Project Management]] [[IS480 Team wiki: 2016T2 Codex Project Management | | ||
− | <font color="# | + | <font color="#FFFFFF" size=2><b>PROJECT MANAGEMENT</b></font>]] |
| style="background:none;" width="1%" | | | style="background:none;" width="1%" | | ||
− | | style="padding:0.3em; font-size:100%; background-color:# | + | | style="padding:0.3em; font-size:100%; background-color:#A6CE39; border-bottom:0px solid #3D9DD7; text-align:center; color:#FFFFFF" width="10%" | |
[[Image:Codex_doc.png |22px | | [[Image:Codex_doc.png |22px | | ||
link=IS480 Team wiki: 2016T2 Codex Documentation]] [[IS480 Team wiki: 2016T2 Codex Documentation| | link=IS480 Team wiki: 2016T2 Codex Documentation]] [[IS480 Team wiki: 2016T2 Codex Documentation| | ||
− | <font color="# | + | <font color="#FFFFFF" size=2><b>DOCUMENTATION</b></font>]] |
|} | |} | ||
<!--/Header--> | <!--/Header--> | ||
Line 39: | Line 39: | ||
{| style="background-color:white; color:white padding: 5 0 0;" width="100%" height=50px cellspacing="0" cellpadding="0" valign="top" border="0" | | {| style="background-color:white; color:white padding: 5 0 0;" width="100%" height=50px cellspacing="0" cellpadding="0" valign="top" border="0" | | ||
− | | style="vertical-align:top;width: | + | | style="vertical-align:top;width:20%;" | <div style="padding: 3px; font-weight: bold; text-align:center; line-height: wrap_content; font-size:16px; border-bottom:1px font-family:helvetica"> [[IS480_Team_wiki:_2016T2 Project Schedule| <font color="#45812B"><b>Project Schedule</b></font>]] |
− | | style="vertical-align:top;width: | + | | style="vertical-align:top;width:20%;" | <div style="padding: 3px; font-weight: bold; text-align:center; line-height: wrap_content; font-size:16px; border-bottom:1px font-family:helvetica"> [[IS480_Team_wiki:_2016T2 Codex Metrics| <font color="#45812B"><b>Metrics</b></font>]] |
− | | style="vertical-align:top;width: | + | | style="vertical-align:top;width:20%;" | <div style="padding: 3px; font-weight: bold; text-align:center; line-height: wrap_content; font-size:16px; border-bottom:3px solid #45812B; font-family:helvetica"> [[IS480_Team_wiki:_2016T2 Codex Risk Management| <font color="#45812B"><b>Risk Management</b></font>]] |
− | [[IS480_Team_wiki:_2016T2 Codex | ||
− | | | + | |} |
+ | <!--Sub Header End--> | ||
+ | |||
+ | <!--Content Start--> | ||
− | | style=" | + | {| class="wikitable" style="text-align: center; background-color:#FFFFFF;" |
+ | |- | ||
+ | ! style="font-weight: bold;background: #A6CE39;color:#fff;" | # | ||
+ | ! style="font-weight: bold;background: #A6CE39;color:#fff;" | Risk Type | ||
+ | ! style="font-weight: bold;background: #A6CE39;color:#fff;" | Risk Event | ||
+ | ! style="font-weight: bold;background: #A6CE39;color:#fff;" | Likelihood | ||
+ | ! style="font-weight: bold;background: #A6CE39;color:#fff;" | Impact | ||
+ | ! style="font-weight: bold;background: #A6CE39;color:#fff;" | Category | ||
+ | ! style="font-weight: bold;background: #A6CE39;color:#fff;" | Mitigation | ||
+ | |- | ||
+ | | 1 | ||
+ | | Technical Risk | ||
+ | | Overall, the team is not familiar with the technologies/resources used for developing the project (i.e. PHP.) | ||
+ | | High | ||
+ | | High | ||
+ | | A | ||
+ | | We will conduct peer teaching and sharing to help each other. | ||
+ | |- | ||
+ | | 2 | ||
+ | | Project Management Risk | ||
+ | | Team’s lack of experience might cause delays in the iterations due to underestimate or overestimate of a programming task. | ||
+ | | Medium | ||
+ | | High | ||
+ | | A | ||
+ | | Regular meetings to update on progress. If necessary, we will re-plan task(s) for the next iteration. | ||
+ | |- | ||
+ | | 3 | ||
+ | | Client Management | ||
+ | | Client is unable to give us the relevant data for us, causing a delay in our project schedule. | ||
+ | | Medium | ||
+ | | Medium | ||
+ | | B | ||
+ | | We will try to make do with sample data first, so that as soon as we get the relevant data from our client, we can integrate into our system straightaway. | ||
+ | |- | ||
+ | | 4 | ||
+ | | Client Management Risk | ||
+ | | Client has not fully decided upon the range of functions in her application as she is new to a e-commerce web application; may eventually lead to big scope changes. | ||
+ | | Medium | ||
+ | | Medium | ||
+ | | B | ||
+ | | Regular meet up with our client to update her on our current progress and ask for incremental feedbacks. | ||
+ | |- | ||
+ | | 5 | ||
+ | | Client Management Risk | ||
+ | | Client has not host an e-commerce or a website before and is not IT savy, she may experience some difficulty with using our system. | ||
+ | | Medium | ||
+ | | Medium | ||
+ | | B | ||
+ | | We try to maintain simplicity in our design but we might compile a user guide for her future reference. | ||
+ | |- | ||
+ | | 6 | ||
+ | | Resource Risk | ||
+ | | Unforeseeable problems with technology that could cause loss of data. | ||
+ | | Low | ||
+ | | High | ||
+ | | B | ||
+ | | Make sure that files are always updated in the dropbox, such that the loss of a local hard drive will not affect the project greatly. | ||
+ | |- | ||
+ | | 7 | ||
+ | | Human Risk | ||
+ | | Team members become unavailable due to sickness or other unavoidable circumstances, as we have only 4 members. | ||
+ | | Low | ||
+ | | Medium | ||
+ | | C | ||
+ | | If time permits and it is a small task, shift the subtask to another iteration. Else, code sharing session and another coder will take over. | ||
+ | |- | ||
|} | |} | ||
− | <!-- | + | <!--/Content End--> |
Latest revision as of 11:49, 19 February 2016
# | Risk Type | Risk Event | Likelihood | Impact | Category | Mitigation |
---|---|---|---|---|---|---|
1 | Technical Risk | Overall, the team is not familiar with the technologies/resources used for developing the project (i.e. PHP.) | High | High | A | We will conduct peer teaching and sharing to help each other. |
2 | Project Management Risk | Team’s lack of experience might cause delays in the iterations due to underestimate or overestimate of a programming task. | Medium | High | A | Regular meetings to update on progress. If necessary, we will re-plan task(s) for the next iteration. |
3 | Client Management | Client is unable to give us the relevant data for us, causing a delay in our project schedule. | Medium | Medium | B | We will try to make do with sample data first, so that as soon as we get the relevant data from our client, we can integrate into our system straightaway. |
4 | Client Management Risk | Client has not fully decided upon the range of functions in her application as she is new to a e-commerce web application; may eventually lead to big scope changes. | Medium | Medium | B | Regular meet up with our client to update her on our current progress and ask for incremental feedbacks. |
5 | Client Management Risk | Client has not host an e-commerce or a website before and is not IT savy, she may experience some difficulty with using our system. | Medium | Medium | B | We try to maintain simplicity in our design but we might compile a user guide for her future reference. |
6 | Resource Risk | Unforeseeable problems with technology that could cause loss of data. | Low | High | B | Make sure that files are always updated in the dropbox, such that the loss of a local hard drive will not affect the project greatly. |
7 | Human Risk | Team members become unavailable due to sickness or other unavoidable circumstances, as we have only 4 members. | Low | Medium | C | If time permits and it is a small task, shift the subtask to another iteration. Else, code sharing session and another coder will take over. |