Difference between revisions of "IS480 Team wiki: 2012T1 M.O.O.T/Project Management/Risk Management"
Jump to navigation
Jump to search
Line 57: | Line 57: | ||
|- | |- | ||
| 1 | | 1 | ||
− | | | + | | No library available for gender recognition |
| | | | ||
* Development is delayed | * Development is delayed | ||
Line 63: | Line 63: | ||
| High | | High | ||
| | | | ||
− | * | + | * Research on possible ways/algorithms to do gender recognition� |
+ | * Devise feasible way to determine gender | ||
+ | �* Learn, modify and integrate algorithm into application | ||
+ | | | ||
+ | |- | ||
+ | | 1 | ||
+ | | No library available for gender recognition | ||
+ | | | ||
+ | * Development is delayed | ||
+ | | High | ||
+ | | High | ||
+ | | | ||
+ | * Research on possible ways/algorithms to do gender recognition� | ||
+ | * Devise feasible way to determine gender | ||
+ | �* Learn, modify and integrate algorithm into application | ||
+ | | | ||
+ | |- | ||
+ | | 1 | ||
+ | | Accuracy of gender recognition | ||
+ | | | ||
+ | * Development is delayed | ||
+ | | High | ||
+ | | High | ||
+ | | | ||
+ | * Add more behaviour traits and characteristics as parameters to determine gender such as shape of clothes, heels elevation | ||
| | | | ||
− | |||
|- | |- | ||
| 2 | | 2 |
Revision as of 12:20, 16 August 2012
Project Schedule | Methodology | Metrics | Risk Management | Minutes Repository |
Risk Management
S/N | Risk Statement | Impact | Likelihood | Impact Level | Mitigation Strategy | Status |
Technology & Learning Risk | ||||||
1 | No library available for gender recognition |
|
High | High |
�* Learn, modify and integrate algorithm into application |
|
1 | No library available for gender recognition |
|
High | High |
�* Learn, modify and integrate algorithm into application |
|
1 | Accuracy of gender recognition |
|
High | High |
|
|
2 | No suitable gestures library that we can use |
|
High | High |
|
|
3 | Self-written motion gestures may be inaccurate/inconsistent/too difficult to perform. |
|
High | High |
|
|
4 | Team is unfamiliar with working with new technology & tools |
|
High | High |
|
|
Scope Risk | ||||||
5 | Sponsor changes his requirements frequently |
|
Medium | Medium |
|
|
6 | Team overpromising new features |
|
Medium | Medium |
|
|
Development Risk | ||||||
7 | There is a critical bug that affects the core functionalities |
|
High | High |
|
|
Schedule Risk | ||||||
8 | Team members have other commitments and different priorities |
|
Medium | High |
|