Seven Habits of Highly Effective DevOps

DevOps Drive-InGlenn O’Donnell, Principal Analyst at Forrester paid a visit to Serena Software headquarters in San Mateo, CA this week and joined us for our monthly DevOps Drive-In webcast.  IT is in its own industrial revolution according to Glenn, in part because IT is currently too slow, has poor quality and customers don’t trust IT.  This revolution requires an IT fitness program and not a weight loss program where IT becomes stronger, faster and more resilient.  To improve quickly, IT needs to embrace Lean principles and methodologies.

Glenn provided an overview of how IT can leverage Lean value stream mapping and the DevOps principles of automation and culture to eliminate waste, increase quality and reduce cycle times.  He also outlined the “Seven Habits of Highly Effective DevOps.” These habits are:

  1. Establish common values and awareness across a common Dev and Ops community.
  2. Take an “outside in” approach to everything.
  3. Automate your build, testing and release management processes.
  4. Standardize the services and the components used to build these services.
  5. Instill a culture of systems engineering across Dev and Ops.
  6. Implement feedback and feed-forward in the service lifecycle.
  7. Put developers on the front line of service support.

During the webinar, we polled attendees and asked them to select which of the seven habits they thought would be the highest priority to improve their organization. Below is a graph of the results.

 

The majority believes automation and establishing common values and awareness between Dev and Ops would provide the most improvement to their organization.  I was surprised having developers on the front line of service support and implementing feedback loops scored so low.  Changing the culture is harder to do but I do like the DevOps principle of shared accountability and the “If I’m awake, you are awake” mentality.  If an operations person gets woken up early in the morning, the responsible developer should work alongside them until the problem is resolved.  You would get faster MTTR and improve reliability and quality.

It was a great DevOps Drive-in.  Thanks goes to Glenn and Forrester.  Make sure you catch our next DevOps Drive-in webcast on April 23rd.  We are teaming up with Cloudbees to discuss the challenges of Enterprise Continuous Delivery.


Mark Levy is a Product Marketing Manager at Serena Software focusing on DevOps and the Enterprise. He has over 25 years of experience in enterprise software, focusing on both application development and IT operations.

Tags: DevOps


Comments

Eugene on May 13th, 2014 at 2:50 am

Hi Mark,

Interesting results you got from the poll. From my point of view, #4 and #5 are the primary goals for esablishing great DevOps cooperation, but looks like the majority of respondents think in another way.

We at Oxagile have decided to take a closer look at DevOps and try to find out its benefits for our business. The first thoughts on DevOps are here: http://www.oxagile.com/company/blog/devops-your-team/

Regards,
Eugene

Mark on May 14th, 2014 at 3:13 pm

Hi Eugene,

That is a good point of view to have! All of these “Habits” are highly effective and should be primary goals. I think automation is favored because it’s something that can reduce cycle times, is measurable, and can provide a quick win, whereas #4 and #5 generally take longer to implement and see value. I believe that all of these principles are important and can provide tremendous value to IT and ultimately to the business.

Best Regards
Mark

Post Comment
Name: 
Email: 
URL: 
Comments: 
  Subscribe by email