Difference between revisions of "IS480 Team wiki: 2012T1 M.O.O.T/Project Management/Risk Management"
Jump to navigation
Jump to search
Line 46: | Line 46: | ||
=== Risk Management === | === Risk Management === | ||
+ | ==== Future Risks ==== | ||
+ | {| class="wikitable" | ||
+ | |- | ||
+ | | style="background: #C082FF; text-align: center;" | <b>S/N</b> | ||
+ | | style="background: #C082FF; text-align: center;" | <b>Risk Statement</b> | ||
+ | | style="background: #C082FF; text-align: center;" | <b>Impact</b> | ||
+ | | style="background: #C082FF; text-align: center;" | <b>Likelihood</b> | ||
+ | | style="background: #C082FF; text-align: center;" | <b>Impact Level</b> | ||
+ | | style="background: #C082FF; text-align: center;" | <b>Mitigation Strategy</b> | ||
+ | | style="background: #C082FF; text-align: center;" | <b>Status</b> | ||
+ | |- | ||
+ | | style="background: #C8BBBE;" colspan="7" | Resource Risk | ||
+ | |- | ||
+ | | style="text-align: center;" |1 | ||
+ | | No available server storage for photos taken | ||
+ | | | ||
+ | * Inability to complete meaningful photo taking feature | ||
+ | | High | ||
+ | | High | ||
+ | | | ||
+ | * Search for complimentary storage | ||
+ | * Make codes modular and dynamic in terms of storing photos | ||
+ | * Utilize personal cloud storage account for this proof-of-concept | ||
+ | | | ||
+ | |||
+ | |- | ||
+ | | style="text-align: center;" |2 | ||
+ | | Unavailability of Internet connection to transfer photos from deployment machine to storage server | ||
+ | | | ||
+ | * Inability of shoppers to download their photos | ||
+ | | Low | ||
+ | | High | ||
+ | | | ||
+ | * For offline mode: upload photos manually to mall social networking page accessible by shoppers | ||
+ | * Implement File Transfer Protocol (FTP) to enable transferring of photos through internal network | ||
+ | | | ||
+ | |||
+ | |} | ||
+ | |||
+ | ==== Resolved Risks ==== | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- |
Revision as of 22:13, 27 September 2012
Project Schedule | Methodology | Schedule & Bug Metrics | Gender Recognition Metrics | Risk Management | Minutes Repository |
Risk Management
Future Risks
S/N | Risk Statement | Impact | Likelihood | Impact Level | Mitigation Strategy | Status |
Resource Risk | ||||||
1 | No available server storage for photos taken |
|
High | High |
|
|
2 | Unavailability of Internet connection to transfer photos from deployment machine to storage server |
|
Low | High |
|
Resolved Risks
S/N | Risk Statement | Impact | Likelihood | Impact Level | Mitigation Strategy | Status |
Technology & Learning Risk | ||||||
1 | No library available for gender recognition |
|
Low |
Low |
|
|
2 | Accuracy of gender recognition |
|
Medium |
Medium |
|
|
3 | No suitable gestures library that we can use |
|
Low |
Low |
|
|
4 | Self-written motion gestures may be inaccurate/inconsistent/too difficult to perform. |
|
Low |
Low |
|
|
5 | Team is unfamiliar with working with new technology & tools |
|
Low |
Low |
|
|
Scope Risk | ||||||
6 | Sponsor changes his requirements frequently |
|
Medium | Low |
|
|
7 | Team overpromising new features |
|
Medium | Low |
|
|
Development Risk | ||||||
8 | There is a critical bug that affects core functionalities |
|
High | Medium |
|
|
Schedule Risk | ||||||
9 | Team members have other commitments and different priorities |
|
Medium | Low |
|
|