Difference between revisions of "IS480 Team wiki: 2012T1 M.O.O.T/Project Management/Risk Management"
Jump to navigation
Jump to search
Line 48: | Line 48: | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
− | | style="background: #C082FF; text-align | + | | style="background: #C082FF; text-align: center;" | <b>S/N</b> |
− | | style="background: #C082FF; text-align | + | | style="background: #C082FF; text-align: center;" | <b>Risk Statement</b> |
− | | style="background: #C082FF; text-align | + | | style="background: #C082FF; text-align: center;" | <b>Impact</b> |
− | | style="background: #C082FF; text-align | + | | style="background: #C082FF; text-align: center;" | <b>Likelihood</b> |
− | | style="background: #C082FF; text-align | + | | style="background: #C082FF; text-align: center;" | <b>Impact Level</b> |
− | | style="background: #C082FF; text-align | + | | style="background: #C082FF; text-align: center;" | <b>Mitigation Strategy</b> |
− | | style="background: #C082FF; text-align | + | | style="background: #C082FF; text-align: center;" | <b>Status</b> |
|- | |- | ||
| style="background: #C8BBBE;" colspan="7" | Technology & Learning Risk | | style="background: #C8BBBE;" colspan="7" | Technology & Learning Risk |
Revision as of 19:26, 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 |
|
High | High |
|
|
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 |
|