The biggest problem I've seen is business priority in work scheduling of development. When the business lead doesn't really get[1] that developers wanting to fix a bug that crops up in production will allow them to sleep the night. Worse when developers and support are separate. Lord help you if the DBA team cannot be bothered to wake up.

I swear, next time someone says "its just needs a little manual intervention, no big deal", I might fly into a violent rage. Particularly if the cause is documented and just waiting a "sprint" to slot it into.

1) often because the development manager is trying to work their way up the ladder and is being a kiss-a$$ about functionality - especially fun in companies that like to move managers around to get them "broad experience" in the company