If your company is starting to embrace DevOps, one of your biggest challenges would be getting your developers on-board. Developers tend not to want to adapt to change if they can't see the reasoning for the change.
If you look at DevOps from a developer's view, they think it is not really doing much for them because most of these folks are not aware of the benefits it can bring to the organization & themselves in the career enrichment.
We usually get some developers asking, - "Why would I want my code to build and deploy on its own? In my world, our CI/CD pipeline builds, tests and deploys to our QA environment upon check-in."
How do you tackle such scenarios?
I need your suggestions and experience with the same.
Developers tend not to want to adapt to change if they can't see the reasoning for the change.
...
How do you tackle such scenarios?
You explain the reasoning for the change?
For example, how is devops different from a "CI/CD pipeline [that] builds, tests and deploys to our QA environment upon check-in"?
Md Zaid Imam
Let learning process continue | Principal Product Manager
When we aggressively started adopting DevOps culture, both Ops and Dev got a chance to involve in both the practices. So they can get an understanding of responsibility and the primary goal of each individual. At initial, we splited both the team and assigned 2 or 3 members (Dev+Ops pending upon the module) to take ownership and accountability for each and every release and log effort, time spent, total failure during development, total failure post-release, an incident occurs, no of RCA published etc. After collecting all this number goal was to reduce the previous failure and this small team was ready to take up this as the next challenge. Of course, we keep swapping members after 3-4 release and now anyone can take up anything. There were blockers but every organization / leader can handle in there own ways.