You may have a difficult time finding a book comparing these practices directly. I am not aware of any.
The software development life cycle and IT are often directly intertwined. IT is often responsible for the production environments, which enables proper separation of duties. As such, you should already have some existing external perspective although probably limited.
Typically, change control or change management between development and IT are nearly identical, at least when the changes are applied to the system. The differences are in the details, as an Apache upgrade is not going to be deployed the same way as a proprietary application. Nevertheless, all changes deployed to production should follow the same fundamental requirements.
Typically, I think of change control as the documentation and audit trail for the following key points in a plan format:
- Summary
- Scheduling
- Testing
- Verification
- Backout
- Change details
If you want to review IT fundamentals best practices in detail, you may find the Practice of Systems and Network Administration to be a good reference. If you want to read further about change control, you will likely find ITIL to be a useful reference.
I would be happy to go into further detail if there are particular areas that you are unclear about.
