| RISK Description | Chance | Impact | Mitigation |
| Not enough time to develop | Very likely | Serious | Allocate extra time, work overtime, work at the weekend |
| Not enough developers | Less likely | Serious | Try to reduced wasted time and optimize planning |
| Changes to technical platform | Little-likely | Problematic | Stick to original plan, unless changes are very important |
| Sickness | Likely (autumn/winter) | Serious | Try to stay ahead of plan if possible, or have work that can be done at home in case of sickness |
| Server crash | Little | Possibly disastrous | Keep a backup on USB stick or other drive |
| Loss of Internet connection | Little | Unable to do research and testing | Move on with other tasks until connection is restored. |
| Delays due to inexperience | Medium | Deadline will be harder to keep | Make sure that project plan is at least kept. Contact supervisor in case of doubt |
| Earthquake | Extremely Faint | total disaster | Call force major / ignored |
| Fish can died | Little | Possible | |
| Octopus can died | Medium | Serious | Try to find another interesting object to movie clip |
| Our customer can change his/her idea | Little | Possible | |
| Museum can be closed | Little | Possible | |