Uniting Development and Operations Teams
Playing the DevOps variant of the Kanban simulation game, the question that invariably surfaces is, "Why should we do any of these Ops maintenance tickets? They cost us time and money and they don't generate revenue."
This is central to the problem - Operations is (or is seen) as a cost center. Companies are often slanted toward new projects (instead of much needed maintenance work) because new projects can be written off as capital expenditures.
The DevOps movement is shifting the focus away from separate departments working independently to an organization-wide collaboration — a “systems thinking” approach. It’s about addressing all the work as a whole, versus looking only at the bits and pieces, or only looking at capital versus expense. It’s about work flowing across functions (versus lurking in silos) and delivering the right thing quickly.
Cutter IT Article
Cutter IT Journal, Devops: A Software Revolution in the Making?
This link is to the complete Cutter IT Journal issue, published Aug 2011 and requires filling out a form. My piece (the 5th of five contributing authors) can be downloaded below (no info required).
With Ops on the receiving end of faster and more frequent deliveries from development teams, the pressure to keep up necessitates faster and more efficient practices. The inefficiencies of the past clearly no longer suffice.
The realization that the world of building, deploying, and maintaining environments can benefit significantly from using a new approach has caught on rapidly.
Adobe Acrobat Document [685.6 KB]