Difference between revisions of "IS480 Team wiki: 2012T1 Timber Werkz Risks"
Jump to navigation
Jump to search
Line 56: | Line 56: | ||
|- | |- | ||
− | ! scope="row" | '''1.1''' | + | ! scope="row" | |
+ | '''1.1''' | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
*Many change requests expected from client as Casting3 application is built from scratch | *Many change requests expected from client as Casting3 application is built from scratch | ||
Line 72: | Line 73: | ||
|- | |- | ||
− | ! scope="row" | '''1.2''' | + | ! scope="row" | |
+ | '''1.2''' | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
*Overestimation of Man Days for a Chapter | *Overestimation of Man Days for a Chapter | ||
Line 93: | Line 95: | ||
|- | |- | ||
− | ! scope="row" | '''2.1''' | + | ! scope="row" | |
+ | '''2.1''' | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
*Business requirements of the Casting3 application might be unclear | *Business requirements of the Casting3 application might be unclear | ||
Line 108: | Line 111: | ||
|- | |- | ||
− | ! scope="row" | '''2.2''' | + | ! scope="row" | |
+ | '''2.2''' | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
*Team’s design of the systems UI might not meet the expectations of the client’s designer | *Team’s design of the systems UI might not meet the expectations of the client’s designer | ||
Line 129: | Line 133: | ||
|- | |- | ||
− | ! scope="row" | '''3.1''' | + | ! scope="row" | |
+ | '''3.1''' | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
*Insufficient manpower during Milestone 1 as three members are overseas (summer studies and community service) | *Insufficient manpower during Milestone 1 as three members are overseas (summer studies and community service) | ||
Line 144: | Line 149: | ||
|- | |- | ||
− | ! scope="row" | '''3.2''' | + | ! scope="row" | |
+ | '''3.2''' | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
*Conflict amongst team members in terms of working behviours and perspectives | *Conflict amongst team members in terms of working behviours and perspectives |
Revision as of 00:42, 6 August 2012
HOME | PROJECT DESCRIPTION |
PROJECT MANAGEMENT |
DOCUMENTATION | RESOURCES | LEARNING EXPERIENCES |
SCHEDULE & SCOPE | MILESTONES | METRICS | RISKS & MITIGATION | PROJECT FRAMEWORK |
Risks & Mitigation
The following diagram shows the risks and mitigation table for the project.
S/N | Risk Description | Impact | Impact Level (High/Med/Low) |
Likelihood (High/Med/Low) |
Mitigation Strategy | Status |
---|---|---|---|---|---|---|
1 |
Project Management | |||||
1.1 |
|
|
High |
High |
|
Mitigation strategy |
1.2 |
|
|
High |
High |
|
Mitigation strategy |
2 |
Business and IT Management | |||||
2.1 |
|
|
High |
Medium |
|
Mitigation strategy |
2.2 |
|
|
High |
High |
|
Mitigation strategy |
3 |
Team Management | |||||
3.1 |
|
|
Medium |
Medium |
|
Risk eliminated |
3.2 |
|
|
Medium |
Low |
|
Mitigation strategy |
4 |
Knowledge & Content Management | |||||
4.1 |
|
|
Medium |
Medium |
|
Mitigation strategy |
4.2 |
|
|
Medium |
Low |
|
Risk eliminated |