{"id":11306,"date":"2016-09-18T08:12:40","date_gmt":"2016-09-18T08:12:40","guid":{"rendered":"http:\/\/www.intelligentcio.com\/me\/?p=11306"},"modified":"2016-09-18T08:12:40","modified_gmt":"2016-09-18T08:12:40","slug":"where-should-organisations-in-the-middle-east-use-devops","status":"publish","type":"post","link":"https:\/\/www.intelligentcio.com\/me\/2016\/09\/18\/where-should-organisations-in-the-middle-east-use-devops\/","title":{"rendered":"Where should organisations in the Middle East use DevOps?"},"content":{"rendered":"<p class=\"p1\"><span class=\"s1\">There lingers the misperception that DevOps is mostly for companies that sport ping-pong tables and have free sushi for lunch. Trendy Web giants out on the technology bleeding edge. Firms that manufacture construction equipment and have large swaths of legacy computer code? Not so much, writes\u00a0<em>Gordon Haff, Technology Evangelist, Red Hat.<\/em><\/span><\/p>\n<p class=\"p1\"><span class=\"s1\">It\u2019s really not surprising that this misperception exists. A traditional IT organisation glances at a company like Netflix and they may see a unique entity, a \u201cunicorn,\u201d wholly unlike themselves. They\u2019re not even entirely wrong. More extreme implementations of approaches such as microservices or near-continuous production releases likely won\u2019t become the universal norm\u2014especially in the \u201cclassic IT\u201d (aka Mode 1, to use the terminology of research firm Gartner) parts of their infrastructure. However, that doesn\u2019t mean DevOps principles can\u2019t also benefit the conservative IT of conservative firms.<\/span><\/p>\n<p class=\"p1\"><span class=\"s1\"><b>It\u2019s about the software<\/b>\u00a0<\/span><\/p>\n<p class=\"p1\"><span class=\"s1\">The first reason that DevOps practices apply outside of greenfield, cloud-native (aka Gartner\u2019s Mode 2) IT is that the rules are changing. Venture capitalist Marc Andreesen\u2019s \u201csoftware is eating the world\u201d meme has become something of a cliche but it\u2019s no less true for that. As my Red Hat colleague James Labocki wrote recently, &#8220;Bank of America is not just a bank, they are a transaction processing company. Exxon Mobil, is not only an oil and gas company, they are a GIS company. With each passing day Walgreens business is more reliant on electronic health records.\u201d<\/span><\/p>\n<p class=\"p1\"><span class=\"s1\">Furthermore, these shifts in technology and how business is transacted are creating new competitors that come at established firms from non-obvious directions and places. Barriers created by capital requirements, transaction costs, or even just brand become less relevant when a mobile app can change the landscape in a relative blink of an eye. (Think of all the new next-day or same-day approaches to delivery being trialed that could emerge as competition to the logistics incumbents.)<\/span><\/p>\n<p class=\"p1\"><span class=\"s1\">Therefore, while the priorities for classic IT may be different from those of cloud-native, business-as-usual needs to evolve. Even calling traditional IT \u201clegacy\u201d is a dangerous and misleading turn of phrase as it implies static and in need of wholesale replacement.<\/span><\/p>\n<p class=\"p1\"><span class=\"s1\">Rather, this \u201clow speed\u201d IT may prioritize stability over rapid change but it still needs to increase its relevance to new organizational initiatives and reduce complexity. To increase relevance, it needs to deliver environments for developers in minutes instead of days or weeks. To reduce complexity, it needs to implement policy-driven automation that reduces the need for manual (and error-prone) tasks.<\/span><\/p>\n<p class=\"p1\"><span class=\"s1\">Getting there requires a combination of policy-based hybrid cloud management and DevOps approaches.<\/span><\/p>\n<p class=\"p1\"><span class=\"s1\"><b>DevOps thinking is proven to work in traditional industries<\/b>\u00a0<\/span><\/p>\n<p class=\"p1\"><span class=\"s1\">DevOps as we usually talk about it today is indeed rather new. It\u2019s the child of pervasive open source, continuous integration technologies, platform-as-a-service (PaaS), software-defined infrastructures, and a host of other relatively modern technologies&#8211;which taken as a whole are quite recent. However, DevOps as a general approach has many analogs going back decades in manufacturing and other industries.<\/span><\/p>\n<p class=\"p1\"><span class=\"s1\">Consider some of the terminology associated with DevOps such as \u201cautomation of process\u201d and \u201cculture of collaboration.\u201d These very much describe the transformation of the automobile industry to the modern age. Concepts such as kaizen (loosely, continuous improvement), just-in-time inventory, build-to-order manufacturing, and most of all the systems thinking embodied in the \u201cToyota Way\u201d invite many parallels to DevOps.<\/span><\/p>\n<p class=\"p1\"><span class=\"s1\">Indeed standardised and reusable parts\u2014which have similarities the small reusable services commonly associated with DevOps&#8211;date to the Syst\u00e8me Gribeauval for cannons in 1765. For their part, the processes and machinery that Brunel and Maudlay applied to sailing blocks to standardise production at the beginning of the 19th century look a lot like the repeatable automatable workflows we associate with DevOps.<\/span><\/p>\n<p class=\"p1\"><span class=\"s1\">But cultural shift that emphasizes flexibility, cooperation, and transparency may be the most important similarity. When Jeffrey Liker wrote \u201cThe Toyota Way has been driven so deeply into the psyche of employees at all levels that it has morphed from a strategy into an important element of the company&#8217;s culture,\u201d he was talking about an automobile manufacturer. DevOps likewise requires putting in place incentives, structure, and organization to create the right kind of culture.<\/span><\/p>\n<p class=\"p1\"><span class=\"s1\"><b>Where should organisations use DevOps?<\/b>\u00a0<\/span><\/p>\n<p class=\"p1\"><span class=\"s1\">The lesson here is that DevOps is broadly relevant.<\/span><\/p>\n<p class=\"p1\"><span class=\"s1\">Oh, the details of how DevOps principles are applied will differ both between organizations and within a given organization just as the rigor of some manufacturing processes will depend on what is being built. Failing fast is fine as a general concept but the nature and bounds of acceptable failure need to be built into the overall process.<\/span><\/p>\n<p class=\"p1\"><span class=\"s1\">But there are universals and this brings us back to the fact that, while DevOps is largely built around innovative open source toolchains, it is at least as much about an approach and a culture as on specific tooling. A focus on continuous improvement. An ethos of sharing information and enabling experimentation. The creation of repeatable and automated processes wherever possible.<\/span><\/p>\n<p class=\"p1\"><span class=\"s1\">These apply whether stability or speed is the priority for the organisation in question. As a result, many analysts and other industry watchers expect DevOps to become widely used even in more traditional IT environments over the coming years.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>There lingers the misperception that DevOps is mostly for companies that sport ping-pong tables and have free sushi for lunch. Trendy Web giants out on the technology bleeding edge. Firms that manufacture construction equipment and have large swaths of legacy computer code? Not so much, writes\u00a0Gordon Haff, Technology Evangelist, Red Hat. It\u2019s really not surprising [&hellip;]<\/p>\n","protected":false},"author":20,"featured_media":11307,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[829,6,332],"tags":[832,144,283],"class_list":["post-11306","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-editors-choice","category-insights","category-software","tag-devops","tag-red-hat","tag-software-2"],"acf":[],"publishpress_future_workflow_manual_trigger":{"enabledWorkflows":[]},"_links":{"self":[{"href":"https:\/\/www.intelligentcio.com\/me\/wp-json\/wp\/v2\/posts\/11306","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.intelligentcio.com\/me\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.intelligentcio.com\/me\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.intelligentcio.com\/me\/wp-json\/wp\/v2\/users\/20"}],"replies":[{"embeddable":true,"href":"https:\/\/www.intelligentcio.com\/me\/wp-json\/wp\/v2\/comments?post=11306"}],"version-history":[{"count":0,"href":"https:\/\/www.intelligentcio.com\/me\/wp-json\/wp\/v2\/posts\/11306\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.intelligentcio.com\/me\/wp-json\/wp\/v2\/media\/11307"}],"wp:attachment":[{"href":"https:\/\/www.intelligentcio.com\/me\/wp-json\/wp\/v2\/media?parent=11306"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.intelligentcio.com\/me\/wp-json\/wp\/v2\/categories?post=11306"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.intelligentcio.com\/me\/wp-json\/wp\/v2\/tags?post=11306"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}