Over a million developers have joined DZone.

Continuous Delivery and the Four Tech Adopter Personality Types

DZone's Guide to

Continuous Delivery and the Four Tech Adopter Personality Types

· DevOps Zone ·
Free Resource

Learn how integrating security into DevOps to deliver "DevSecOps" requires changing mindsets, processes and technology.

By Yaniv Yehuda

We all like to think of ourselves at innovators, working in tech, we are usually exposed to new technologies, new ideas and new concepts well before the general population.

Here are the “Four personality types of tech adopters”:

  • Innovators adopt simply because it is new. They love exploring for the sake of exploring and the excitement it brings, and they are willing to take risks.
  • Early adopters (often thought leaders) are similar to innovators in how quickly they adopt, they will also provide candid feedback to help vendors refine their future product releases, as well as the associated means of distribution, service, and support.
  • Early majority and late majority are the critical mass that ensure adoption. The early majority looks for productivity and practical benefits more than coolness or reputation. The late majority are similar but also expects a lot of help and support before they are willing to commit.
  • Laggards are slow to adopt. They are the most resistant to change and do so only when they have to, because everyone else has.

Continuous Delivery, which has already been adopted by 55% of the companies according to this survey, has passed into late majority stage.

Continuous Delivery is considered a proven practice, with well-established benefits:

  • Discover software defects as early as possible rather than late in the lifecycle – or worse, in production.
  • Use Agile to speed up development, and don’t see benefits evaporate once the app goes into production.
  • Pinpoint problems across development, testing, and production operations.
  • Prevent simple human errors from wreaking havoc during development and deployment.
  • Make sure you shift focus from blamestorming to brainstorming :)

A recent IBM blog showed just how big of a difference the acceleration of delivery cycles can make:

“(we have made) good progress with our internal DevOps journey, particularly around acceleration of delivery cycles. Highlights from the most recent 2 – 3 years include:

  • Project Initiation – 10 days to 2 days – 8 days faster
  • Overall Time to Development – 55 days to 3 days – 52 days faster
  • Build Verification Test Availability – 18 hours to < 1 hour – 17 hours faster
  • Overall Time to Production – 3 days to 2 day – 1 day faster
  • Time Between Releases – 12 months to 3 months – 9 months faster

I should note that the gains are even more impressive looking over the life of the transformation.

As the General Manager for IBM Rational, I represent the business line. And the most exciting numbers from these results are a shift in share of resources focused on innovation (vs. maintenance) – from 58% to nearly 80% during the period, increasing the share of innovative work by 37%” (source here)

If you haven’t started implementing Continuous Delivery in your company, you are now part of the late majority to adopt it – which is fine if we were talking about gadgets, but not so fine if you are considering business competing to have the fastest time to market in this fast moving world.

Don’t slip into the laggards section of the graph – the time to implement is now!

And don’t forget about your Database when planning or implementing your Continuous Delivery adoption…

Read about the state of database continuous delivery here

About the Author

Yaniv Yehuda is the Co-Founder and CTO of DBmaestro, an Enterprise Software Development Company focusing on database development and deployment technologies. Yaniv is also the Co-Founder and the head of development for Extreme Technology, an IT service provider for the Israeli market. Yaniv was a captain in Mamram, the Israel Defense Forces computer centers where he served as a software engineering manager.

Learn how enterprises are using tools to automate security in their DevOps toolchain with these DevSecOps Reference Architectures.


Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}