{"id":9492,"date":"2017-10-13T04:32:46","date_gmt":"2017-10-13T04:32:46","guid":{"rendered":"http:\/\/abstracta.us\/?p=9492"},"modified":"2025-05-05T21:20:43","modified_gmt":"2025-05-05T21:20:43","slug":"much-talk-around-devops-culture","status":"publish","type":"post","link":"https:\/\/abstracta.us\/blog\/devops\/much-talk-around-devops-culture\/","title":{"rendered":"Why So Much Talk Around DevOps Culture?"},"content":{"rendered":"<p><!-- Go to www.addthis.com\/dashboard to customize your tools --><script src=\"\/\/s7.addthis.com\/js\/300\/addthis_widget.js#pubid=ra-58d80a50fc4f926d\" type=\"text\/javascript\"><\/script><\/p>\n<h1><span style=\"font-weight: 400;\">DevOps is taking software development by storm\u2026 Here\u2019s what it means for testers.<\/span><\/h1>\n<p><span style=\"font-weight: 400;\">DevOps is a little word that has become very much <i><span style=\"font-weight: 400;\">the <\/span><\/i><span style=\"font-weight: 400;\">trend.<\/span><span style=\"font-weight: 400;\"> It comes from uniting the words Development and Operations, with the idea of joining two worlds between which there is usually a lot of friction. One speaks of &#8220;DevOps culture&#8221; perhaps because it is something that&#8217;s more related to people and their ways of working, and not only with technologies; it is about uniting two things that are historically separate: software construction (development) and the operation thereof. It\u2019s also about uniting more parts of the different worlds involved in the creation and operation of software.<\/span><\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"DevOps_Culture\"><\/span>DevOps Culture<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">A DevOps culture proposes to generate a culture of learning, communication, and feedback cycles at different levels. It&#8217;s not just a technical thing, much less a role, even though you often hear\u00a0&#8220;I&#8217;m a DevOps&#8221; or &#8220;Looking for a DevOps for a very cool company.&#8221;<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Typically, something like this happens: there\u2019s an idea, change, requirement, etc., the developers work on writing code, they put together a package that is passed to the operations and they are the ones that put that into production, and from there it goes into the hands of the user. After that, it&#8217;s the operations people who keep managing it, and are responsible for everything that happens on the production side. There is a typical conflict of interest between development and operations that often causes difficulty and delay:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Developers want to give the user the product as soon as possible (more so within agile methodologies, possibly aiming to put changes into production as often as once a week).<\/span><\/li>\n<li style=\"font-weight: 400;\">Operations does not want to put something in production that might cause problems, then have to regress, recovering backups because the last change broke the database or the system crashes, and then users call\u2026 and<i><span style=\"font-weight: 400;\"> they <\/span><\/i><span style=\"font-weight: 400;\">are the first line of support.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">This demonstrates a huge source of friction between development and operations, which affects the business. And this does not happen due to the tools we use. As Jerry Weinberg&#8217;s second consulting law states (from his book, \u201c<\/span><a href=\"https:\/\/www.amazon.com\/Secrets-Consulting-Giving-Getting-Successfully\/dp\/0932633013\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">The Secrets of Consulting: A Guide to Giving and Getting Advice<\/span><\/a><span style=\"font-weight: 400;\">\u201d), <\/span><\/p>\n<p><span style=\"font-weight: 400;\">[tweet_box design=&#8221;box_12_at&#8221; float=&#8221;none&#8221; author=&#8221;Jerry Weinberg&#8221; pic_url=&#8221;http:\/\/abstracta.us\/wp-content\/uploads\/2016\/01\/jerryWeinberg-221&#215;300-min.jpg&#8221;]&#8221;No matter how it looks at first, it\u2019s always a people problem.&#8221;[\/tweet_box]<\/span><\/p>\n<p><span style=\"font-weight: 400;\">DevOps is a culture. It not only deals with the technical parts, but it has a lot to do with the human components and with the processes. To overcome the possible friction, communication is fundamental. Interaction is also essential and the way in which responsibilities are divided and shared implies an Agile approach that involves not only the developers, but also the operations team.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">And DevOps culture is not only adopted because it\u2019s the \u201cin\u201d thing. It\u2019s used to reduce the time between the birth of an idea to its release.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">According to a study <\/span><span style=\"font-weight: 400;\"><a href=\"https:\/\/www.atlassian.com\/devops\" target=\"_blank\" rel=\"noopener\">mentioned here<\/a>:\u00a0<\/span><\/p>\n<p>[tweet_box design=&#8221;default&#8221; float=&#8221;none&#8221;]Teams that employ DevOps deliver 30 times more frequently, have 60 times fewer failures and recover 160 times faster.[\/tweet_box]<\/p>\n<p>&nbsp;<\/p>\n<p><span style=\"font-weight: 400;\">From the same article mentioning the study, I borrowed the following image, because I think it represents the concept of DevOps culture very well. It shows all stages of the development process, with continuous feedback, continuous integration, all surrounded by real-time communication. <\/span><\/p>\n<figure id=\"attachment_9497\" aria-describedby=\"caption-attachment-9497\" style=\"width: 768px\" class=\"wp-caption aligncenter\"><a href=\"http:\/\/abstracta.us\/wp-content\/uploads\/2017\/10\/devops-loop-illustrations-768x435-min.png\"><img decoding=\"async\" class=\"wp-image-9497 size-full\" src=\"http:\/\/abstracta.us\/wp-content\/uploads\/2017\/10\/devops-loop-illustrations-768x435-min.png\" alt=\"DevOps loop\" width=\"768\" height=\"435\" \/><\/a><figcaption id=\"caption-attachment-9497\" class=\"wp-caption-text\">Image source: Atlassian<\/figcaption><\/figure>\n<h2><span class=\"ez-toc-section\" id=\"The_Evolution_to_DevOps_From_a_Testing_Perspective\"><\/span>The Evolution to DevOps From a Testing Perspective<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Something I found particularly interesting was Katrina Clokie\u2019s way of viewing DevOps from a tester\u2019s point of view, from her book, \u201c<\/span><a href=\"https:\/\/leanpub.com\/testingindevops\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">A Practical Guide to Testing in DevOps<\/span><\/a><span style=\"font-weight: 400;\">\u201d (A book I highly recommend!). <\/span><\/p>\n<p><span style=\"font-weight: 400;\">She shows in three different figures, how the relationships between testers and everyone else involved in software development have changed throughout the evolution from waterfall to Agile to DevOps.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In waterfall, we have the tester interacting with different roles, but since the testing is independent, it finds itself siloed, isolated from the rest of the team.<\/span><\/p>\n<p><a href=\"http:\/\/abstracta.us\/wp-content\/uploads\/2017\/10\/waterfall-vs-devops-276x300-min.png\"><img decoding=\"async\" class=\"aligncenter wp-image-9499 size-full\" src=\"http:\/\/abstracta.us\/wp-content\/uploads\/2017\/10\/waterfall-vs-devops-276x300-min.png\" alt=\"testers in waterfall\" width=\"276\" height=\"300\" \/><\/a><\/p>\n<p><span style=\"font-weight: 400;\">Then, in Agile, you see there is just one team, with a more horizontal structure, all sharing responsibility for quality, without distinguishing as much all of the different roles. <\/span><\/p>\n<p><a href=\"http:\/\/abstracta.us\/wp-content\/uploads\/2017\/10\/agile-vs-devops-274x300-min.png\"><img decoding=\"async\" class=\"aligncenter wp-image-9498\" src=\"http:\/\/abstracta.us\/wp-content\/uploads\/2017\/10\/agile-vs-devops-274x300-min.png\" alt=\"agile-vs-devops-274x300-min\" width=\"276\" height=\"302\" \/><\/a><\/p>\n<p><span style=\"font-weight: 400;\">But here as you can see in Agile, the development ends when the \u201cpackage\u201d is passed over to operations to then release into production. In the team\u2019s <a href=\"https:\/\/www.stickyminds.com\/article\/kanban-software-testing-teams\" target=\"_blank\" rel=\"noopener\">Kanban<\/a>, we would see that the concept of \u201cdone\u201d implies that the code is production ready, but it is still not in the hands of the client. Agile always praises \u201cthe team\u201d but it fails to include operations team members, support, etc.<\/span><\/p>\n<p><a href=\"http:\/\/abstracta.us\/wp-content\/uploads\/2017\/10\/devops-culture-min.png\"><img decoding=\"async\" class=\"aligncenter wp-image-9500\" src=\"http:\/\/abstracta.us\/wp-content\/uploads\/2017\/10\/devops-culture-min.png\" alt=\"devops-culture-min\" width=\"276\" height=\"294\" \/><\/a><\/p>\n<p><span style=\"font-weight: 400;\">I think the signs are clear, DevOps emphasizes <\/span><b>having the right conversations, at the right time, across different teams to maximize outcomes. <\/b><\/p>\n<p><span style=\"font-weight: 400;\">Are you working within a culture of DevOps? Do you think it\u2019s here to stay? Let me know in the comments!<\/span><\/p>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Recommended_for_You\"><\/span>Recommended for You<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"color: #00b674;\"><span style=\"font-weight: 400;\"><a href=\"http:\/\/abstracta.us\/blog\/software-testing\/devops-venn-diagram\/\">We Want Our\u00a0DevOps Venn Diagram Back &#8211; Plus One!<\/a>\u00a0<\/span><br \/>\n<\/span><a href=\"https:\/\/abstracta.us\/software-testing\/what-is-a-qe\/\"><span style=\"font-weight: 400;\">[Infographic] What is a QE?<\/span><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>DevOps is taking software development by storm\u2026 Here\u2019s what it means for testers. DevOps is a little word that has become very much the trend. It comes from uniting the words Development and Operations, with the idea of joining two worlds between which there is&#8230;<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[236],"tags":[68,101],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v14.0.2 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Why So Much Talk Around DevOps Culture? | Abstracta<\/title>\n<meta name=\"description\" content=\"DevOps is taking software development by storm. A DevOps culture proposes a culture of learning, communication, and feedback cycles at different levels.\" \/>\n<meta name=\"robots\" content=\"index, follow\" \/>\n<meta name=\"googlebot\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<meta name=\"bingbot\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/abstracta.us\/blog\/devops\/much-talk-around-devops-culture\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Why So Much Talk Around DevOps Culture? | Abstracta\" \/>\n<meta property=\"og:description\" content=\"DevOps is taking software development by storm. A DevOps culture proposes a culture of learning, communication, and feedback cycles at different levels.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/abstracta.us\/blog\/devops\/much-talk-around-devops-culture\/\" \/>\n<meta property=\"og:site_name\" content=\"Blog about AI-powered quality engineering for teams building complex software | Abstracta\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/AbstractaQA\/\" \/>\n<meta property=\"article:published_time\" content=\"2017-10-13T04:32:46+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-05-05T21:20:43+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/abstracta.us\/wp-content\/uploads\/2017\/10\/DevOps-1-min.png\" \/>\n\t<meta property=\"og:image:width\" content=\"560\" \/>\n\t<meta property=\"og:image:height\" content=\"315\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@fltoledo\" \/>\n<meta name=\"twitter:site\" content=\"@AbstractaUS\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/abstracta.us\/blog\/#website\",\"url\":\"https:\/\/abstracta.us\/blog\/\",\"name\":\"Blog about AI-powered quality engineering for teams building complex software | Abstracta\",\"description\":\"AI-powered quality engineering\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/abstracta.us\/blog\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/abstracta.us\/blog\/devops\/much-talk-around-devops-culture\/#primaryimage\",\"inLanguage\":\"en-US\",\"url\":\"http:\/\/abstracta.us\/wp-content\/uploads\/2017\/10\/devops-loop-illustrations-768x435-min.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/abstracta.us\/blog\/devops\/much-talk-around-devops-culture\/#webpage\",\"url\":\"https:\/\/abstracta.us\/blog\/devops\/much-talk-around-devops-culture\/\",\"name\":\"Why So Much Talk Around DevOps Culture? | Abstracta\",\"isPartOf\":{\"@id\":\"https:\/\/abstracta.us\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/abstracta.us\/blog\/devops\/much-talk-around-devops-culture\/#primaryimage\"},\"datePublished\":\"2017-10-13T04:32:46+00:00\",\"dateModified\":\"2025-05-05T21:20:43+00:00\",\"author\":{\"@id\":\"https:\/\/abstracta.us\/blog\/#\/schema\/person\/7421e539de0357d3adb0c69ed469a1c2\"},\"description\":\"DevOps is taking software development by storm. A DevOps culture proposes a culture of learning, communication, and feedback cycles at different levels.\",\"breadcrumb\":{\"@id\":\"https:\/\/abstracta.us\/blog\/devops\/much-talk-around-devops-culture\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/abstracta.us\/blog\/devops\/much-talk-around-devops-culture\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/abstracta.us\/blog\/devops\/much-talk-around-devops-culture\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/abstracta.us\/blog\/\",\"url\":\"https:\/\/abstracta.us\/blog\/\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/abstracta.us\/blog\/devops\/\",\"url\":\"https:\/\/abstracta.us\/blog\/devops\/\",\"name\":\"DevOps\"}},{\"@type\":\"ListItem\",\"position\":3,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/abstracta.us\/blog\/devops\/much-talk-around-devops-culture\/\",\"url\":\"https:\/\/abstracta.us\/blog\/devops\/much-talk-around-devops-culture\/\",\"name\":\"Why So Much Talk Around DevOps Culture?\"}}]},{\"@type\":[\"Person\"],\"@id\":\"https:\/\/abstracta.us\/blog\/#\/schema\/person\/7421e539de0357d3adb0c69ed469a1c2\",\"name\":\"Federico Toledo, Chief Quality Officer at Abstracta\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/abstracta.us\/blog\/#personlogo\",\"inLanguage\":\"en-US\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/6de7ec6536c4028b5c02ad4ec1b9af0d?s=96&d=blank&r=g\",\"caption\":\"Federico Toledo, Chief Quality Officer at Abstracta\"},\"description\":\"Co-founder and COO of Abstracta\",\"sameAs\":[\"https:\/\/twitter.com\/fltoledo\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/posts\/9492"}],"collection":[{"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/comments?post=9492"}],"version-history":[{"count":15,"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/posts\/9492\/revisions"}],"predecessor-version":[{"id":16031,"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/posts\/9492\/revisions\/16031"}],"wp:attachment":[{"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/media?parent=9492"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/categories?post=9492"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/tags?post=9492"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}