Project: | PROJECT-NAME |
---|---|
Internal Release Number: | X.Y.Z |
Related Documents: |
LINKS-TO-RELEVANT-STANDARDS
LINKS-TO-OTHER-DOCUMENTS
|
Update your project plan with any new tasks needed to mitigate risks. Use an issue tracking tool to assign responsibilities and track status of risks and tasks.
Likelihood \ Impact | Catastrophic | Critical | Significant | Marginal |
---|---|---|---|---|
Very likely | None | R-10 | R-05 R-06 | None |
Likely | None | R-02 | R-01 R-03 R-04 R-11 | None |
Unlikely | None | R-07 R-08 R-12 R-13 | R-09 | None |
Very unlikely | R-14 | None | None | None |
Risk ID | Description | Mitigation Strategy |
---|---|---|
R-01 | There are significant technical difficulties in this project. This will be a risk because only one person on our team has much experience with NEEDED-TOOL-or-TECHNOLOGY. | We will address this risk by scoping and scheduling the project to leave enough time for training and reviews. |
R-02 | We could exhaust our schedule without producing a release. The schedule for this project is very short. |
|
R-03 | The performance of the system will be significantly impacted by the decisions made during database design. None of our current team members has experience with database optimization. |
|
R-04 | We could be underestimating the effort needed for known tasks. |
|
R-05 | We could be underestimating the impact of unknown tasks. |
|
R-06 | We could be underestimating the dependencies between tasks. |
|
R-07 | We could have misunderstood the customer's requirements. |
|
R-08 | The customer could change the requirements. |
|
R-09 | We could face major difficulties with the technology chosen for this project. |
|
R-10 | We could have low quality that demands significant rework. |
|
R-11 | We could incorrectly assess our progress until it is too late to react. |
|
R-12 | We could lose resources: e.g., team members could get sick, spend time on other projects, or quit. |
|
R-13 | There may be a misalignment of stakeholder goals or expectations. |
|
R-14 | A major business change could occur: e.g., the customer goes out of business or we go out of business for reasons unrelated to this project. |
|
R-15 | SOMETHING-BAD could happen to PROJECT-ELEMENT |
|
R-16 | SOMETHING-BAD could happen to PROJECT-ELEMENT |
|
R-17 | SOMETHING-BAD could happen to PROJECT-ELEMENT |
|
R-18 | We could exhaust our RESOURCE |
|
R-19 | We could exhaust our RESOURCE |
|
R-20 | We could fail to DO-SOMETHING |
|
R-21 | We could fail to DO-SOMETHING |
|