DZone
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
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones AWS Cloud
by AWS Developer Relations
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones
AWS Cloud
by AWS Developer Relations
The Latest "Software Integration: The Intersection of APIs, Microservices, and Cloud-Based Systems" Trend Report
Get the report
  1. DZone
  2. Testing, Deployment, and Maintenance
  3. DevOps and CI/CD
  4. DevOps Is a Philosophy, Not a Title

DevOps Is a Philosophy, Not a Title

Presenting the practices of DevOps at an organizational level instead of an individual level is the only way to reap its benefits.

Joshua Platt user avatar by
Joshua Platt
·
Apr. 15, 19 · Opinion
Like (9)
Save
Tweet
Share
8.54K Views

Join the DZone community and get the full member experience.

Join For Free

Whenever I discuss DevOps with someone outside of engineering, there is a common theme to their reaction, something along the lines of, “Oh, is that a new position in IT?”

This bothers me because it implies DevOps:

  • is new, and somehow duct-taped onto IT;
  • is the responsibility of someone or a small group;
  • that someone is not them.

In some ways, this reaction is not wrong. Organizations often have people with titles like DevOps Engineer, DevOps System Admin, DevOps architect; all imply that one person is responsible for DevOps. It ties DevOps to a title and makes it their job. Or worse, it implies you can stick DevOps in front of SysAdmin, and viola, you are doing DevOps. This checks the box, but does not deliver the true benefit of DevOps.

Examine high-performing organizations where DevOps has reached wide adoption, and you will see this reaction is quite wrong. In these organizations, it is not simply a job title constrained to an individual or even a small team. It is a philosophy adopted by the entire organization. When DevOps is approached as a philosophy, it becomes:

  • A company-wide priority, not duct taped on;
  • Everyone’s responsibility, not an individual's;
  • A personal responsibility for everyone in the organization.

It might seem odd, but in practice, it further breaks down silos of action and communication. It becomes part of the culture, part of hiring and training for everyone. From support to QA, development to operations, all the way up to management. Everyone feels empowered and approaches their activities as part of the larger initiative of delivering features the customers want, more quickly, and with fewer bugs.

This philosophical approach at an organizational level has historical precedent. Lean was never a job title in manufacturing. There were no Lean production managers, there were just production managers. Instead, Lean was the philosophy Toyota applied to how they manufactured cars across the entire organization. It was not one person’s responsibility to improve quality, it was everyone’s. Toyota’s transformation from also-ran to market leader in just a few short years is evidence a philosophical approach is a winning approach.

Adopting a new philosophy will impact many areas of the organization, and might even be painful. But it will be worth it. Most of all it is a journey. A methodical movement toward the goal of delivering more value, fewer bugs, more efficiently.

DevOps philosophy

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Documentation 101: How to Properly Document Your Cloud Infrastructure Project
  • Reliability Is Slowing You Down
  • Create a CLI Chatbot With the ChatGPT API and Node.js
  • Choosing the Right Framework for Your Project

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • 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: