IS480 Team wiki: 2011T1 Aperture - Main - Project Management - Risk Management - Risk Analysis
Contents
Project Management
Risk Management
Risk Analysis - Project Elaboration Phase
Potential Risks Ahead | |||||
1. Scope Risk | |||||
Risk Statement | Risk Rating (Derived) |
Likelihood (High/Med/Low) |
Impact Level (High/Med/Low) |
Mitigation Strategy | Comments |
---|---|---|---|---|---|
|
A |
High |
Medium |
|
Partially mitigated. As we are building the application from scratch, we have discussed with the client and come up with a prioritized list of functionalities to complete. |
3. Resource Risk | |||||
Risk Statement | Risk Rating (Derived) |
Likelihood (High/Med/Low) |
Impact Level (High/Med/Low) |
Mitigation Strategy | Comments |
|
B |
Medium |
Medium |
|
Some of the risk has been mitigated. If we are stuck with some technical difficulties, we will post questions on forums such as Google groups, instead of relying on one person to complete the task for us. However, if we are behind schedule, we will have to re-allocate manpower. |
4. Technical Risk | |||||
Risk Statement | Risk Rating (Derived) |
Likelihood (High/Med/Low) |
Impact Level (High/Med/Low) |
Mitigation Strategy | Comments |
|
A |
Medium |
High |
|
Currently, there are some issues . |
Resolved Risks | |||||
1. Scope Risk | |||||
Risk Statement | Risk Rating (Derived) |
Likelihood (High/Med/Low) |
Impact Level (High/Med/Low) |
Mitigation Strategy | Comments |
---|---|---|---|---|---|
|
B |
Low |
Low |
|
Mitigated. The paper prototype was very useful in ensuring that we understood the requirements of the client. |
|
A |
Low |
Low |
|
Mitigated. We have prioritized the functions in the client's requirement list, before coming to an agreement with him. |
2. Schedule Risk | |||||
Risk Statement | Risk Rating (Derived) |
Likelihood (High/Med/Low) |
Impact Level (High/Med/Low) |
Mitigation Strategy | Comments |
|
C |
Low |
Low |
|
Partially mitigated. Team members have been assisting the Project Manager to check on the schedule, as well as consistently completing their tasks. |
|
C |
Low |
Low |
|
Mitigated. We learnt to compromise about how each team prioritizes this project. The Project Manager will continue to ensure that each member completes his tasks |
4. Technical Risk | |||||
Risk Statement | Risk Rating (Derived) |
Likelihood (High/Med/Low) |
Impact Level (High/Med/Low) |
Mitigation Strategy | Comments |
|
A |
Low |
Low |
|
Mitigated. We have allocated time for each member to learn the new technology. In addition, we are able to post questions on online forums when we encounter issues |
|
A |
Low |
Low |
|
Mitigated, as we started developing from scratch. |