##Risk Description

= The Library loses interest in DOMS =

## Detailed description of this risk and its possible implications.
## E.g. If one of the car's tires suffers a puncture, we may run off the road.

Note that we think of the entire library, including boss level

The DOMS currently enjoys a high level of interest in the library, since the identified problems are present in the library.

However we need to keep that level of interest.

== When to react? ==

## When must we respond to the risk? E.g. When the event occurs or already when we see the warning signs?
## E.g. We must react if we hear a hissing sound.
We should react if we start to see a trend towards cutting in the resources for implementing DOMS, or if we see trends towards introducing alternate solutions to DOMS.

== Reaction ==

## Detailed description of how to react on the risk and which actions to take, if it is imminent.

## There exists 4 basic reactions:
## 1: Accept the risk.
## 2: Eliminate the cause to the risk.
## 3: Mitigate the probability or the consequence of the risk.
## 4: Delegate the risk to another party, e.g. by outsourcing it or take out insurance for it.

We can mitigate the consequences by communication of importance of DOMS
## E.g. We accept the risk and change the tire if we suffer a puncture.
Communication is again the key issue. We need to communicate the importance of DOMS, and why DOMS is the right way to solve the problems we face.

== Responsible Persons ==

The below persons are responsible for continuously monitoring and acting on this risk:

## Add a bullet list with links to the wiki pages of the responsible persons here:
## E.g.
## * [:JohnDoe: John Doe]