This document lists potential risks that may occur during a game development project and proposes solutions to address each risk. It identifies risks such as losing work, code or sprites not working as expected, objects having errors, rooms not changing as intended, sounds not working, and tasks or systems going offline. Corresponding solutions are provided such as creating backups, finding and fixing problems in code, changing image or sound types, adding new objects to change rooms, and finding alternative places to work if primary tools or locations become unavailable.

1. Risk Solution Probability of
Risk
Severity of risk
Lose Work Create backups L` H
Code doesn’t work Go through the code to
find the problem
H M
Sprites don’t work Redo or change the image
type when importing
L M
Objects have errors Game maker tells you
what the problem is, so
you know where to fix
H M
Rooms don’t change Create a new object to
change the room on a
timer
M H
Sounds aren’t working Change the sound type or
change it to
uncompressed
L L
Tasks aren’t
completed on time
Remain to the schedule M H
Piskellapp is offline Do other work until it is
online
L L/M
D12 isn’t open Find somewhere else to
work
L M/H
Systems go offline Do some written work for
later to be written up
L M/H