Risks and Technical Debts
This section describes the risks to the FullStaQD reference architecture and its progress. We list the risks, the corresponding countermeasures, the likelihood of the risk and the impact of it.
| Risk | Countermeasure | Likelihood | Impact |
|---|---|---|---|
| Impact of new research findings on future project work, which can drastically change the requirements for the quantum software system | By continuously taking new publications into account, maintaining close ties with research institutions, industry, and other initiatives, and regularly participating in conferences, we ensure that relevant innovations are identified early on and can be incorporated as needed. Also, the modularity of the architecture allows changes locally, which reduces the overall effort of adjusting it. | middle | middle |
| Scope Creep: Exceeding the originally agreed-upon project scope due to additional deliverables requested | The clearly defined work packages enable targeted work based on the project schedule. Regular coordination meetings within the consortium, as well as with the project sponsor and funding agency, and the monitoring of the work packages make it possible to follow the project schedule in a targeted manner and take corrective action early on if necessary. Also, thanks to standardised interfaces, components can be reused between projects so that extending the scope becomes an integration problem. | low | middle |
| Scarce resources, absence of individual stakeholders (change of employer, illness, bankruptcy) | Given the ambitious objectives, the involvement of highly qualified staff and key stakeholders is an effective way to use scarce resources efficiently and effectively and to avoid deviations from the goals. A clear description of the project goal, the approach, and the division of labor also makes it possible to successfully onboard new colleagues as needed. | middle | middle |