IS480 Team wiki: 2014T1 Happy Sounds Risk Management
HOME | PROJECT OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION | ABOUT US |
PROJECT SCHEDULE | METHODOLOGY | METRICS MANAGEMENT | RISK & ISSUE MANAGEMENT | MEETING MINUTES |
Risk Management
Risk Type | Risk Event | Likelihood | Impact | Category | Mitigation |
---|---|---|---|---|---|
Client Management Risk |
Difficult to meet client as Carousell is now rapidly expanding into SEA region. As a result, our clients are very busy and might remain abroad for long periods |
High |
High |
A |
|
Client Management Risk |
Carousell co-founders makes major changes to project requirements such as Offers and Leaving reviews after transaction. This leads us to rescope our project and to ensure that both mobile and web application are in sync. |
High |
High |
A |
|
Client Management Risk |
Carousell co-founders are uncomfortable with us using their live database, calling and modifying existing APIs as it might affect their business operations |
Low |
High |
B |
|
Project Management Risk |
Team is unsure of the time required to complete each task/functionality & which task should be allocated more time |
Medium |
Medium |
B |
|
Project Management Risk |
Team is unsure of the project progress and if the project is behind/ahead of planned schedule |
Low |
Medium |
C |
|
Technical Risk |
Team is not proficient in the technologies/resources used for developing the project
|
Medium |
High |
A |
|
Technical Risk |
Carousell co-founders may implement new technologies that the team has to familiarize themselves with within the project schedule |
Medium |
High |
A |
|
Resource Risk |
Team is unsure of which resources can be reused from the mobile application that Carousell developed |
Medium |
Low |
C |
|
Resource Risk |
Unexpected technology issues (laptop crashes) |
Low |
High |
B |
|
Human Risk |
Team member is not available due to illness or unforeseen circumstances |
Low |
Medium |
C |
|