HeaderSIS.jpg

IS480 Team wiki: 2014T1 Happy Sounds Risk Management

From IS480
Jump to navigation Jump to search

Happysounds logo.png

HomeButton.png HOME   Glyphicons 042 pie chart.png PROJECT OVERVIEW   Calendaricon.png PROJECT MANAGEMENT   Tableicon.png DOCUMENTATION   Aboutus.png ABOUT US
PROJECT SCHEDULE   METHODOLOGY   METRICS MANAGEMENT   RISK & ISSUE MANAGEMENT   MEETING MINUTES


Risk Management

HS risk matrix.jpg
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

  • Communicate with the clients via HipChat to update them on the progress and to get their feedback

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

  • Regular communication with the clients to keep ourselves informed about the latest status in the firm

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

  • Communicate with all stakeholders and ensure that they are willing to accept the risk involve in our project
  • Team to inform/verify with Carousell before making any changes to their existing APIs involving their live database

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

  • Review and re-estimate project schedule and the time required to complete the individual task
  • Gather feedback from all team members especially the developers to ensure that they have sufficient time to complete the application function

Project Management Risk

Team is unsure of the project progress and if the project is behind/ahead of planned schedule

Low

Medium

C

  • Ensure that metrics are up-to-date to efficiently & accurately track project/team progress
  • Hold regular meeting and communicate frequently among the team to ensure that everyone is aware of the current status & project's progress

Technical Risk

Team is not proficient in the technologies/resources used for developing the project

  • Python, Flask-SQL Alchemy, PostgreSQL & Flask

Medium

High

A

  • Each team member to research on technology/resources used for developing project & learn from team members that are proficient

Technical Risk

Carousell co-founders may implement new technologies that the team has to familiarize themselves with within the project schedule

Medium

High

A

  • Constantly communicate with client to know their development plans
  • Research on related technologies for a better grasp in case any changes are implemented

Resource Risk

Team is unsure of which resources can be reused from the mobile application that Carousell developed

Medium

Low

C

  • Team to discuss internally and decide which are the resource to reuse that will benefit us and Carousell
  • Team to communicate with Carousell co-founders and find out if they allow our team to leverage on their current resources

Resource Risk

Unexpected technology issues (laptop crashes)

Low

High

B

  • Ensure that the latest documentations and codes are back up in the repository that team uses (GitLab)

Human Risk

Team member is not available due to illness or unforeseen circumstances

Low

Medium

C

  • Each member to have primary & secondary role
  • Back up member to take over the role if such circumstances arise


Issue Management