Risk Assessment
Two ways to manage and identify key risks and issues in the project we are using are Trello dependency links and a Risk assessment table.
On our Trello board linking tasks via dependency links is a way to highlight to each member of the project whether or not the task they are working on is blocking or linked to another members task.
Another method for highlighting issues and risks that aren't necessarily on Trello cards/tasks is a Risk Assessment table. Here each risk is given an ID and description and then a probability and impact rating (Low, Medium, High). Risks with High in both categories are raised at each meeting to assess if the risk has been addressed. A column is also added to highlight which group of people on the project the risk most affects; Programmers, Artists, Level Designers, e.g.
| No. | Description | Probability | Impact | Affects |
|---|---|---|---|---|
| 1 | ||||
| 2 | Needing to learn new tools to complete certain aspects | Low | High | Everyone |
| 3 | Constant design changes | High | High | Everyone |
| 4 | Working on things that are out of scope | Low | High | Everyone |
| 5 | Working and prioritising the incorrect tasks | Low | Low | Everyone |
| 6 | Not testing enough to be sure features are needed or not | Medium | Low | Programmers |
| 7 | Unsure of what features are still needed | Medium | High | Designers |
| 8 | Covid and motivation issues | High | Medium | Everyone |
| 9 | Not ensuring the codebase is well kept | Medium | Medium | Programmers |
| 10 | Only being able to have 1 person work on the island design at a time | High | Medium | Designers |
| 11 | Members needing time for other subjects | High | Medium | Everyone |