Risk Analysis

The following are risks acknowledged and managed collectively by the group.

---

Description	Impact Level	Risk Likelihood	Mitigation Strategy	Management Strategy
Project deliverable not completed before due date	High	Low	Have at least two meetings a week where group members give progress updates on assigned tasks. If a group member is behind schedule, assign another member to assist.	Inform client immediately and estimate time of completion. Create newer, strict work plan.
Code contains bugs	Medium	High	Utilise pair-programming whenever suitable. Create test cases for every robot node and critical functionality using the gtest framework. Utilise code reviews whenever functionality is implemented.	Fix bugs.
ROS package build failure	High	Medium	Build the project every time new functionality is added, so that build failures may be pinpointed, isolated, and fixed. Ensure the build works on multiple machines.	Fix bugs.
Presenter unavailable on presentation day	High	Low	All presenters are to be briefly familiar with the entire presentation material.	Backup presenter to present in place of missing member.
Committing push to GitHub 'breaks the build'	High	Medium	Code review before any major commit pushes. Also ensure the build works on more than one machine.	Assign team member to fix bug as soon as possible, which is then committed and pushed to the remote repository.
Machine used for presentation runs into issues	High	Low	Prepare multiple 'backup' machines prior to presentations, and have them available on presentation day.	Proceed with presentation without slides.
Group member not partaking in sufficient work	Low	Medium	Project Manager to use timesheets to determine if all members are contributing to the project accordingly. If a member is not contributing sufficiently, member is to be assigned more work/assist other members. The Gantt Chart could also be used to allocate tasks evenly between group members.	Assign additional responsibilities to the team member.
Workload underestimated during planning phase	High	Medium	Have at least two meetings a week where group members give progress updates on assigned tasks.	Consider implementation alternatives and allow for flexibility.
Over promising during requirements gathering phase results in project delivery difficulties due to 'hard/impossible-to-implement' features	High	Low	Ensure all group members are familiar with ROS on a fundamental level before promising features to the client. Also project plan should seek to under promise and over deliver.	Host meeting, brainstorm as a team, and seek out alternative solutions.
Miscommunication between group members leading to different members having different ideas of what the project should be	High	Low	Have at least two meetings a week to ensure there is no overload of new information each session. Use of the Slack platform where announcements can be pushed to each group member's mobile device.	Carry out a meeting as soon as possible and resolve the confusion.
GitHub repository is wiped	High	Low	Always check before pushing local repository to remote repository.	Store backup on physical machines and reupload repository when necessary.