• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (1)

1 Damon Edwards commented Permalink

Hi Ivor,

Glad to see you (and other IBM folks) talking about DevOps!
You ask why it took this long for IT to figure out that a wall between "build" and "do" is fundamentally a bad idea. For the answer I think you have to look no further than who the people are that started the DevOps movement.
The bulk of the early DevOps community was from small web 2.0 startups (or web 2.0 style carve-out businesses within large enterprises). For them, IT was no longer a cost center that supports the "real" business, IT IS the business. Getting an idea from someone's head to where it is making you money in a customer facing environment (i.e. production) is their factory floor.
Anything that gets in the way of that "idea -> prod" process is waste and makes you less competitive. That early group looked at the current tooling and practices that were born out of the old IT model and found them to be unsuitable for the new "IT as factory floor" world. Hence, when Patrick Debois put together the first DevOps Days conference, it was a lightening rod and the DevOps movement was born. A movement of practitioners organized by practitioners (not analysts or vendors).
If you are interested in the business case behind why DevOps matters, I've written about it in more detail here:
If you are interested in why DevOps is needed in an increasingly cloudy world, you might like this presentation:
You and your IBM colleagues should really consider attending the DevOps Days conferences, it's where the DevOps movement was founded and they continue to be ground zero for the movement:
-Damon Edwards

Add a Comment Add a Comment