Difference between revisions of "IS480 Team wiki: 2012T1 M.O.O.T/Project Management/Risk Management"
Jump to navigation
Jump to search
Line 58: | Line 58: | ||
|- | |- | ||
| style="text-align: center;" |1 | | style="text-align: center;" |1 | ||
− | | No available server storage for photos taken | + | | No available server storage for photos taken |
| | | | ||
* Inability to complete meaningful photo taking feature | * Inability to complete meaningful photo taking feature |
Revision as of 15:49, 30 November 2012
Project Schedule | 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 | Low |
|
FTP has been implemented for such situation |
Schedule Risk | ||||||
3 | Inability to complete photo-taking narrative in time as two members will be unavailable in week 8 |
|
Medium | High |
|
Resolved: project has been completed in time |
Usability Risk | ||||||
4 | Shoppers do not know how to respond to AlterSense |
|
Low | Low |
|
|
Technical Risk | ||||||
5 | iOS6 incompatibility with Microsoft Tag scanner prohibits users from scanning tag |
|
Low |
Low |
|
|
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 |
|
|
6 | Inability to refine overlaying of augmented background |
|
Low | Low |
|
|
Scope Risk | ||||||
7 | Sponsor changes his requirements frequently |
|
Medium | Low |
|
|
8 | Team overpromising new features |
|
Medium | Low |
|
|
Development Risk | ||||||
9 | There is a critical bug that affects core functionalities |
|
High | Medium |
|
|
Schedule Risk | ||||||
10 | Team members have other commitments and different priorities |
|
Medium | Low |
|
|