Difference between revisions of "IS480 Team wiki: 2012T1 M.O.O.T/Project Management/Risk Management"
Jump to navigation
Jump to search
Line 46: | Line 46: | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
− | | style="background: #C082FF;" | S/N | + | | style="background: #C082FF;" | <b>S/N</b> |
− | | style="background: #C082FF;" | Risk Statement | + | | style="background: #C082FF;" | <b>Risk Statement</b> |
− | | style="background: #C082FF;" | Impact | + | | style="background: #C082FF;" | <b>Impact</b> |
− | | style="background: #C082FF;" | Likelihood | + | | style="background: #C082FF;" | <b>Likelihood</b> |
− | | style="background: #C082FF;" | Impact Level | + | | style="background: #C082FF;" | <b>Impact Level</b> |
− | | style="background: #C082FF;" | Mitigation Strategy | + | | style="background: #C082FF;" | <b>Mitigation Strategy</b> |
− | | style="background: #C082FF;" | Status | + | | style="background: #C082FF;" | <b>Status</b> |
|- | |- | ||
− | | style="background: #C8BBBE;" colspan="7" | | + | | style="background: #C8BBBE;" colspan="7" | Technology & Learning Risk |
|- | |- | ||
| 1 | | 1 | ||
Line 102: | Line 102: | ||
| | | | ||
|- | |- | ||
− | | style="background: #C8BBBE;" colspan="7" | | + | | style="background: #C8BBBE;" colspan="7" | Scope Risk |
|- | |- | ||
| 5 | | 5 | ||
Line 127: | Line 127: | ||
| | | | ||
|- | |- | ||
− | | style="background: #C8BBBE;" colspan="7" | | + | | style="background: #C8BBBE;" colspan="7" | Development Risk |
|- | |- | ||
Line 141: | Line 141: | ||
| | | | ||
|- | |- | ||
− | | style="background: #C8BBBE;" colspan="7" | | + | | style="background: #C8BBBE;" colspan="7" | Schedule Risk |
|- | |- |
Revision as of 15:56, 8 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 | Lack of documentation for Kinect SDK |
|
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 |
|