{"id":14516,"date":"2020-03-16T19:15:56","date_gmt":"2020-03-16T13:45:56","guid":{"rendered":"https:\/\/coforge.site\/cigniti\/blog\/?p=14516"},"modified":"2023-03-08T18:10:03","modified_gmt":"2023-03-08T12:40:03","slug":"enterprise-qa-transformation-devops-testing-devops-trans","status":"publish","type":"post","link":"https:\/\/coforge.site\/cigniti\/blog\/enterprise-qa-transformation-devops-testing-devops-trans\/","title":{"rendered":"Enterprise transformation from legacy QA to DevOps"},"content":{"rendered":"

The DevOps market is predicted to experience a growth rate of over 20% through this year. By 2025, it is projected to grow by $12.4 billion at a CAGR of 24.9%.\u00a0<\/span>This impending market explosion can be attributed to\u00a0<\/span>the benefits that organizations are reaping after implementing DevOps.\u00a0<\/span>With 27% of their resources and time dedicated to testing, companies\u00a0<\/span>that adopted DevOps methodologies<\/span>\u00a0achieve<\/span>d<\/span>\u00a0440x shorter time from committing to release, 46x more frequent code deployment, and 96x faster\u00a0<\/span>time\u00a0<\/span>to resolve (TTR).<\/span>\u00a0While these benefits of DevOps adoption seem lucrative, organizations report\u00a0<\/span>several<\/span>\u00a0challenges<\/span>\u00a0related to people, p<\/span>roces<\/span>se<\/span>s, technology, and information.\u00a0<\/span>\u00a0<\/span><\/p>\n

A decade ago, the failure\/challenge rates were as high as 60-70%.\u00a0<\/span>The overall project & portfolio management consulting & vendor spend is increasing against the increasing failure rates. McKinsey reported that<\/span>\u00a070% of all change initiatives fail.\u00a0<\/span>The top 10 reasons for failure are:<\/span>\u00a0<\/span><\/p>\n

    \n
  1. Incomplete requirements<\/span>\u00a0<\/span><\/li>\n
  2. Lack of user involvement<\/span>\u00a0<\/span><\/li>\n
  3. Lack of resources<\/span>\u00a0<\/span><\/li>\n
  4. Unrealistic expectations<\/span>\u00a0<\/span><\/li>\n
  5. Lack of executive support<\/span>\u00a0<\/span><\/li>\n
  6. Chan<\/span>g<\/span>ing requirements<\/span>\u00a0<\/span><\/li>\n
  7. Lack of planning<\/span>\u00a0<\/span><\/li>\n
  8. Didn\u2019t need it any longer<\/span>\u00a0<\/span><\/li>\n
  9. Lack of IT management<\/span>\u00a0<\/span><\/li>\n
  10. Technology illiteracy<\/span>\u00a0<\/span><\/li>\n<\/ol>\n

    50% of the time, DevOps implementation is challenged by \u2018people issues\u2019.\u00a0<\/span>The secret to overcoming these hurdles lies in the resolution of these issues and changing the behavior.<\/span>\u00a0<\/span>Behemoths like Amazon, Etsy, Facebook, Google, Netflix, and WalmartLabs are leading the race because they know the secret<\/span>.\u00a0<\/span>Etsy deploys to its production servers 50 times a day while Facebook releases 100 million lines of code daily. Google runs over 500 million tests per day inside its systems and Amazon deploys code every 11.7 seconds, on average.<\/span>\u00a0<\/span>The unification of software development, testing, and deployment activities enable<\/span>s<\/span>\u00a0enterprises to improve and evolve software products rapidly and efficiently.<\/span>\u00a0<\/span><\/p>\n

    Scot Raymond Hanley, Head of QA at Synovus, spoke at our recent Meetup in Atlanta about\u00a0<\/span>transforming from legacy QA to DevOps in the enterprises<\/span><\/a>. This blog summarizes the key takeaways from his in-depth presentation<\/span>. Let\u2019s dig in:<\/span>\u00a0<\/span><\/p>\n

    Evolution of behavior leading the evolution of quality<\/span><\/b>\u00a0<\/span><\/h3>\n

    T<\/span>he annual release frequency in Waterfall<\/span>\u00a0<\/span>is<\/span>\u00a0reduced to quarterly\/monthly releases with Agile. With DevOps, the release frequency has shortened to weeks, days, and hours. The segregated, siloed Dev, Ops, and Test\u00a0<\/span>teams\u00a0<\/span>work collaboratively, together, simultaneously under\u00a0<\/span>the\u00a0<\/span>DevOps framework. From long, phase-wise testing at the end of a long development cycle, we have moved on to in-sprint testing strategies and unattended automation aligned with build frequency in the CI\/CD pipeline. DevOps methodology allow<\/span>s<\/span>\u00a0organizations to focus on in-sprint end-to-end testing, non-functional engineering, continuous integration & testing, test data engineering, build readiness for operation and release, UX engineering & assurance, & automated test enabling functions such as test data & environment engineering.<\/span>\u00a0<\/span><\/p>\n

    The transition, rather<\/span>,<\/span>\u00a0evolution from Waterfall to Agile & DevOps is not only technical \u2013\u00a0<\/span>it is behavioral.<\/span><\/i>\u00a0<\/span>It is about instilling end-to-end visibility across the SDLC. It is about\u00a0<\/span>exposing<\/span>\u00a0a failure and\u00a0<\/span>making it transparent<\/span>\u00a0to learn from it and avoid it in the future.<\/span>\u00a0It is about\u00a0<\/span>emphasizing<\/span>\u00a0Q<\/span>uality Assurance to\u00a0<\/span>lower risks, allow incremental changes, and conquer change resistance.<\/span>\u00a0<\/span><\/p>\n

    Transitioning from Quality Assurance to Quality Engineering<\/span><\/b>\u00a0<\/span><\/h3>\n

    Cloud computing & serverless architectures are in vogue. Organizations are formulating container-first strategies. They are adopting DevSecOps and dual-shift quality automation approach for making quality inherent in the SDLC. This shift from traditional to built-in quality approach is mainly because of the rising cost\u00a0<\/span>of defects in production. Extreme automation with integrated quality engineering techniques\u00a0<\/span>is becoming<\/span>\u00a0a cornerstone\u00a0<\/span>of<\/span>\u00a0daily deployments. A paradigm shift<\/span>\u00a0is being observed<\/span>\u00a0towards BDD with TDD delivery practices<\/span>\u00a0while\u00a0<\/span>the role of quality<\/span>\u00a0is getting extended<\/span>\u00a0to Ops and post-production.\u00a0<\/span>\u00a0<\/span><\/p>\n

    Navigating your DevOps<\/span><\/b>\u00a0implementation<\/span><\/b>\u00a0journey<\/span><\/b>\u00a0<\/span><\/h3>\n

    For a successful implementation<\/span>, organization<\/span>s<\/span>\u00a0need to take an all-rounded<\/span>\u00a0DevOps<\/span>\u00a0approach that includes automation, data engineering, non-functional engineering, continuous monitoring, governance, and infrastructure automation.\u00a0<\/span>\u00a0<\/span><\/p>\n

    \u00a0 \u00a0 1. Automation:<\/span><\/b>\u00a0<\/span><\/p>\n