Risk analysis » Historie » Verze 1
Václav Šíma, 2023-03-25 10:04
| 1 | 1 | Václav Šíma | h1. Potential risks |
|---|---|---|---|
| 2 | |||
| 3 | Potential risks we may encounter in our project: |
||
| 4 | |||
| 5 | * *Scope creep*: Scope creep refers to the tendency for project requirements to expand beyond the original scope, which could lead to delays and decreased code quality. To eliminate this risk. |
||
| 6 | *Method of risk elimination* : It is crucial to establish a clear project scope and maintain effective communication with stakeholders to prevent scope creep. |
||
| 7 | |||
| 8 | * *Integration risk*: When integrating different software components or third-party systems (for instance OpenSim or other libraries used in our project), there can be compatibility issues that can result in errors or system crashes. |
||
| 9 | *Method of risk elimination*: Thoroughly test the integration process to ensure that the software works correctly. |
||
| 10 | |||
| 11 | * *Sickness of a developer*: Depending on the severity of the illness, the developer may be unable to work for an extended period, which can impact project timelines. Also if |
||
| 12 | the sick developer is the only person with knowledge of a critical part of the software project, it can be challenging to transfer that knowledge to another team member. This can impact the quality and progress of the project. |
||
| 13 | *Method of risk elimination*: Cross-train team members + Plan project timelines with some buffer |
||
| 14 | |||
| 15 | * *Requirements ambiguity* : Requirements ambiguity refers to unclear or incomplete requirements that can lead to misunderstandings, errors, or omissions in the software design and development process. |
||
| 16 | *Method of risk elimination*: Well-defined set of requirements and effective communication with stakeholders |
||
| 17 | |||
| 18 | * *Lack of technical expertise*: The project is implemented in C++ with which none of the developers in our team has any experience. If the development team lacks the necessary expertise, it can result in errors, bugs, and poor-quality software. |
||
| 19 | *Method of risk elimination*: Learning the programming language before starting the project and regular internal knowledge sharing meetings. |