Risk Management

Risk	Severity	Likelihood	Mitigation Plan
Unfamiliar with Version Control	4	4	Complete Git course on Blackboard to be familiar with how Git works and what to do for commits, pushed, pulls and merges. The people already familiar with Git will assist those who are to provide assistance on a human level. More friendly Git applications such as Git Desktop and Git Kraken will be used instead of Git Bash for new users.
Language Barrier	4	5	Speak slowly and use simple words so everyone can be on the same page as to what work needs to be done for the project. A translate app such as Google translate will be used when there is complete misunderstanding.
Git Version Control Issues	5	1	Develop and Master branches are locked so code cannot be directly uploaded, to prevent precious work being destroyed. Instead, feature branches will be created for each person working on a different branch, such that when they are finished, they can create a merge request into develop branch. To be extra safe, force pushes are not allowed and a merge request must be approved by another team member.
Time Constraint	5	5	Have stand-up meetings everyday to understand where everyone is at in terms of progress. Try to get the minimum demonstration features working in the short time frame. Always keep communicating between team members to keep everyone up to date.
New Technologies	2	4	Many of us have never used Android Studio before. However, since Android Studio is quite similar to IntelliJ in terms of UI and the Java language; we will use our previous skills along with research along the way to be successful in the project.
New Working Environment	2	5	Along with the language barrier, working away from home can be a struggle. The best way we can deal with this is to adapt to the new environment and support each other as best as possible. The Wi-Fi is also a big issue associated with the new working environment. To solve this, we will simply try, try and try again; also work on tasks not requiring internet in the meantime. Additionally, personal hotspots will be utilised as a last resort.
Sickness	4	4	In the event that a team member gets sick, the sick team member will try to rest up and recover as soon as possible whilst attempting to work from their dorm. Team members well at SOVO will continue to work on their parts and will split the sick team member’s work if it’s unable to be done.

The Severity and Likelihood ratings are from 1 to 5 with 1 as least (severe/ likely) and 5 as most (severe/ likely).