Difference between revisions of "IS480 Team wiki: 2012T1 M.O.O.T/Project Management/Risk Management"
Jump to navigation
Jump to search
Line 62: | Line 62: | ||
| | | | ||
* Development is delayed | * Development is delayed | ||
− | | High | + | | <strike>High</strike><br><span style="color: green;">Low</span> |
| <strike>High</strike><br><span style="color: green;">Low</span> | | <strike>High</strike><br><span style="color: green;">Low</span> | ||
| | | | ||
Line 68: | Line 68: | ||
* Devise feasible way to determine gender | * Devise feasible way to determine gender | ||
* Learn, modify and integrate algorithm into application | * Learn, modify and integrate algorithm into application | ||
− | | | + | | |
+ | * Neural Network with backward propagation made gender recognition possible | ||
+ | * Gender recognition feature has been tested and worked at a minimum of 60% accuracy | ||
+ | * Measurement taking provided us with clues of physical differences between male and female | ||
+ | * Research supported primary findings from measurement taking sessions | ||
+ | |||
|- | |- | ||
| style="text-align: center;" |2 | | style="text-align: center;" |2 |
Revision as of 21:04, 27 September 2012
Project Schedule | Methodology | Schedule & Bug Metrics | Gender Recognition 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 |
|
Low |
Low |
|
|
2 | Accuracy of gender recognition |
|
High | High |
|
|
3 | No suitable gestures library that we can use |
|
High | High |
|
|
4 | Self-written motion gestures may be inaccurate/inconsistent/too difficult to perform. |
|
High | High |
|
|
5 | Team is unfamiliar with working with new technology & tools |
|
High | High |
|
|
Scope Risk | ||||||
6 | Sponsor changes his requirements frequently |
|
Medium | Medium |
|
|
7 | Team overpromising new features |
|
Medium | Medium |
|
|
Development Risk | ||||||
8 | There is a critical bug that affects the core functionalities |
|
High | High |
|
|
Schedule Risk | ||||||
9 | Team members have other commitments and different priorities |
|
Medium | High |
|