This is the third post in a series of three by effectual CEO, Robb Allen. The first two posts can be read here:
     • Embracing DevOps to Solve IT Tension
     • Defusing the Tension

Key Takeaways

  • Successfully adopting DevOps means embracing a new culture, not just a new methodology — engineering and IT must work together throughout the product lifecycle, sometimes as a single merged team.
  • A 2017 survey of 450 C-level and VP/director executives found 54% already used DevOps methodologies during cloud migrations, according to AWS's Global Head of Partner Ecosystem for Cloud Migrations.
  • Fostering DevOps collaboration requires concrete steps: unified reporting structures, cross-functional teams, automating repetitive tasks, and making feedback a core part of the workflow.
  • The 2016 State of DevOps Report from Puppet found DevOps adoption drove a 200-fold increase in deployment frequency, 24 times faster recovery, and a 3-times decrease in change failure rates.
  • Cloud deployment is a natural moment to start adopting DevOps culture change — done well, it benefits both business outcomes and team morale.

The successful adoption of DevOps is about much more than accepting a new methodology – it means embracing a new culture. DevOps methodology requires seeing engineering and IT more holistically. They work together throughout the product lifecycle, with some organizations merging them into a single team.

DevOps culture decreases time to market while increasing reliability, scale, and security through closer collaboration between development (engineering) and operations (IT). It can require a sea change in your company’s culture, but again — the costs of not adopting DevOps can be far greater.

DevOps methodology requires seeing engineering and IT more holistically.

Fostering Communication and Cooperation

  • Create a unified reporting structure for DevOps teams. Set clear expectations and guidelines, driven by fundamental values.
  • Build cross-functional teams including both engineers and IT technicians.
  • Leverage engineers to assist IT technicians in understanding complexities involved in delivering business features.
  • Leverage IT technicians to help engineers understand how involved 24/7 support of those features is.
  • Automate repetitive tasks, freeing up engineers and IT technicians to perform more creative, value-adding work while reducing human error.
  • Make feedback a fundamental feature of workflow to encourage communication-driven action. Create a culture of data sharing.

Driving Improvements through DevOps

While DevOps is generally part of product development, it can also be an invaluable tool during cloud migration. No less an authority than Bina Khimani, Global Head of Partner Ecosystem (Cloud Migrations) at Amazon Web Services, made this case in late 2017. A survey of 450 C-level and VP/director-level executives in the United States, Canada, and the UK found 54 percent already leveraged DevOps methodologies.

This is not an easy direction to move in, even with the best circumstances. It requires unwavering leadership in the truest sense of the word. However, the rewards are wide-ranging, including:

  • Continuous development with shorter development timetables.
  • Decreased complexity.
  • Faster problem resolution.
  • More productive teams with higher morale and engagement.
  • More opportunities for professional development.
  • More time spent creating and innovating, as opposed to fixing and maintaining.

The Undeniable Benefits

The 2016 State of DevOps Report from Puppet found DevOps adoption resulted in a 200-fold increase in deployment times, 24x increase in recovery times, and a 3x decrease in change failure rates.

Cloud deployment can be the perfect time to start adopting these changes in your organizational culture. Successful adoption means that not only does everyone win, but everyone will feel like they’ve won as well. That’s a value you just can’t put a price on.

Robb Allen is the CEO of Effectual Inc.

Frequently Asked Questions

Is DevOps just a new methodology, or something bigger?

According to the article, successful DevOps adoption is fundamentally a culture change — it requires engineering and IT to work together holistically throughout the product lifecycle, sometimes merging into a single team, not just adopting new tools.

How common is DevOps adoption during cloud migrations?

A survey of 450 C-level and VP/director-level executives across the US, Canada, and the UK found that 54% already leveraged DevOps methodologies, a trend highlighted by AWS's own Global Head of Partner Ecosystem for Cloud Migrations in late 2017.

What practical steps help foster DevOps collaboration between engineering and IT?

Creating a unified reporting structure, building cross-functional teams, having each side help the other understand its challenges, automating repetitive tasks, and building continuous feedback into the workflow.

What measurable benefits does DevOps adoption deliver?

Per the 2016 State of DevOps Report from Puppet, organizations that adopted DevOps saw a 200-fold increase in deployment frequency, 24 times faster recovery from failures, and a 3-times lower change failure rate.

Why is cloud migration a good time to adopt DevOps?

Cloud deployment naturally coincides with organizational change, making it a practical entry point for adopting DevOps culture — the article argues that when adoption succeeds, everyone benefits and feels like they've won.