- TIME: needing time for content addition, iterations, bug fixes, compensating delays...
- STAFFING: missing key resources, absences, wrong team chemistry,...
- BUDGET: needing more money for resources & time.
Headers
- Chapters
-
Pre-Pro [7/8]
Risks Management
-
0 0
-
0
-

How do we manage risks?
K6 found a paper about the Risk Management process. The file is mixed up however we can re-arrange it.
Build the puzzle in less than 3min to get a bonus star























































Got it! Makes sense. Let's build the TOP 5 RISKS assessment for SpacePlan.
To do so, what is a simple and good way to classify risks?
IMPACT
PROBABILITY
Minor | Moderate | Major | Severe | |
---|---|---|---|---|
Very Likely | Medium | Medium High | High | High |
Likely | Low | Medium | Medium High | High |
Possible | Low | Medium | Medium High | Medium High |
Unlikely | Low | Low | Medium | Medium High |
Very Unlikely | Low | Low | Medium | Medium |
🎤 K6 decides to interview each team member to ask them what they think our project risks are?
We prioritized and kept 4 key risks mentionned:
🖥️
Luke

Luke's Top Risk:
STAFFING:
I may have a Math exam on day 4 of the GameJam week.
Our math teacher has not confirmed the date.
He is aware that I am participating to the GameJam and encouraged it, however the exam is mandatory.
🎨
Kira

Kira's Top Risk
QUALITY:
What if the Playtests results are not good?
The game might be too short, and maybe too easy or too hard.
We may receive so much feedback that we might not be able to address everything.
💡
Ben

Ben's Top Risk
RESSOURCES:
Playtest attendance:
What if the PlayTesters don't show up?
It is exams' season. Many are studying.
And we won't have time to book a second session.
👤👤👤
All

Mentioned by all
TIMELINE & DEADLINE:
What if we miss the submission deadline?
Some of the tasks are not easy and we have very little buffer...
Did you capture everything?
Please make sure to consult all cards.
Ok, so let's build our TOP 4 RISKS assessment and start managing risks!
ID | RISK DESCRIPTION | PROBABILITY | IMPACT | SEVERITY | OWNER | MITIGATION |
---|---|---|---|---|---|---|
R1 | Missing submission deadline | Possible | Severe | HIGH | PM | Features priorities & Gantt chart locked. Tight daily schedule monitoring. PM to package a back up version Day 4. |
R2 | Poor playtest results | Possible | Major | HIGH | PM | Playtest planned Day 4 afternoon latest. 1 day buffer for iteration & polish. |
R3 | Luke availability Day 4 due to a math exam. | Unlikely | Severe | MED | Luke | Ben to do code reviews with Luke to potentially take over Prog tasks. Getting an excuse letter from the dean to miss the exam. |
R4 | Playtesters not showing up for the Playtest | Unlikely | Moderate | LOW | PM | Individual calls to confirm attendance. Offering a gift for coming. |
We seem to have options and at least, we discussed the worst case scenarios.
I'll sleep better tonight!
Pre-Production / Mission [7/8] completed
The usual risks of a tech project are about:
Let's explore this last topic: How do we manage a budget? What are the stakes?