An important question from Impact 2014 - Is deployment automation the same thing as DevOps?
This week at Impact has been full of thought-provoking sessions and interactions with folks from IBM and attendees from companies around the world. The Expo floor was full of attendees asking about DevOps, and many folks specifically around the Rele
This misconception has come up more and more lately, as DevOps has grown in popularity, and as many companies come out with deployment automation tools that are marketed as "DevOps tools." It's easy to see how the moniker "DevOps tool" could confuse people into thinking that purchasing that tool alone would equate to "doing DevOps." And doing DevOps is just that, it's something to be implemented, and done, not something that can be bought.
While that is true, it still doesn't define what each is and why they are two separate things. DevOps is a means of continuously delivering value by obtaining customer feedback and responding rapidly. DevOps is traditionally achieved through automation solutions, a general shift in culture that encourages development and Operations to work together for a common goal (customer satisfaction), and a change in process for agility across the entirety (stress, entirety) of the application lifecycle. IBM DevOps breaks down this concept into four main entry points or adoption paths that include tooling; Plan & Measure, Develop & Test, Release & Deploy and Monitor & Optimize. Addressing each of these entry points for the right blend of solutions, along with fostering a responsive and collaborative culture and continuously improving processes enables IBM customers to achieve DevOps. And within the Release & Deploy entry point is where we find depl
For more information on deployment automation, download your free copy of Appl