Documents  Decision Records  Risks Project Risk Register

1 Project Risk Register

This registry collects the project-level risks: everything that threatens the plan, the budget, or the team, as opposed to the product itself.

1.1 Scales

Each risk is scored on two five-point scales, written into its Probability and Impact sections:

Value Probability Impact
1 Rare Negligible
2 Unlikely Minor
3 Possible Moderate
4 Likely Major
5 Almost certain Critical

The register computes the Initial RPN as Probability times Impact. A score of 6 or below is acceptable, 15 or above is unacceptable and demands a response before further work; the band between is tolerable while a mitigation is in progress.

1.2 Lifecycle

Records move through Identified, Analysed, Mitigating, Accepted, and Closed. Every record whose current status is not Closed counts as open in the registries summary.

# Title Probability Impact Response Affected Documents Status Initial RPN
PRJR-001 Key Expertise Loss

4

4

Reduce, by spreading the knowledge: pair the senior engineer with a second developer on every architecture change, and require the deployment procedure to be executed once per release by somebody else, following the written runbook only.

 REQ-003 Mitigating 16
PRJR-002 Uncontrolled Scope Creep

4

3

Reduce: every new feature request becomes a written change request with an estimate before it is discussed; the release scope is frozen at the iteration boundary and changes are traded, not added.

 Analysed 12
PRJR-003 Estimate-Driven Schedule Overrun

3

3

Reduce: re-estimate the remaining work as focused and safe ranges, plan against the aggregated buffer rather than padding every task, and track buffer consumption weekly.

 Identified 9
PRJR-004 External Vendor Delay

2

4

Accept, with a fallback: the integration is scheduled last in the release, and a file-based import path covering the demo scenarios is kept working so a vendor slip degrades the feature instead of blocking the release.

 REQ-004 Accepted 8
PRJR-005 Mid-Release Budget Cut

2

3

Avoid: the release scope was re-cut into a funded core and an optional tail, and the core was signed off by the sponsor as protected. The cost review concluded on 07-07-2026 without touching the project.

 Closed 6