DevOps is an education and communication position. You won't get the devs to do ops, since they are good at development and don't know much about ops and the sa

DevOps is an education and communication position. You won't get the devs to do ops, since they are good at development and don't know much about ops and the same applies to ops in reverse. You need people (ideally, on each product team) who understand enough of both sides to efficiently communicate problems and facilitate solutions. Before you make your devs write provisioning scripts for databases (which they can do, but probably won't get the trade-offs of different parameters), you might want to explain the difference between running database migration scripts on application server startup on a single-instance dev laptop and on a distributed master-master replicated database with multiple application server instances. You increase awareness, you provide platforms, you communicate. That's what DevOps and especially DevOps teams do. They are glue between people of different competence areas. The alternative is Peter's principle applied to both sides.