Difference between revisions of "IS480 Team wiki: 2012T1 Timber Werkz Risks"
Jump to navigation
Jump to search
Line 200: | Line 200: | ||
*Use a collaborative file management software (e.g. Google Documents) to organise respective folders of the project. Consensus amongst team members to adhere to proper version labelling. | *Use a collaborative file management software (e.g. Google Documents) to organise respective folders of the project. Consensus amongst team members to adhere to proper version labelling. | ||
|style="text-align: center; color:#008000"| | |style="text-align: center; color:#008000"| | ||
− | '''Risk eliminated'''|} | + | '''Risk eliminated''' |
+ | |} |
Revision as of 00:45, 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 |