| Risk ID | Risk (Name) | Impact | Probability | I x P | Risk Response Tasks | Re-evaluated Impact (Ir) | Re-evaluated Probability (Pr) | Ir x Pr |
|---|---|---|---|---|---|---|---|---|
| 1 | Time management issues | 5 | 4 | 20 | Applying 30% above the stipulated time for each task | 3 | 2 | 6 |
| 2 | APIs may be too demanding for Raspberry pi 4 | 4 | 5 | 20 | Change the method of performing speech recognition or uses an additional Raspberry Pi | 3 | 4 | 12 |
| 3 | Structural failure | 5 | 3 | 15 | Reprint or even redesign project parts that break or do not work properly | 4 | 2 | 8 |
| 4 | Team member quits or is fired | 5 | 3 | 15 | Reduce requirements by approximately 20% | 3 | 2 | 6 |
| 5 | Team member gets sick | 3 | 4 | 12 | Tasks scheduled will be redistributed to the backup student | 2 | 3 | 6 |
| 6 | Electronic component loss | 4 | 3 | 12 | Double check how to connect each component before powering | 4 | 2 | 8 |
| 7 | Connectivity issue between Raspberry and interface | 4 | 3 | 12 | Keep a copy of the database stored locally | 3 | 2 | 6 |
| 8 | Cloud Firestore might not be suited for the project | 4 | 3 | 12 | Purchase extra storage or store database locally in the Raspberry Pi. | 3 | 2 | 6 |
| 9 | gTTS can produce poor audio | 3 | 3 | 9 | Use the API Cloud Text-to-Speech from Google | 2 | 2 | 4 |
| 10 | Motors may not be strong enough | 3 | 3 | 9 | Replacing the motor with the stronger ones | 3 | 2 | 6 |
| 11 | Arm movement may be slow or out of sync | 3 | 3 | 9 | ||||
| 12 | Database connection may be too slow | 3 | 3 | 9 | ||||
| 13 | Google Vision API's detection may not work properly | 3 | 2 | 6 | ||||
| 14 | Chosen programming language may not be ideal | 3 | 2 | 6 | ||||
| 15 | Push button may be unprecise | 2 | 2 | 4 | ||||
| 16 | Communication issues | 3 | 1 | 3 |
The response plans are detailed in the archive below: