DevOps is the way a group of people, who typically hold different roles, skills, and responsibilities, work together to achieve some goal. It’s a collaboration protocol, and asking one person or one team to “do all the collaborating” makes no sense. Put another way, if you adopted DevOps because you had a silo problem, creating a new “DevOps” silo is unlikely to be an effective solution. (1)
Widely accepted definitions of DevOps:
CALMS (Culture, Automation, Lean, Measurement, Sharing)
The Three Ways (Flow aka "Systems Thinking", Amplify Feedback Loops, Continual Experimentation and Learning)
Accelerate metrics (Lead time, deployment frequency, MTTR, change failure %)
"We simply don’t give DBAs enough credit for all the tasks they do beyond writing queries."
https://towardsdatascience.com/has-devops-killed-the-ba-qa-dba-roles-fbc187abddeIndividuals and interactions
Working software
Customer collaboration
Responding to change
over
Processes and tools
Comprehensive documentation
Contract negotiation
Following a plan
That is, while there is value in the items on the right, we value the items on the left more.