I really enjoyed this article, Steve. Your introduction to it via recognition (Employee of the month, etc.) was excellent. We have an Employee of the month aware. I've never seen any developer or DBA get it. I think its because the work we do is so much behind the scenes, that people don't recognize it, even though if our work weren't done, then nothing that those who get the Employee of the month would have been possible.
The main thrust of your article is on how we can measure DevOps. WOW, great question! I work in state government, where traditional project management is very deeply entrenched. But, even in this environment I'm seeing small, incremental steps towards DevOps. At this point I think the metrics used to determine success are things like the number of help tickets closed or the speed with which they're closed. This article, and the link you pointed to, encourages me to begin to consider other means of measuring the success of DevOps. Without new ways of measuring the efficacy of DevOps ultimately I think it is doomed to failure, because DevOps doesn't have a direct impact upon how many help desk tickets are closed or the speed with which they're closed. I guess there are two challenges for me. First, working with my colleagues to come up with better metrics to measure DevOps efficacy, and second to convince upper management of the validity of those metrics.