In short
Sneha Poddar argues that DevOps delivers its real value when it is a shared team culture, not a role handed to a separate group. When developers own their code all the way to production, silos disappear, quality and speed improve, and costs fall over time. Getting there means closing skill gaps, automating relentlessly, accepting an early slowdown and releasing far more often.
Key takeaways
- A closer look at DevOps: its definition and importance.
- Key benefits of working in a DevOps team versus a traditional team.
- Understanding how DevOps can reduce bottlenecks in the 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.
The wall of confusion
Poddar starts with a plain definition. DevOps combines two kinds of work: the development team identifies tasks, plans, writes, tests and builds code, while the operations team deploys and releases finished features and monitors them in production. The trouble begins when those two halves sit in different groups.
In her experience, the biggest problem with DevOps as a role is that teams work in silos. Developers have no idea about deployment or release, and operations has no idea which features are being built. "This often results in a wall of confusion." (1:49) The practical consequence is concrete: operations cannot tell which build of which service belongs in which environment, and the wrong build often ends up in the wrong environment, causing production issues.
From a role to end-to-end ownership
Her answer is to remove the wall rather than manage around it. "By promoting a DevOps culture within a team, we basically empower each team member to be anyone they can be as per the requirement." (2:16) In this model, the person who writes the code is also the person who tests it, builds it, deploys it and watches it in production.
"The developer now has end to end responsibility, not only to write his code, but also to deliver the code all the way to production." (2:16) Having worked in both role-based and culture-based DevOps teams over five years, Poddar reports what she observed in the culture-based ones: higher productivity, collaboration and trust, better product quality and reliability, faster delivery and higher customer satisfaction. Because a team that delivers faster spends less to ship the same product, she also points to a substantial reduction in delivery cost over time.
Close the skill gap and automate
The first practical step is personal. To be able to take on any role in a team, each person needs to identify what they do not yet know and learn it. A developer stepping into operations work, for example, needs to pick up deployment tooling such as Docker and Helm.
The second step is automation, which Poddar treats as non-negotiable. "A foundation of any of the DevOps culture lies in automation." (4:33) She suggests three things teams can begin with immediately. First, automated tests, which many teams already write regardless of their culture, so they may already have one box ticked. Second, automated deployment using tools like Docker and Helm, so that nobody has to deploy or roll back by hand when something goes wrong. Third, continuous monitoring with tools like Prometheus that watch the application and raise alerts when issues appear.
Change the mindset and expect a slowdown
Tooling alone does not create a culture. Poddar's next piece of advice is aimed at anyone willing to step outside their comfort zone. "The change of mindset starts with being accountable for your work and taking responsibility from end to end." (6:12)
She is candid about the cost. A cultural change comes with a learning curve, and it will slow the team down at first because people are learning tools they have never used. Her advice is not to feel guilty about shipping fewer features in that period. "But with time, the process and the product delivery will definitely increase." (6:43)
Release continuously
The final change concerns cadence. Traditionally, she notes, teams released to production about once a sprint or even once every two sprints, whether or not they followed agile or DevOps practices. "Lastly, continuously integrate and release the code." (7:10) Continuous integration and frequent releases bring quick customer feedback, which she describes as essential to a successful DevOps culture.
Poddar closes by asking viewers to motivate their own teams and spread knowledge about DevOps culture, acknowledging that a full shift will not happen overnight but that understanding the needed changes is where it begins.
Watch the talk
"DevOps is not a role, its a culture" by Sneha Poddar, about 8 minutes: https://www.womentech.net/video/devops-not-role-its-culture-sneha-poddar
About the speaker
Sneha Poddar is a Technical Lead with more than seven years of experience and a graduate in MIS from Carnegie Mellon, passionate about UI development, improving product UX and teaching best coding practices. She promotes quality over speed in delivery, loves pair and mob programming, and aims to become a Software Architect and, in the longer term, a CTO.
Questions this talk answers
- Why is DevOps as a separate role a problem?
- What does DevOps as a culture look like in practice?
- What benefits has the speaker seen in DevOps-culture teams?
- Where should a team start with automation?
- Will adopting a DevOps culture slow the team down?
Drafted with AI from the talk transcript. Editor review pending.