[dreamfactory2]

hmm I've worked with some of the people who invented the term and this is a bit off. devops is bringing dev practises into ops as you describe - e.g. replacing ad-hoc bespoke shell scripts with more standardised automation frameworks leading to full infrastructure-as-code phoenix-pattern deployments. It is also breaking the dev and ops wall in the same way that agile is intended to break the bus/dev wall. An example of this would be continuous deployment and automated testing (e.g. the kind of things that IMVU did with automated performance testing on commit to live with rollback if problems started to appear as changes cascaded through the infrastructure). and like agile it is meant to describe a mindset rather than a role or department. and also like agile, it is horribly bent out of shape by most orgs and comes to mean different things to many people...