{"id":14696,"date":"2020-07-02T20:24:47","date_gmt":"2020-07-02T14:54:47","guid":{"rendered":"https:\/\/cigniti.com\/blog\/?p=14696"},"modified":"2023-03-08T18:09:25","modified_gmt":"2023-03-08T12:39:25","slug":"devops-leadership-traits-key-metrics-devops-trans","status":"publish","type":"post","link":"https:\/\/www.cigniti.com\/blog\/devops-leadership-traits-key-metrics-devops-trans\/","title":{"rendered":"DevOps and digital transformation \u2013 leadership characteristics & key metrics"},"content":{"rendered":"

Gartner predicts<\/a> that through 2022, 75% of DevOps initiatives will fail to meet expectations due to issues around organizational learning and change. Another study suggested that the DevOps market is expected to reach $6.6 billion in the same year.<\/p>\n

DevOps is not a mere trendy buzzword anymore. It is expected to become the standard way of software development in each organization in the coming future as it transitions from the phase of early adoption to early majority uptake. As leaders realize the need to fundamentally transform the way their businesses operate and to keep customer-centricity at the core of their initiatives, DevOps adoption is expected to gain further momentum this year and beyond.<\/p>\n

Jermaine Oldham, VP of Engineering & Technology at J.B. Hunt, recently talked in detail about the main characteristics required in a leader to drive a successful DevOps organization, impact of DevOps on digital transformation<\/a>, and the key metrics necessary to determine the DevOps performance in an organization. This blog is an excerpt from the discussion on the QATalks podcast.<\/p>\n

The key characteristics of Quality Engineering & DevOps leaders<\/strong><\/p>\n

The pace of change around us has accelerated many-folds with the ongoing pandemic. What was supposed to be a 4-year transformation plan for several organizations was realized in the span of three months. While keeping up with the speed of change, it is important that the leaders do not fall into a rut and put significant focus on innovation as well. Therefore, quality engineering and DevOps leaders need to embrace a holistic point of view while navigating the digital transformation or DevOps transformation<\/a>.<\/p>\n

Jermaine suggests four key characteristics that these leaders should embrace \u2013 \u201cOne, lead with confidence. Confidence is the key to know that innovation and change are out there, and you need to embrace it. Two, as a QE leader, you need to be willing to adapt and learn and grow. So, the key thing there is just being flexible to be able to adapt, learn, and grow so that you can evolve as a leader. Three, be willing to challenge your previous exceptions and understandings. Things may not be the status quo. So, you\u2019ll have to certainly challenge your previous assumptions and understandings of what you thought you knew. And then finally, you need to be open to failing. But the key with failing in this space is failing and failing very fast.\u201d<\/p>\n

CI\/CD\/CT pipeline for failing fast<\/strong><\/p>\n

DevOps enables automation and augments and accelerates software delivery and innovation. With a Continuous Integration & Continuous Deployment pipeline, coupled with a continuous testing feedback loop, DevOps offers the scope to fail fast, but also to get up and bounce back faster.<\/p>\n

Jermaine elaborates on the concept of failing fast as, \u201cThe key thing here is, as I attributed before, failing very fast. It needs to be a kind of a fast feedback loop and a fast kind of evolution of how you work through problems and situations. So, I\u2019ve seen leaders before who get myself and my teams where we failed on something, we tried to implement something, we tried to adopt a new technology. We thought we had the use cases and documentation to support the business, but we didn\u2019t actually hit the nail on the head the first time around. So, in those instances where I\u2019ve seen that we failed in the beginning, we went back, and we iterate it to understand what we needed to do to improve on. We came back with a working model in order to solve the problem. So I would say just that there\u2019s a continuous evolution where you may deliver a solution per the use cases and requirements that you gathered, but you may fail the first time, but don\u2019t be swayed from the overall goal of trying to solve business problems. You want to fail fast and you want to come back and you want to be persistent.\u201d<\/p>\n

The rising importance of DevOps in digital transformation<\/strong><\/p>\n

The COVID-19 outbreak has hit the digital transformation initiatives as a wrecking ball. With the accelerated pace of digital transformation and adoption of digital practices, DevOps is also shifting from a \u2018nice-to-have\u2019 to a \u2018must-to-have\u2019 component within the digital transformation strategy<\/a>. While offering recommendations to organizations trying to embrace this change coming at them so quickly, Jermaine says, \u201cI would say one of the things that are important is preparing your team for the cultural change. When I think about DevOps and I think about quality, I think about really how you are developing the tool chain and a methodology. The first thing you need to think about is culture, the culture of the team. Prepare the team and yourself to embrace a cross or working model. When you think about the implementation of DevOps in the digital age, it\u2019s cross functional team that consists of not only just developers and IT operations, but quality experts as well , so quality engineers and quality leaders and quality analysts to make that kind of working model. In addition, you need to prepare your team to own the quality as a key pillar to delivering software. I\u2019ve seen teams not own quality. Quality is extremely important and in order to ensure that you\u2019re going to deliver value fast and often to the business, you\u2019ve got to own your own quality. And the last thing I would say on this is you also need to prepare the business to embrace getting valued to software delivery early and often. So it does you no good to have a very stringent pipeline where you\u2019ve got dev and operations working together, where you\u2019re able to build, where you\u2019re able to test and release, and you\u2019ve got continuous testing inside of the pipeline, but the business doesn\u2019t have the capacity to consume that. So, you need to also prepare your business in order to receive this value on a frequent basis as well.\u201d<\/p>\n

The relevance and importance of Testing Centers of Excellence<\/strong><\/p>\n

With the introduction of Agile and DevOps methodologies, it seemed that the Testing Centers of Excellence or TCoEs lost their relevance. As quality started to shift left in the SDLC, TCoEs appeared to be redundant and are still in a challenging spot. Sharing an interesting perspective on the importance of TCoEs in a DevOps era \u2013 \u201cThere is a lot of shift in the overall IT itself is happening, and that includes quality as well. So, the testing center of excellence is becoming a challenging spot right now and it\u2019s getting into a next evolution, I would say. Quality and testing is not going to go away. It will exist in different format. It could be quality engineering, and that\u2019s where the industry shift is happening. I want to get my testers ahead of the game to start working from the requirement itself, I want each of my test engineers to be certified with the quality engineering concept or scaled agile framework concept. In the agile and DevOps model, the whole of the shift is towards building out pockets of excellence, which could be a quality engineering center of excellence, or digital center of excellence, or it could be automation, or it could be DevOps center of excellence.\u201d<\/p>\n

On further explaining the concept of the pockets of excellence, \u201cLike the way how agile is split into multiple parts and you call it as a story, or you call it as a scrum and execute them, quality is also shifted into each of those pockets, testing underneath the IT domain itself. For example, if I\u2019m creating an IT life cycle with respect to agile or DevOps, you form a small scrum team. And within that, you are bringing in this test-driven development concept, and bringing in the quality engineers, or bringing in the software development engineer in test, and part of that team itself and creating that CoE within that in-sprint, no development life cycle. So as TCoE is evolving into the next stages of the excellence with respect to quality, we are repositioning the entire IT with respect to continuous testing in the name of quality engineering.\u201d<\/p>\n

Impact of DevOps on digital transformation<\/strong><\/p>\n

DevOps has a significant impact on driving customer value through digital transformation. For creating a structured model and methodology for delivering software with quality through automation, it is important to consider automation holistically \u2013 automation of builds, automation of deployments, and automation of monitoring. Jermaine says, \u201cWhen I think about the impact, I\u2019m also thinking about creating a software delivery model that provides a quick feedback loop. So in the DevOps world in relation to digital transformation driving customer value, you\u2019ve got to have a system checks and balances that allow you to fail and fail fast as I was mentioning before, but it\u2019s got to be a continuous feedback. So if my bill failed, because I didn\u2019t pass the security check, I get notification as a developer and I\u2019m able to adjust on the fly and reinitiate that bill to ultimately get that value, which is the code that I\u2019m developing and the features and functions that I\u2019m trying to iterate on the software and deliver a new functions and functionality to the business as fast as possible.\u201d<\/p>\n

\u201cI would say integration of testing as a practice needs to be first and foremost and embracing continuous testing is a requirement to success. I\u2019ll tell you that a DevOps methodology in order to deliver software is just as good as testing that\u2019s integrated. So, when I think about tests, I\u2019m thinking about some unit testing of the code, I\u2019m thinking about testing multiple modules together, I\u2019m thinking about doing service calls and service testing, I\u2019m thinking about functional testing, I\u2019m thinking about non-functional testing, performance testing. In the perfect world, this would be integrated as a product of your delivery pipeline, which is your DevOps pipeline. And then you need to create a method to deliver software to the business fast and when they want it, but with higher quality. You never compromise quality for speed, but you want to do a little bit of both. You want to deliver it fast, which is the value proposition, but you want to do it with higher quality.\u201d<\/p>\n

Building a DevOps culture and shifting mindset<\/strong><\/p>\n

One of the key components for shifting to a DevOps culture is having a shared responsibility. A DevOps culture drives better communication in a cross-working model to facilitate higher collaboration between dev, IT Ops, and QA teams. Having a shared responsibility and accountability not only enables the delivery of high-quality software at high-speed but also establishes end-to-end transparency.<\/p>\n

Talking about transparency and trust, Jermaine says, \u201cWhen you think about the culture, you\u2019ve got to work with others and you\u2019ve got to work with others very frequently, and you can\u2019t get in a situation where you\u2019re hiding something or trying to suppress something on the development side, or on the IT operations side, or when you\u2019re doing the testing aspects of it. You\u2019ve to be a hundred percent transparent. And you\u2019ve to trust. So in the DevOps culture, one of the underlying factors that you\u2019ve to have is you got to trust one another. You\u2019ve to bring people together, you\u2019ve to communicate, and you\u2019ve to trust one another. If you get that and things start clicking, then that\u2019s when you\u2019re able to really deliver software faster with higher quality.\u201d<\/p>\n

The key metrics for evaluating DevOps maturity in an organization<\/strong><\/p>\n

There are five key metrics that allow organizations to evaluate their DevOps maturity \u2013 deployment frequency, lead time, change failure rate, meantime-to-recovery, and the total cost of quality.<\/p>\n

Talking about these metrics, Jermaine elaborates, \u201cOne is deployment frequency \u2013 how able, how fast, and how frequent am I able to deploy to production, to lay binaries to production services and servers, and what\u2019s the frequency of that. Another is lead time that really measures the amount of time that occurs between starting a work item until it\u2019s deployed. So that really allows you to measure the time of value from the time that you\u2019ve logged that user story using your scrum or Kanban methodologies and from the time that it\u2019s logged to the time it\u2019s deployed. Another key KPI and metric in this space is change failure rate. You want to deploy frequently, but you don\u2019t want to deploy frequently if you\u2019re failing. You want to be able to measure your change failure rate. From a time that I\u2019ve deployed, what\u2019s my failure rate with that because that\u2019s going to give you that quick feedback loop in order to change to make your deployments more seamless. And meantime to recovery \u2013 from the time that you do deploy and you do have a failure, this metric really helps you track how long does it take to recover from failures. That\u2019s important because not all deployments, not all the solutions deployment will be successful. So, measuring meantime recovery will allow you to measure how long it took for you to recover so that you can get faster and faster and faster, and ultimately really delivering value to the business at a fast rate with higher quality with the least amount of thought as possible.\u201d<\/p>\n

Explaining the total cost of quality, \u201cYou want to see how you\u2019re improving the total cost of quality and the meantime to recover \u2013 How quickly I fixed it, how quickly I tested it and released it to production, and have your quality as the metrics.\u201d<\/p>\n

To sum up<\/strong><\/p>\n

Implementing DevOps testing<\/a> practices helps CxOs bring about a cultural shift that leads to greater collaboration across teams, improves the quality of code, increases the response rate of business changes, inculcates shift-left practices, & creates an environment of growth for Software Development Engineers in Test (SDETs) \u2013 all of which are necessary to provide DevOps solutions.<\/p>\n

At Cigniti, we standardize efforts and ensure accelerated time-to-market with DevOps testing solutions. We focus on delivering improved deployment quality with greater operational efficiency. Our DevOps testing specialists with their deep experience in Continuous Integration (CI) testing & Continuous Deployment (CD) help configure & execute popular CI\/CD tools supporting your DevOps transformation<\/a> & application testing efforts.<\/p>\n

Schedule a discussion<\/a> with our DevOps testing experts to know more.<\/p>\n","protected":false},"excerpt":{"rendered":"

Gartner predicts that through 2022, 75% of DevOps initiatives will fail to meet expectations due to issues around organizational learning and change. Another study suggested that the DevOps market is expected to reach $6.6 billion in the same year. DevOps is not a mere trendy buzzword anymore. It is expected to become the standard way […]<\/p>\n","protected":false},"author":20,"featured_media":14697,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_lock_modified_date":false,"footnotes":""},"categories":[735,2727],"tags":[3161,974,246,976,3156,3160,3158,2078,314,3159,2050,1025,2040,2018,170,383,575],"ppma_author":[3727],"class_list":["post-14696","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops-testing","category-digital-transformation","tag-ci-cd","tag-continuous-deployment","tag-continuous-integration","tag-continuous-integration-testing","tag-continuous-testing-strategy","tag-devops-center-of-excellence","tag-devops-continuous-integration","tag-devops-digital-transformation","tag-devops-implementation","tag-devops-in-digital-transformation","tag-devops-qa","tag-devops-quality-assurance","tag-devops-strategy","tag-devops-test-automation","tag-devops-testing","tag-devops-transformation","tag-digital-transformation-strategy"],"authors":[{"term_id":3727,"user_id":20,"is_guest":0,"slug":"cigniti","display_name":"About Cigniti (A Coforge Company)","avatar_url":{"url":"https:\/\/www.cigniti.com\/blog\/wp-content\/uploads\/2024\/10\/Coforge-blog-Logo.png","url2x":"https:\/\/www.cigniti.com\/blog\/wp-content\/uploads\/2024\/10\/Coforge-blog-Logo.png"},"user_url":"https:\/\/www.cigniti.com\/","last_name":"(A Coforge Company)","first_name":"About Cigniti","job_title":"","description":"Cigniti Technologies Limited, a Coforge company, is the world\u2019s leading AI & IP-led Digital Assurance and Digital Engineering services provider. Headquartered in Hyderabad, India, Cigniti\u2019s 4200+ employees help Fortune 500 & Global 2000 enterprises across 25 countries accelerate their digital transformation journey across various stages of digital adoption and help them achieve market leadership by providing transformation services leveraging IP & platform-led innovation with expertise across multiple verticals and domains.\r\n
\r\nLearn more about Cigniti at www.cigniti.com<\/a> and about Coforge at www.coforge.com<\/a>."}],"_links":{"self":[{"href":"https:\/\/www.cigniti.com\/blog\/wp-json\/wp\/v2\/posts\/14696"}],"collection":[{"href":"https:\/\/www.cigniti.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cigniti.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cigniti.com\/blog\/wp-json\/wp\/v2\/users\/20"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cigniti.com\/blog\/wp-json\/wp\/v2\/comments?post=14696"}],"version-history":[{"count":0,"href":"https:\/\/www.cigniti.com\/blog\/wp-json\/wp\/v2\/posts\/14696\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cigniti.com\/blog\/wp-json\/wp\/v2\/media\/14697"}],"wp:attachment":[{"href":"https:\/\/www.cigniti.com\/blog\/wp-json\/wp\/v2\/media?parent=14696"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cigniti.com\/blog\/wp-json\/wp\/v2\/categories?post=14696"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cigniti.com\/blog\/wp-json\/wp\/v2\/tags?post=14696"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.cigniti.com\/blog\/wp-json\/wp\/v2\/ppma_author?post=14696"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}