Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

3 Critical Keys for DevOps Success — Experts and Customers Speak Out

DZone's Guide to

3 Critical Keys for DevOps Success — Experts and Customers Speak Out

If you're looking to make the switch to DevOps or looking to improve your current shop, keep these three critical points in mind to ensure DevOps success.

· DevOps Zone ·
Free Resource

Download the blueprint that can take a company of any maturity level all the way up to enterprise-scale continuous delivery using a combination of Automic Release Automation, Automic’s 20+ years of business automation experience, and the proven tools and practices the company is already leveraging.

We've been saying for a while that deployment automation, self-service catalogs, and modernizing with microservices are key elements for successful DevOps initiatives. But it's not just us saying that. On Thursday, March 1, three of our customers and an industry analyst got together to prove it.

Here are some highlights:

  • Chris Condo, a Senior Analyst from Forrester Research, presented the roles played by value stream mapping, automating everything, and self-service environments in DevOps success.
  • Aloisio Rocha, from NetEnt, transformed their ability to onboard new customers and sell into new markets by reducing customer deployment times from 4 hours (with downtime) to less than fifteen minutes with no downtime. They can now update their entire customer base in two weeks instead of the 18 months it used to take, a 4000% increase in speed.
  • Manish Aggarwal, from Intel, shifted quality left with a self-service catalog to manage and automate their 20,000+ test scripts. They now run 1000-fold more tests per day and increased annual releases by 2500%.
  • Gary McKay, from Somos, future-proofed his company and changed a mainframe operating mindset to an Agile/DevOps culture with microservices. Instead of taking 36 hours and 30-40 people, their releases now take less than an hour with only 5 people.

As a bonus, Aloisio graciously answered some questions from the audience with details on how they got their 4000% increase in performance (his numbers, not ours).

Q: How long did it take you at NETENT to go from 18 months to < 2 weeks?

A: It took about a year and a half with an iterative process. This included evaluation of tools, whiteboarding, learning the tool, building the pipelines, and some refactoring. And also developing trust in the automation pipelines.

Q: Did you stop and pause?

A: No we did not. It just took time to get to a stable, trustworthy and valuable automation pipeline.

Q: Did you get external help?

A: Yes, we had training and some professional services consulting from Electric Cloud in the beginning to help us understand the tool and how we could use it to fit our specific needs and environment. The rest we did on our own.

Q: What are the hurdles you faced?

A: At first we started the project with a few people that were only partly dedicated to it. So freeing up those people was one hurdle. It had a huge impact when we went for creating a real team with these people, dedicated to the task.

-Getting buy-in from stakeholders to help drive the initiative was another one. We were not showing progress and value fast enough because of the way we worked. Our initial approach was to build the automation pipelines as complete as possible before delivering. This led to a longer time before we got feedback from users, buy-in from stakeholders, and a loss of momentum.

We changed our approach and started working with MVP's (minimum viable pipelines) instead. Which led to faster feedback, which in turn led to more stable and trustworthy automation and faster time to value, which got us buy-in.

Q: Any suggestions for organizations in a similar boat?

A: If you have just started, try to show value or potential early. Prototype it or MVP it. Another key is to get feedback early and consistently - it is critical for building stability and achieving trust in what you are doing.

-It does take time to do something like this, so it is important to manage expectations, but also like I mentioned to show constant improvement and value deliveries. This is key in getting the users and stakeholders to buy into the future potential, the end goals, and to make it tangible.

-Value delivery analysis and/or value stream mapping are always key tools in these types of initiatives. But keep in mind that they can get very large, complex and sometimes not even understandable depending on the level you are doing them. It makes sense sometimes to split or layer these mappings so that you can get a clearer picture of were to focus efforts and then start to work more efficiently.

So there you have it:

  1. Set expectations early
  2. Start fast with a minimum viable pipeline
  3. Communicate constantly
  4. Improve the value as you go, and,
  5. Adapt as you learn from your feedback.

To see how you, too, can enjoy up to 4000% faster deployments and still have your evenings and weekends anxiety-free, watch the webinar!

#c9d9: Electric Cloud and DZone Come Together for Continuous Discussions Episode 89!

Remember to check out Electric Cloud and DZone's DevOps Toolchain podcast taking place on July 17 at 10 am Pacific Time! Electric Cloud's Anders Wallgren and DZone's Tom Smith will be joined by a lineup of guests from SmartBear, Atlassian, New Relic, and GitHub to discuss the current state of each stage of the DevOps toolchain. You can learn about the Continuous Discussions podcast here!

Download the ‘Practical Blueprint to Continuous Delivery’ to learn how Automic Release Automation can help you begin or continue your company’s digital transformation.

Topics:
devops ,webinar ,enterprise devops ,software development ,continuous delivery

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}