Maybe it is me but I think that Jeff Knupps is missing the point of the "DevOps" movement. In the same paragraph that he states
"DevOps" is meant to denote a close collaboration and cross-pollination between what were previously purely development roles, purely operations roles, and purely QA roles
he goes on to say that
Developers must also take responsibility for the quality of the testing and release environments
.
I totally agree with the former but will vehemently disagree that it means the latter.
In my opinion the movement is there to stop things being thrown over the fence and deny all responsibility. Collaboration does not equate to "passing the buck" in the opposite direction to before. Again in my opinion, Jeff Knupps' rant is more likely due to experience of teams violating the principles of collaboration and just pushing back all responsibility to the source i.e. the people who created the software that it is all about (OK the real source is the business but NOONE would dare make them responsible).
As for his hierarchy, it is a gross simplification. Too many developers shouldn't be allowed out of bed in the morning and I have met operations support engineers who could do anything if they wanted to.
In fact the blog posting that this is all the fault of the Agile methodology or Startups is as naive as his views on chefs i.e. a head chef tends to create dishes for the other chefs under him to cook for the clientele.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!