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 Video Library
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
View Events Video Library
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
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

Integrating PostgreSQL Databases with ANF: Join this workshop to learn how to create a PostgreSQL server using Instaclustr’s managed service

Mobile Database Essentials: Assess data needs, storage requirements, and more when leveraging databases for cloud and edge applications.

Monitoring and Observability for LLMs: Datadog and Google Cloud discuss how to achieve optimal AI model performance.

Automated Testing: The latest on architecture, TDD, and the benefits of AI and low-code tools.

Related

  • Three Ways AI Is Reshaping DevSecOps
  • DevSecOps: Integrating Security Into Your DevOps Workflow
  • What Technical Skills Can You Expect To Gain From a DevOps Course Syllabus?
  • How To Start a Successful Career in DevOps

Trending

  • Difference Between High-Level and Low-Level Programming Languages
  • How To Start a Successful Career in DevOps
  • [DZone Research] Join Us for Our 5th Annual Kubernetes Survey!
  • Continuous Integration vs. Continuous Deployment
  1. DZone
  2. Testing, Deployment, and Maintenance
  3. DevOps and CI/CD
  4. 7 Habits of Successful DevOps

7 Habits of Successful DevOps

An overview of a recent DevOps.com podcast reviewing some DevOps best practices.

Yaniv Yehuda user avatar by
Yaniv Yehuda
·
Jan. 16, 16 · Opinion
Like (6)
Save
Tweet
Share
7.60K Views

Join the DZone community and get the full member experience.

Join For Free

Alan Shimel of DevOps.com recently sat down with Sam Guckenheimer of Microsoft for an interview on the seven habits of successful DevOps. Below is an overview. Check out the full podcast here.

  1. Team Autonomy and Enterprise Alignment
    Scrum teams should autonomously pull items from a common product backlog, and at the same time, align to enterprise goals on a six month planning cycle. In that time frame it should be clear what needles you’re trying to move for the business. You can then measure, how you’re doing against that. They may move forward, they may move backward, they may decide, based on the data they’re collecting to do more or do something else. But you know, what’s in their control based on the things they’ve agreed for the six months.
  2. Rigorous Management of Technical Debt
    When you’re running a service, you really can’t afford to let any debt creep in, and you have to stay clean all the time. To do that, you must constantly monitor both what’s happening in the production service and what’s happening in the development process. So for example, if there’s anything happening in the development process, like a feature crew is letting its bug count start to ride up, they have to stop immediately, fix the bugs, and you can’t do any new work until they get them down to zero, so that you remain clean on tech debt as you’re go.
  3. Focus on the Flow of Customer Value
    Look at how people use your software, both quantitatively; that is – actually observe what gets used, what doesn’t get used, what the scenarios are – and reach out to customers qualitatively; engage with the high usage accounts and encourage your engineers to buddy up and find out what’s gone well, what’s gone not so well and what they would like you to do. 

    Download our latest white paper: Pitfalls to avoid while evaluating DevOps for database solutions.
  4. Hypothesis Driven Development
    The backlog is a set of hypotheses or beliefs. The hypotheses must be turned into experiments, and you have to collect data against those experiments so that you can substantiate or diminish the hypothesis.
  5. Evidence Gathered in Production
    Everything is evidence that is needed in order to build up or draw down against those hypotheses. You can use instrumentation and telemetry and measure it against what’s important. So, for example, run the new against the old in parallel, and see what the evidence shows you about how much better the new is than the old – if indeed it is at all.
  6. Live Site Culture
    The idea of a live site culture is that the site status is always first priority. If there is a live site incident, you want to, as quickly as possible, remediate so that customers aren’t affected, and you want to drive to a root cause analysis. Getting to the root cause allows you to identify the actions that you need to take in order to prevent a recurrence of such an incident or something similar. Learn from live site incidents so that you’re always getting better.
  7. Manage Infrastructure as a Flexible Resource
    Start each Sprintly deployment with a canary instance, so that you know from the canary if there’s anything wrong with the deployment, and if there is, you can then restart at the canary before you roll out to the subsequent deployment rings. This practice of canary-ing, is part of the deployment pipeline. You can then use the automation to roll out in subsequent rings in order to harden the service and get to a global scale on a regular basis.
DevOps

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

Opinions expressed by DZone contributors are their own.

Related

  • Three Ways AI Is Reshaping DevSecOps
  • DevSecOps: Integrating Security Into Your DevOps Workflow
  • What Technical Skills Can You Expect To Gain From a DevOps Course Syllabus?
  • How To Start a Successful Career in DevOps

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

  • 3343 Perimeter Hill Drive
  • Suite 100
  • Nashville, TN 37211
  • support@dzone.com

Let's be friends: