You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disclaimer: this is not the real content, not even the draft content.
21
+
It is used for monitoring/steering our process automation effort.
22
+
23
+
Automation Status via Process Requirement Table
24
+
***********************************************
25
+
26
+
All process requirements should be labelled with the priorization of automation implementation:
27
+
28
+
- A label "manual" means nothing to do, because it must be fulfilled manually (e.g. by filling attributes).
29
+
- A label "done_automation" means nothing to do, because it already works. Note that in docs-as-code repository there are tool requirements linking to the process requirements with an "Implemented" attribute.
30
+
- A label "prio_*_automation" means the prio 1, 2, ... labelled requirement shall be implemented in this order. Prio 1 is everything we need for the re-audit, prio 2 could be done manually as a fallback, prio 3 is nice to have ...
0 commit comments