DevOps shouldn’t be a straitjacket Mar15

DevOps shouldn’t be a straitjacket

The DevOps movement has a dirty little secret it doesn’t want anyone talking about.  DevOps isn’t about making you money, or making your life easier.  DevOps is about making vendors and consultants money.  If you’re lucky and wise you will be able to choose good partners who, in the course of enriching themselves also make your business significantly more efficient.  But how to narrow the playing field? The most important thing to do is ask “where does the money go”?  Anyone banging on about an IT industry buzzword wants your money.  The question is how much do they want and what are they proposing to give you for it? In almost every case you don’t need a consultant to get to DevOps.  I can tell you the secret sauce of their advice right here: DevOps is hard to implement.  This is not because the tools are difficult, the theory is complicated or the value vague and nebulous. DevOps is hard to implement because it means radical change for many people, many of whom cannot easily see how or why they will still be employed after the process is completed.  Fear, and a very human resistance to change are what stand in the way of “implementing DevOps culture”. No consultant can change that.  No consultant can do anything to ease people through the process or soothe their fears.  Management of the business in question need to recognize the fears of the technologists they employ, engage with them, and provide assurances that everything will be all right once the dust settles. No consultant can do that for management.  The best they can do is spend their time trying to serve as a translation layer: explaining to management why the tech staff are reluctant, and explaining to...