[Communitivity]

This depends so much on the situation. It might be a way to get things better, but it's also likely to leave a sour taste in your customer's mouth. They may know that Dev Bob was't responsible for the problem but IT Alice was, but what they'll internalize is that there was a problem with Bob and Alice that caused them pain, and they'll associate Bob and Alice both with that pain.

It's necessary where the relationship with IT becomes adversarial, often with IT that's less skilled, or more constrained by their management.

Where possible though a mutual beneficial relationship is best.

Where I work I have two laptops. One is my corporate laptop, less powerful but it can connect to our internal network. The other is my dev laptop, more powerful but it can only connect to Internet and our dev network. I can install whatever I need on the dev laptop, as long as I a) keep a running log of installed software and update IT when that changes, b) regularly check NVDB for the software I have installed and apply mitigations as needed, c) keep versions updated to current versions where possible (and never to versions that have known vulns).