Project Risk Matrix

(Interactive CVE Learning Platform: Test-Driven CVE

Remediation Labs)

# Risk Type Risk Name & Probability Impact Mitigation

Description Strategy

1 Technology Local High Acceptable Mitigate:

development Standardize
environment toolsets,
variance: Python/[Link]
Differences in OS versions, and
(Windows vs. provide a unified
Linux) and tool setup guide.
versions among
students.

2 Technology Local Docker Medium Serious Contingency:

issues: Slow Use lightweight
performance or Docker
difficulty configurations or
configuring local a single shared
Docker engines local test server if
during early needed.
testing.

3 People Learning curve for High Serious Mitigate: Build

new tech: Time small Proof of
required to master Concepts (PoC)
UI and terminal and schedule
libraries (e.g., regular
[Link], React). knowledge-
sharing sessions.

4 People Overlapping task Medium Acceptable Avoid: Clearly

assignments: delineate project
Ambiguity in modules
responsibility (Frontend,
boundaries for Backend, CVE
initial feature Schema) and
development. assign explicit
ownership.
5 Organisational Supervisor Medium Acceptable Mitigate: Submit
feedback delay: concise
Waiting time for summaries and
academic targeted
supervisor questions on a
feedback on fixed weekly
documentation. schedule.

6 Organisational Academic exam High Serious Contingency:

conflicts: Project Plan intensive
work stall during work sprints
midterm exams or immediately
heavy assignment before and after
periods. examination
weeks.

7 Tools Git merge High Acceptable Mitigate: Enforce

conflicts: Code feature branch
collisions and workflow and
integration errors mandate
when merging frequent, small
student feature pull request
branches. merges.

8 Tools Library package Low Acceptable Avoid: Lock

breaking changes: stable
Updates or dependency
deprecation of versions in
open-source package files
packages during ([Link] /
development. [Link]).

9 Requirements CVE schema High Serious Avoid: Limit initial

unification scope to 3–5
complexity: simple, well-
Structural defined CVE
variance in schema
imported initial templates.
CVE vulnerability
data.

10 Requirements UI design churn: Medium Acceptable Mitigate: Finalize

Frequent frontend and approve low-
interface revisions fidelity
following early wireframes
user feedback. before starting
frontend
 implementation.

11 Estimation Underestimating High Serious Mitigate: Allocate

Frontend/Backend buffer time and
integration time: perform early
Delays in endpoint
connecting APIs integration
and terminal testing.
components.

12 Estimation Underestimating High Serious Contingency:

final report writing Write report
time: Focusing on sections
code while incrementally
neglecting SAD alongside each
documentation development
outputs. phase.