DevOps Zone is brought to you in partnership with:

Patrick Debois has been working on closing the gap between development and operations for many years. In 2009 he organized the first devopsdays.org conference and since then the world is stuck with the term 'devops'. Always seeking for opportunities to optimize the global IT instead of local optimizations. Patrick is a DZone MVB and is not an employee of DZone and has posted 39 posts at DZone. You can read more from them at their website. View Full User Profile

Devops Metrics - Velocityconf 2011

09.08.2011
| 3195 views |
  • submit to reddit

Whenever you hear a new theory or idea (like devops), people ask for proof before they engage. This is only natural I guess. This was the reason why I wanted to explore ways to measure devops success. Or rephrased: "Measuring the devops gap" . The result of my findings were presented at VelocityConf in June. While I initially planned to present with Israel Gat due to circumstances he switched at the last responsible moment with Andrew Shafer.

In the talk we used the metaphor of monitoring to explore the metrics. This probably put a lot of people on the wrong track, expecting a lot of real/ganglia metrics. The main point is that the higher level your monitoring the more interesting: measure the end-user perspective in both technical and human monitoring gives you the most value. Monitoring a server is like monitoring an individual person: good to know ,but it doesn't tell you anything on the end-result. I know this is meta-stuff , so you need your head clear to understand.

One of the nicest findings during the research was that whenever people say collaboration(in general) will improve things, there is a high demand for proof. The phrase "Collaboration is like a black hole, you can only measure it effects by looking at it's effects".

Also it makes no sense to increase the number of interactions between different groups (dev, ops, qa, mgt) for the sake of increasing it: "More interaction doesn't mean a better party" . You should work on the quality of the interactions.

A third take-away I got from the research what that in the Design world, they too are exploring ideas outside the usual user-centered design and are going the way of Participatory design. This fits directly to the devops idea, you automate and do all the stuff you need to, to free up more time in design. And there you can collaborate with your collegues, your peers from other groups and even with your end-users to test out new ideas. In the past design used to be a collective and shared ability. Only in the recent years this craft has become an individual thing.

Enjoy the presentation :


 

References
Published at DZone with permission of Patrick Debois, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)