0:008:29

DevOps is not a role, its a culture

Sneha Poddar 8:29 2022

Wrong builds reach production when developers and ops never talk

When developers know nothing about releases and operations know nothing about the features in flight, the wrong build lands in the wrong environment and production breaks. Sneha Poddar, a technical lead who has worked in both role-based and culture-based DevOps teams, has watched that wall of confusion form. What can a team change starting today to tear it down, and what will it cost at first?

Get the concrete changes that turn DevOps from a job title into a shared team habit

Watch on YouTube

In short

Sneha Poddar argues that DevOps works best as a team culture rather than a separate role, because split development and operations teams create a wall of confusion that sends wrong builds to production. Drawing on five years in both kinds of teams, she outlines the benefits she has seen and the practical changes a team can start today: bridging skill gaps, automating tests, deployment and monitoring, owning work end to end, and releasing continuously.

“By promoting a DevOps culture within a team, we basically empower each team member to be anyone they can be as per the requirement.”
“A foundation of any of the DevOps culture lies in automation.”

What you will learn

  • Explain the difference between DevOps as a role and DevOps as a team culture.
  • Spot the silo symptoms, such as wrong builds deployed to wrong environments, that signal a wall between dev and ops.
  • Identify your own skill gaps in operations tooling like Docker and Helm and plan how to close them.
  • Prioritize three automation starting points: automated tests, automated deployment with rollback, and monitoring with alerts.
  • Set realistic expectations for the early slowdown while a team learns new tools and moves to continuous release.

Key takeaways from the speaker

  • A closer look at DevOps its definition and importance.
  • Key benefits of working in a DevOps team vs traditional
  • Understanding how devOps can reduce bottlenecks in process and expedite product delivery
  • Recommendations on incremental changes that can be made to overcome silos within a team.
  • Even though a sudden cultural shift is not possible, understanding the required changes is a viable starting point

Details

Level
Beginner
Format
Lightning talk
Technical depth
Introductory technical
For
Early career, Mid-career, People manager
Length
8:29
Published
July 2022

Questions this talk answers

Why is DevOps as a separate role a problem?

Development and operations end up working in silos, creating a wall of confusion where ops does not know which build of which service goes to which environment. This often leads to wrong builds in the wrong environment and production issues.

What does DevOps as a culture look like in practice?

Each developer takes end-to-end responsibility: writing, testing, building, deploying and monitoring their code all the way to production.

What benefits has the speaker seen in DevOps-culture teams?

She noticed higher productivity, collaboration and trust, better product quality, reliability and delivery speed, higher customer satisfaction and a lower cost to deliver over time.

Where should a team start with automation?

Start with automated tests, then automate code deployment with tools like Docker and Helm so rollbacks are not manual, and use tools like Prometheus to monitor the application and send alerts.

Will adopting a DevOps culture slow the team down?

Yes, at first, because people are learning tools they have not used before, so teams should not feel guilty about delivering fewer features initially. Over time, process and delivery speed improve.

About this talk

For decades, software folks have had separate roles as developers or testers or DevOps or automation engineers. But what if today one could be all? Now is the time to rethink the way we work and take end-to-end responsibility for our work. During my talk, I would like to introduce DevOps and how one can be anyone or all in a team. Did you know that DevOps is not a role but a team culture? With +7 of work experience in both traditional and DevOps cultured teams, I want to share why we need DevOps culture today more than ever. DevOps culture is an ultimate solution to quench the thirst of SDLC knowledge. The best time to switch to DevOps culture was yesterday and the second-best time is now. In my lightning talk, I would share five key changes that can be made today by the teams willing to adopt DevOps culture.

Topics

Related talks

Browse the library