I don't think DevOps can really be a failure anywhere as it isn't old enough or solidified enough to have a universal definition and any group of activities its

I don't think DevOps can really be a failure anywhere as it isn't old enough or solidified enough to have a universal definition and any group of activities itself can be mis-performed regardless of what you call it. That includes being a bad webmaster and having a system operations department that isn't able to actually deliver anything. If Development and Operations intersect for some activities, and sharing responsibilities for those activities helps, then it's a win. That includes developers not having to wait for some resource to be provisioned because they are "not allowed to click the button themselves", and operations people not having to do the same "create resource" task all day long.