Risk Management - IP-2025/waves-of-the-fallen GitHub Wiki
Risk Management Plan
First Iteration
| ID | Risk Description | Category | Probability | Impact | Risk Level (PxI) | Priority | Mitigation Strategy |
|---|---|---|---|---|---|---|---|
| R1 | Poor communication and coordination | Team | High | Medium | 6 (3x2) | 🟠 Medium | Use Discord, set communication guidelines, assign leads. |
| R2 | Unclear roles and responsibilities | Team | Medium | Medium | 4 (2x2) | 🟠 Medium | Define clear roles and document them |
| R3 | Unfamiliarity with chosen technologies | Technical | Medium | High | 6 (2x3) | 🟠 Medium | Help each other, skillbase in wiki with tutorials. |
| R4 | Inadequate time estimation for development | Planning | High | Medium | 6 (3x2) | 🟠 Medium | Correct sprints, buffer time. |
| R5 | Feature creep (Scope expansion) | Scope | Medium | High | 6 (2x3) | 🟠 Medium | New features into backlog, work on important issues (MVP's) first |
| R6 | Late start of testing and bug fixing | Quality | Medium | High | 6 (2x3) | 🟠 Medium | Integrate testing into each sprint, QA every issue |
| R7 | Version control conflicts / loss of work | Technical | Medium | High | 6 (2x3) | 🟠 Medium | Enforce Git best practices (feature branches, pull requests, code reviews). |
| R8 | No centralized documentation | Organization | Medium | Medium | 4 (2x2) | 🟠 Medium | Use only GitHub Wiki. |
| R9 | Legal issues with third parties | Compliance | Low | High | 3 (1x3) | 🟡 Low | Only use open-source/commercial-use assets; verify licenses. |
Second Iteration
| ID | Risk Description | Category | Probability | Impact | Risk Level (PxI) | Priority | Mitigation Strategy |
|---|---|---|---|---|---|---|---|
| R1 | Poor communication and coordination | Team | High | High | 9 (3x3) | 🔴 High | Use Discord, set communication guidelines, assign leads. |
| R2 | Unfamiliarity with chosen technologies | Technical | Medium | Medium | 4 (2x2) | 🟠 Medium | Help each other, skillbase in wiki with tutorials. |
| R3 | Inadequate time estimation for development | Planning | High | High | 9 (3x3) | 🔴 High | Correct sprints, buffer time. |
| R4 | Feature creep (Scope expansion) | Scope | High | Medium | 6 (3x2) | 🟠 Medium | New features into backlog, work on important issues (MVP's) first |
| R5 | Late start of testing and bug fixing | Quality | High | High | 9 (3x3) | 🔴 High | Integrate testing into each sprint, QA every issue |
| R6 | Legal issues with third parties | Compliance | Low | Very High | 3 (1x3) | 🟡 Low | Only use open-source/commercial-use assets; verify licenses. |
Changes:
- R1 higher impact -> high priority
- R2 not present anymore
- R3 lower impact
- R4 higher impact + probability -> high priority
- R5 lower impact + higher probability
- R6 higher impact -> high priority
- R7 not present anymore
- R8 not present anymore
- R9 higher impact
Third Iteration
| ID | Risk Description | Category | Probability | Impact | Risk Level (PxI) | Priority | Mitigation Strategy |
|---|---|---|---|---|---|---|---|
| R1 | Poor communication and coordination | Team | Medium (2) | High (3) | 6 (2x3) | 🟠 Medium | Use Discord, set communication guidelines, assign leads. |
| R2 | Unfamiliarity with chosen technologies | Technical | Medium (2) | Medium (2) | 4 (2x2) | 🟠 Medium | Help each other, skillbase in wiki with tutorials. |
| R3 | Inadequate time estimation for development | Planning | Medium (2) | High (3) | 6 (2x3) | 🟠 Medium | Correct sprints, buffer time. |
| R4 | Feature creep (Scope expansion) | Scope | Medium (2) | High (3) | 6 (2x3) | 🟠 Medium | New features into backlog, work on important issues (MVP's) first. |
| R5 | Late start of testing and bug fixing | Quality | High (3) | High (3) | 9 (3x3) | 🔴 High | Integrate testing into each sprint, QA every issue. |
| R6 | Poor code architecture | Technical | Very High (4) | Critical (5) | 20 (4x5) | 🔴 High | Enforce design patterns, peer reviews, and conduct architecture reviews. |
Changes:
- R1: Probability reduced, impact unchanged → Lowered risk level to Medium.
- R2: Re-added; probability and impact lower → Medium priority.
- R3: Probability and impact lower → Risk level reduced to Medium.
- R4: Probability lower, impact unchanged → Medium priority remains.
- R5: Probability higher, impact unchanged → High priority.
- R6: Newly identified risk with Very High priority due to critical impact and very high probability.
- Legal issues: No longer considered a risk.
Forth Iteration
Original Values
| ID | Risk Description | Category | Probability | Impact | Risk Level (PxI) | Priority | Mitigation Strategy |
|---|---|---|---|---|---|---|---|
| R1 | Poor communication and coordination | Team | Medium (2) | Medium (2) | 4 (2x2) | 🟡 Low | Use Discord, set communication guidelines, assign leads. |
| R2 | Unfamiliarity with chosen technologies | Technical | Medium (2) | Medium (2) | 4 (2x2) | 🟡 Low | Help each other, skillbase in wiki with tutorials. |
| R3 | Inadequate time estimation for development | Planning | High (3) | High (3) | 9 (3x3) | 🔴 High | Use proper sprint planning and buffer time. |
| R4 | Feature creep (Scope expansion) | Scope | Medium (2) | High (3) | 6 (2x3) | 🟠 Medium | Add new features to backlog, prioritize MVP items. |
| R5 | Late start of testing and bug fixing | Quality | High (3) | High (3) | 9 (3x3) | 🔴 High | Integrate testing into each sprint, QA every issue. |
| R6 | Poor code architecture | Technical | High (3) | High (3) | 9 (3x3) | 🔴 High | Enforce design patterns, conduct peer and architecture reviews. |
Changes (compared to Third Iteration – Original Values)
- R1: Lower probability → Risk level decreased from Medium to Low.
- R2: No change in values → Remains Low priority.
- R3: Same values as before → Still High priority.
- R4: Lower probability → Risk level dropped from High to Medium.
- R5: No change → Remains High priority.
- R6: Probability and impact reduced → Risk level dropped from 20 to 9 → Still High, but less critical.
- Legal issues: Still not present in this iteration.
Scaled Values (+1 on all Probabilities and Impacts)
| ID | Risk Description | Category | Probability | Impact | Risk Level (PxI) | Priority | Mitigation Strategy |
|---|---|---|---|---|---|---|---|
| R1 | Poor communication and coordination | Team | High (3) | High (3) | 9 (3x3) | 🔴 High | Use Discord, set communication guidelines, assign leads. |
| R2 | Unfamiliarity with chosen technologies | Technical | High (3) | High (3) | 9 (3x3) | 🔴 High | Help each other, skillbase in wiki with tutorials. |
| R3 | Inadequate time estimation for development | Planning | Very High (4) | Very High (4) | 16 (4x4) | 🔴 High | Use proper sprint planning and buffer time. |
| R4 | Feature creep (Scope expansion) | Scope | High (3) | Very High (4) | 12 (3x4) | 🔴 High | Add new features to backlog, prioritize MVP items. |
| R5 | Late start of testing and bug fixing | Quality | Very High (4) | Very High (4) | 16 (4x4) | 🔴 High | Integrate testing into each sprint, QA every issue. |
| R6 | Poor code architecture | Technical | Very High (4) | Very High (4) | 16 (4x4) | 🔴 High | Enforce design patterns, conduct peer and architecture reviews. |
Changes (Scaled +1 Compared to Third Iteration)
- All risks are now High priority due to elevated values.
- R1 & R2: Up from Medium/Low to High risk level (9 points).
- R3: Risk level increased from 9 to 16, marking it as very critical.
- R4: Risk level increased from 6 to 12, now in High range.
- R5 & R6: Already high, now maximum priority risks with a level of 16.
- Highlights the impact of scaling on risk prioritization: even smaller risks become major if risk perception increases.
Fifth Iteration
| ID | Risk Description | Category | Probability | Impact | Risk Level (PxI) | Priority | Mitigation Strategy |
|---|---|---|---|---|---|---|---|
| R1 | Poor communication and coordination | Team | Medium (2) | High (3) | 6 (2x3) | 🟠 Medium | Use Discord, set communication guidelines, assign leads. |
| R2 | Unfamiliarity with chosen technologies | Technical | High (3) | High (3) | 9 (3x3) | 🔴 High | Help each other, maintain a shared knowledge base with tutorials. |
| R3 | Inadequate time estimation for development | Planning | Very High (4) | Very High (4) | 16 (4x4) | 🔴 High | Improve sprint planning, include time buffers, regularly review workload. |
| R4 | Feature creep (Scope expansion) | Scope | High (3) | High (3) | 9 (3x3) | 🔴 High | Log new feature requests in backlog, prioritize MVP functionality first. |
| R5 | Late start of testing and bug fixing | Quality | Very High (4) | Very High (4) | 16 (4x4) | 🔴 High | Integrate automated and manual testing into all sprints, track bugs early. |
| R6 | Poor code architecture | Technical | High (3) | High (3) | 9 (3x3) | 🔴 High | Define architectural guidelines early, enforce code reviews and refactoring cycles. |
| R7 | Online multiplayer not working properly until release date | Technical | Very High (4) | Very High (4) | 16 (4x4) | 🔴 High | - |
Changes
- R1: Impact increased from 2 → 3 → Risk level increased from 4 → 6 (Low → Medium).
- R2: Probability increased from 2 → 3 → Risk level increased from 4 → 9 (Low → High).
- R3: Probability and impact increased from 3 → 4 → Risk level increased from 9 → 16 (still High, but more severe).
- R4: Probability increased from 2 → 3 → Risk level increased from 6 → 9 (Medium → High).
- R5: Same as before → remains at 16 (High).
- R6: Same as before → remains at 9 (High).
- R7: New risk added to reflect technical uncertainty with online features. Assigned Very High severity.
Sixth Iteration (Last)
| ID | Risk Description | Category | Probability | Impact | Risk Level (PxI) | Priority | Mitigation Strategy |
|---|---|---|---|---|---|---|---|
| R1 | Inadequate time estimation for development | Planning | Very High (4) | Very High (4) | 16 (4x4) | 🔴 High | Improve sprint planning, include time buffers, regularly review workload. |
| R2 | Late start of testing and bug fixing | Quality | Very High (4) | Very High (4) | 16 (4x4) | 🔴 High | Integrate automated and manual testing into all sprints, track bugs early. |
| R3 | Online multiplayer not working until release date | Technical | Very High (4) | Very High (4) | 16 (4x4) | 🔴 High | Create reproducible multiplayer tests early, simulate real usage cases on test servers. |
| R4 | User experience is lacking | Quality | High (3) | High (3) | 9 (3x3) | 🔴 High | Conduct regular UX testing with real users, prioritize feedback-driven improvements. |
Changes Compared to Fifth Iteration
-
Removed Risks:
- R1 Poor communication and coordination → no longer considered a risk.
- R2 Unfamiliarity with chosen technologies → removed.
- R4 Feature creep (Scope expansion) → removed.
- R6 Poor code architecture → removed.
-
R3 (Inadequate time estimation): Same values as in Fifth Iteration → still 16 (High).
-
R5 (Late testing and bug fixing): Same values → still 16 (High).
-
R7 (Online multiplayer): Wording adjusted to reflect full-release concern → same severity.
-
R8 (User experience is lacking): Newly added risk, significant as it may block release-readiness.