A couple of colleagues and I have been pushing automated data testing and deployment testing techniques and local workstation builds. We've been equally amazed and dismayed at the lack of enthusiasm for changing to this approach.
We've burned a lot of effort making it possible to
- Build a local workstation by executing a batch/shell script.
- Execute a one line command to deploy/rollback a release locally
- Execute a one line command to test the release locally
We've put together "....for Dummies" documentation to support these new methods. We've hyperlinked between our Confluence and git README.md files
We've "eaten our own dog food" and found it delicious. Really a lot of it is the stuff that SQL Server folk and in particular Redgate tool users take for granted.
A lot of hand holding has taken place. We've tested our HOW TO documentation to new employees with a mandate for them to improve it if they can.
We've invested time and effort to find out why there is resistance. Bar one or two easily addressed niggles it really does boil down to "we like the way we currently operate".
One of the points in the article calls out the effort to change vs the benefit to change. In my experience the effort/cost are upfront and highly visible. The benefits are a promise that is to be delivered but not delivered yet. Over time the ROI will be significant.
I am mindful that Jeff Moden says "Change is inevitable, change for the better is not".