2i Testing | Copyright |© 2016

Purpose of this presentationDevOps has really gained traction over the last few years and has proven, where successful to be a very efficient operating model.

But what are the pitfalls?

What needs to be in place from a Staff/Tooling/Environment perspective?

When should you try to move to a DevOps model?

Most of all from the perspective of Testing, where do we fit?

Recently 2i attended a DevOps summit in London to try and learn more about how different companies have implemented DevOps and build our understanding of the Operating model so that we can better advise our clients.

2i Testing | Copyright |© 2016

So what is DevOpsWhile researching online we are faced with quite a few differing takes on what DevOps is, there is however a very common thread throughout.

CULTURE PROCESS PEOPLE

These are the key elements to DevOps and embedding this within a delivery setting. Teams that are built up of individual talents (Developers, Sysadmins and Testers) can add a huge benefit with the correct team work and attitude, without this it is almost impossible. When people collaborate, communicate and integrate the Team and business as a whole move forward.DevOps represents a change in IT culture, focusing on rapid IT service delivery through the adoption of agile, lean practices in the context of a system-oriented approach. DevOps emphasizes people (and culture), and seeks to improve collaboration between operations and development teams. DevOps implementations utilize technology — especially automation tools that can leverage an increasingly programmable and dynamic infrastructure from a life cycle perspective. Gartner

2i Testing | Copyright |© 2016

DevOps is not:Simply the

combination of Dev and Ops

A separate team

A tool

all about Automation

one size fits all

2i Testing | Copyright |© 2016

Cultural and structural changeTraditional

Silo

Architecture

Development

Test

Operations

Product Teams

BA

ArchitectureDevelopmentCustomer ExTestMkt AnalyticsOperationsProduction- SupportBusiness

To gather more information on the subject of DevOps we recently attended the Computer weekly DevOps Summit in London. We have selected some of the slides from the opening presentation by Dan Worth which we believe apply to our clients and industries in which we operate.

DevOps Summit facts and figures

State Of DevOps (puppet)Each year puppet create a “State of DevOps” report. This report is conducted by gathering insight from both puppet’s client base and the wider IT industry. Over the past 5 years they have surveyed 25000 technical professionals to understand cultural norms and lean management practices associated with DevOps.

State Of DevOps (puppet)Key findings 1. High-performing organizations are decisively outperforming their lower-

performing peers in terms of throughput. High performers deploy 200 timesmore frequently than low performers, with 2,555 times faster lead times. They also continue to significantly outperform low performers, with 24 times faster recovery times and three times lower change failure rates.

2. High performers have better employee loyalty, as measured by employee Net Promoter Score (eNPS). Employees in high-performing organizations were2.2 times more likely to recommend their organization to a friend as a great place to work, and 1.8 times more likely to recommend their team to a friend as a great working environment. Other studies have shown that this is correlated with better business outcomes.

State Of DevOps (puppet)3. Improving quality is everyone’s job. High-performing organizations spend 22 percent less time on unplanned work and rework. As a result, they are able to spend 29 percent more time on new work, such as new features or code. They are able to do this because they build quality into each stage of the development process through the use of continuous delivery practices, instead of retrofitting quality at the end of a development cycle. 4 . High performers spend 50 percent less time remediating security issues than low performers. By better integrating information security objectives into daily work, teams achieve higher levels of IT performance and build more secure systems.

State Of DevOps (puppet)5. Taking an experimental approach to product development can improve your IT and organizational performance. The product development cycle starts long before a developer starts coding. Your product team’s ability to decompose products and features into small batches; provide visibility into the flow of work from idea to production; and gather customer feedback to iterate and improve will predict both IT performance and deployment pain. 6. Undertaking a technology transformation initiative can produce sizeable cost savings for any organization. Every technology leader wants to know what return to expect on investing in a technology transformation. Using key metrics from this report, as well as industry benchmarks, we’ve provided formulas to help you quantify your potential cost savings, using metrics from your own organization. We also provide suggestions for reinvesting those savings to improve IT and organizational performance.

State Of DevOps (puppet)Compared to last year, high performers significantly improved throughput, going from 200 deploys per year to 1,460 deploys per year. They have also improved their lead time for changes, going from days to minutes. Low performers, on the other hand, have maintained the same level of throughput for the past three years. Both high and low performers are maintaining their stability, with high performers recovering in less than an hour. Understanding the ROI of DevOps, downtime can have a real impact on the bottom line. It’s also highly visible to customers, C-level executives and in some cases, the media. So in addition to financial costs, downtime can also incur reputational costs.

What did we learn• DevOps is a culture not a role. If the correct culture of open

communication, support and collaboration does not exist, moving to a DevOps framework will not be a success and will not return the perceived benefits. The right culture needs be have buy in from all areas of the organisation and good sponsorship from senior management.

• You need to be prepared to be more open to risk and failure in a DevOps framework. This is not advocating taking risks for the sake of it, but to understand the risks you are dealing with, try things, and if they don’t work change them as required so that they work next time. Create a collaborative culture of open communication, support and continuous learning. We learn more from our failures than we do our successes. Don’t be afraid to change things if they are not working. Make the changes and move on.

2i Testing | Copyright |© 2016

What did we learn• From a skillset perspective - We do believe this reinforces the need

for testers to become more technically minded. Our continued shift left, which started with the introduction of Agile, has brought testing closer than ever to development. The more technically minded we are as testers the easier we will find it to harness the tools available to the development team and utilise them for ourselves. Imagine a world where you can spin up your own environments, create your own simulators or inject your own data.• From a testers perspective - We have have changed our minds

somewhat. Prior to the Summit, we had in our minds that this would be a seismic shift for test, however, if you work in a fully agile test team who are comfortable with Test Driven Development, Automation, Continuous Delivery and a collaborative multi team approach, the move to DevOps is a sensible one which you should embrace with open arms. If this is not the world you are working in, don’t give up but start by making small changes in culture and process that move you towards where you need to be.

2i Testing | Copyright |© 2016

Culture, Culture and Culture

“Culture over tools every time”Finbarr Joy, CTO Lebara Mobile

“DevOps is a culture not a role”Mike Dilworth, DevOps Transformation Lead

“That’s a nice strategy, but culture eats strategy for breakfast”Simon Tarry, Engineering Lead, Ticketmaster

Bibliography http://www.gartner.com/technology/home.jsp

https://puppet.com

Reference

Useful sites

http://DevOps.com

http://stickyminds.com

http://techbeacon.com

http://www.testingexcellence.com

http://www.computerweekly.com