Risk Analysis
| Scenario | This will affect... | Likelihood | Impact | Mitigation | Has this occurred? | On occurrence.../Mitigation monitoring |
|---|---|---|---|---|---|---|
| Client changes requirements | Project, requirements | Very Likely | Moderate | Structure project and its code to be as extendable as possible, in anticipation for new unexpected features to be added | Yes | 2024-03-15: The client changed the requirements of the project such that each territory's name, and each path between each territory, should be changeable. They also requested implementation of a collection of mission cards containing objectives for each player to attempt to complete during a play session. |
| Team member is taken ill or is otherwise unable to fulfil their responsibilities | Project, people | Possible | Serious | Appoint members of team to pick up slack from missing member's role | No | 2024-02-21: Ricardo has many other academic responsibilities and might not be able to complete responsibilities for first sprint. Mei will take on his tasks if this occurs. 2024-03-14: Mei has been taken ill for the majority of this week, preventing her from contributing to the wiki and working on our planned entity relationship diagram. 2024-03-28: Due to an unexpected bereavement, Charlie disappeared for several weeks and was unable to contribute to the project. Her role was temporarily taken over by John and Ricardo for that span of time. 2024-04-24: Jo made the executive decision during the second meeting of sprint 3 to expel Charlie from the team due to a justified but obstructive and persistent absence from sprint meetings and contributing to the repository. 2024-04-25: John alerted the team at 7am notifying us that they had just regained consciousness after emergency surgery and, while they may be put out of action for a little while, they hope to contribute in the final stretch before the deadline. If they are unable to, then someone else will have to take over their current task of developing a computer-controlled player, which is one of the main requirements of the project. 2024-04-26: John updated the team and notified everyone that their recovery process was not progressing as smoothly as they had hoped, and would likely be unable to contribute to the project any further, meaning that their responsibilities will have to be managed by another team member for the final week of the final sprint. |
| Team member accidentally commits to main in repo | Project | Likely | Moderate | Instil clear access rights for team members, and distinguish from team leader, who will approve and deny pull requests. Alternatively, use project history to revert incorrect changes | No | N/A for now |
| Team member accidentally force pushes to main and wipes history of repo | Project | Unlikely | Catastrophic | Instil clear access rights for team members, and distinguish from team leader, who will approve and deny pull requests | No | N/A for now |
| Team member takes idea\asset without citing source | Project, people | Likely | Serious | Cite URLs or include a written explanation in all code and documentation stating where the idea or asset was taken from | No | N/A for now |
| Sprint takes longer than planned | Project | Likely | Serious | Ensure, by all means necessary, that the current sprint is finished by the next meeting. Additionally, arrange more meetings than usual for tighter collaboration | Yes | 2024-03-07: Sprint 1 took a week longer than planned since the frontend and backend had not yet been connected and we consequently didn't have a working prototype just yet |
| Two sprints in a row take longer than planned | Project | Possible | Catastrophic | Seriously re-evaluate distribution of workload in order to find reason for such a sustained delay | No | N/A for now |
https://excalidraw.com/#room=1851bcfc9176792aff9a,kMrRJ1w7mM6gC4j7od8n8w