Difference between revisions of "IS480 Team wiki: 2012T1 M.O.O.T/Project Management/Risk Management"
Jump to navigation
Jump to search
(4 intermediate revisions by the same user not shown) | |||
Line 58: | Line 58: | ||
|- | |- | ||
| style="text-align: center;" |1 | | style="text-align: center;" |1 | ||
− | | No available server storage for photos taken | + | | No publicly-available server storage for photos taken |
| | | | ||
* Inability to complete meaningful photo taking feature | * Inability to complete meaningful photo taking feature | ||
Line 69: | Line 69: | ||
* Utilize personal cloud storage account for this proof-of-concept | * Utilize personal cloud storage account for this proof-of-concept | ||
| | | | ||
+ | *Personal cloud storage used as CMA is sourcing for its own alternative server storage | ||
+ | *User experience is not compromised for now, but storage from CMA is required for future maintenance and sustainability | ||
|- | |- | ||
Line 76: | Line 78: | ||
* Inability of shoppers to download their photos in real time | * Inability of shoppers to download their photos in real time | ||
| Low | | Low | ||
− | | High | + | | <strike>High</strike><br><span style="color: green;">Low</span> |
| | | | ||
* For offline mode: upload photos manually to mall social networking page accessible by shoppers | * 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 | * Implement File Transfer Protocol (FTP) to enable transferring of photos through internal network | ||
| | | | ||
+ | FTP has been implemented for such situation | ||
|- | |- | ||
Line 97: | Line 100: | ||
* Iteration to last from week 8 to week 9, design for narrative can be started in week 8 and implemented in week 9 | * Iteration to last from week 8 to week 9, design for narrative can be started in week 8 and implemented in week 9 | ||
| | | | ||
+ | Resolved: project has been completed in time | ||
|- | |- | ||
Line 112: | Line 116: | ||
* Insertion of speech bubble besides shopper's head to inform shoppers on how to respond | * Insertion of speech bubble besides shopper's head to inform shoppers on how to respond | ||
| | | | ||
+ | *Instructions have been refined according to User Testing observation and feedback | ||
+ | *Users picked up gestures quickly after the first one during UT2 | ||
+ | |- | ||
+ | | style="background: #C8BBBE;" colspan="7" | Technical Risk | ||
+ | |- | ||
+ | | style="text-align: center;" |5 | ||
+ | | iOS6 incompatibility with Microsoft Tag scanner prohibits users from scanning tag | ||
+ | | | ||
+ | *Compromised experience | ||
+ | *Inability to access photo gallery | ||
+ | |<strike>High</strike><br><span style="color: green;">Low</span> | ||
+ | |<strike>Medium</strike><br><span style="color: green;">Low</span> | ||
+ | | | ||
+ | *Use Microsoft QR code | ||
+ | *Research on reasons for incompatibility | ||
+ | *Recommend updates to Microsoft | ||
+ | | | ||
+ | *New version compatible with iOS6 was launched in end October | ||
+ | *Tested and working during UT2 on 5 November | ||
+ | |- | ||
|} | |} | ||
Latest revision as of 15:53, 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 publicly-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 |
|
|