DZone
DevOps Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > DevOps Zone > The Road to DevOps

The Road to DevOps

Contrary to the belief of an optimistic business, a change in process such as agile or DevOps does not happen overnight. How do we guide them on that road?

Yaniv Yehuda user avatar by
Yaniv Yehuda
·
Jun. 24, 16 · DevOps Zone · Opinion
Like (7)
Save
Tweet
3.79K Views

Join the DZone community and get the full member experience.

Join For Free

for years, software development comprised of working on major product releases with countless features, fixes, and updates. this “waterfall model,” a system of development that flows down linearly from concept to testing, has proven to be expensive, slow, and buggy. in recent years, with the implementation of devops, the waterfall model has been losing favor among companies.

devops is a system that allows for rapid progress using continuous integration and development. the devops method results in faster product releases that are small enough to change quickly if bugs or errors are found. companies employing this approach experience “60 percent fewer code deployment failures and they recover from failures 168 times faster, all the while delivering code updates 30 times faster” according to puppet's 2015 state of devops report. however, many it companies are struggling to shift from traditional software development to a devops-based methodology.

the primary reason for this difficulty is often the result of lack of desire by employees to alter or expand their roles and implement the techniques necessary for a proper transition. developers, for example, tend to be strong-willed when it comes to coding, and often fail to take responsibility for their work. testing is seen as a low-level role by high ranking coders, but sometimes it’s the lack of comfort in testing that’s to blame.

businesses are not alone, however. while a firm will always need the cooperation of all of its employees, the heavy burden often associated with implementing a devops-based continuous deployment system has been lessened by consulting firms and automation systems that can scale to support hundreds or even thousands of projects.

read about a vital area of devops often skipped over: in database automation we trust – ebook.

no transition of this magnitude is ever completely smooth. roles shift, processes change, and resistance within the workplace is not unusual. the results speak for themselves, though, with higher quality releases, faster production time and fewer bugs. the road to devops is a long one, but value it presents is unquestionable.

DevOps Software development

Published at DZone with permission of Yaniv Yehuda, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • 6 Best Books to Learn Multithreading and Concurrency in Java
  • 10 Books Every Senior Engineer Should Read
  • Why I'm Choosing Pulumi Over Terraform
  • Debugging Deadlocks and Race Conditions

Comments

DevOps Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo