Service ownership #
TLDR: All services running in our environments have registered ownership
Rationale: In a diverse software landscape it is essential everyone knows who is responsible for maintaince and support
Background #
In any governance system, risks are managed by controls. But humans are ultimately responsible.In this context there are many reasons to keep a register of service ownership in diverse software landscapes:
- Knowlege: Who knows how this is supposed to work? How can I get help with this system?
- Incident: Alerts are firing for a service, who do I contact? What has changed lately?
- Audit: who is reponsible that the DevOpsCTL process is followed for this service?