27 lines
1.7 KiB
Markdown
27 lines
1.7 KiB
Markdown
- #+BEGIN_QUOTE
|
||
Title — Erkennung und Meldung von Red-Flags
|
||
|
||
User Story Description
|
||
|
||
Als KI-Pipeline möchte ich besonders kritische Beiträge (Red-Flags) automatisiert erkennen und melden.
|
||
|
||
Prerequisites which have to be fullfilled by the customer — If there are things which have to be provided by the customer in order to start working on this user story, these things have to be listed here.
|
||
|
||
Acceptance criterias
|
||
|
||
Es müssen übergreifende Red-Flag-Themen (z.B. Diskriminierung, Sexismus, Rassismus, Gefahr für Leib und Leben) als Basis-Themen definiert und erkannt werden.
|
||
|
||
Kunden müssen die Möglichkeit haben, individuelle Red-Flags oder Krisenthemen zu definieren.
|
||
|
||
Ein Alert bzw. eine Red-Flag muss innerhalb von 12 Stunden identifiziert und abgebildet sein.
|
||
|
||
customer specific implementation? — Should the user story only be available for a subset of customers? If so, for which ones?
|
||
|
||
Technical solution details — This field has to be only filled in by developers. This field is a fine granular description of steps which have to be done to implement the user story so that the effort can be estimated more precisely and in best case there won’t be any additional questions while implementing the user story.
|
||
|
||
Risk analysis — This field has to be only filled in by developers. Potential risks associated with the feature have to be listed and contractually secured by the company so that the customer can no longer claim anything without additional payment.
|
||
|
||
Do continuous efforts for operation arise? — This field has to be only filled in by developers.
|
||
|
||
Should the software architect be consulted? — e.g. if central components have to be modified
|
||
#+END_QUOTE |