Using this Risk Assessment format, I will go over some circumstances this project may have faced during its progression, and how different it might've been if preventive measures were put in place.

Loss Of Data (3D Models, Unity Projects, etc.) - This seems like something of an unpredictable circumstance as I hear of projects being ruined through this happening all the time so it definitely seems very possible, because of this I'd label this a high risk problem due it being quite catastrophic to the project. With measures such as backing up work however and working from GitHub this nullifies the severity of the issue and makes it a rare occurrence so I'd say by making smart decisions you can make this very low risk.
Lazy Team Member - If a team member ever decided to go inactive or drop out this can be either low risk or catastrophic depending on the work that individual were required to do. I don't really feel there is a way to actively lessen the possibility of this happening either apart from being smart with who you pick from the get, make sure your colleagues are reliable and have good references.
Running Out Of Time - Running out of time is normally a major risk because it'd imply you're working towards some kind of of release date or course deadline like we are. But with extensive Research and Development and making sure the team is very aware of what do and things like software have been accounted for and prepared then this is quite low risk.
Comentários