BT

Your opinion matters! Please fill in the InfoQ Survey!

Which Practices Contribute the Most for Successfully Implementing a DevOps Culture?

| by Manuel Pais Follow 6 Followers on Sep 29, 2015 |

InfoQ's research widget has been deprecated. It should continue to work however, and we hope to relaunch it at some point in the future.

InfoQ is currently running a series of articles on "Patterns of DevOps Culture", highlighting some of the practices and patterns commonly found in organizations exhibiting a successful DevOps culture.

As part of that initiative we wanted to know which practices you believe contribute the most towards an environment of collaboration (across the board), sharing (continuous learning) and ownership (of both successes and failures). In other words, what moves the needle towards DevOps?

Here's the list we've gathered so far, in no particular order:

  • Devs pair programming with Ops on joint tasks
  • Devs responsible for application deployments (manual or automated)
  • Devs have root access to production systems
  • Automated machine provisioning (private or public cloud)
  • Infrastructure as code (using configuration management tools such as Puppet, Chef, etc)
  • Devs on-call (first line incident response)
  • Devs monitoring application performance (and understanding system performance)
  • Blameless post-mortems (including everyone involved in outages)
  • Having ops engineer(s) embedded in the development/product team
  • Having a dedicated team responsible for deployments and infrastructure management
  • Self-service (automated) production-like environments (infrastructure-as-a-service)
  • Including operational requirements in the sprint/backlog
  • Devs and Ops joint daily stand-up meetings
  • Devs and Ops joint retrospective meetings
  • Shared goals and responsibilities for key metrics
  • Highly visible, shared dashboards showing key metrics
  • Kanban-style board including Dev and Ops work in progress
  • Infrastructure code reviews (in any form - async or in person)
  • Mentoring other teams' members (for e.g. Devs teaching programming practices to Ops)

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Nice by alicia worthington

I will go with
1- Devs responsible for application deployments (manual or automated) 2- Infrastructure as code (using configuration management tools such as Puppet, Chef, etc)
3- evs monitoring application performance (and understanding system performance) like we are doing with our App like SmartIOApp.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

1 Discuss

Sponsored Content

Login to InfoQ to interact with what matters most to you.


Recover your password...

Follow

Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.

Like

More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.

Notifications

Stay up-to-date

Set up your notifications and don't miss out on content that matters to you

BT