Risk analysis¶

Potential risks we may encounter in our project:

• 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.
  Method of risk elimination : It is crucial to establish a clear project scope and maintain effective communication with stakeholders to prevent scope creep.

• 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.
  Method of risk elimination: Thoroughly test the integration process to ensure that the software works correctly.

• 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
  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.
  Method of risk elimination: Cross-train team members + Plan project timelines with some buffer

• 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.
  Method of risk elimination: Well-defined set of requirements and effective communication with stakeholders

• 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.
  Method of risk elimination: Learning the programming language before starting the project and regular internal knowledge sharing meetings.