|
|
 |
|
Viewing report
|
|
|
|
DevOps
Ovum, Oct 2010, Pages: 26
Introduction
It is early days for the DevOps movement. Its nature, scope, and ambitions are still in flux. Some of its ideas are old (for example, Ops-Devs collaboration), while others are leading edge (such as cloud-based API-centric Ops). Enterprises and vendors alike should start paying attention to both types of ideas, as we expect the DevOps movement to slowly gain momentum.
Features and benefits
- The report provides an overview of the various facets of the DevOps movement and puts these facets in context.- The report enables enterprises to figure out how and to what extent DevOps relates to their own IT development and operations activities.
Highlights
The DevOps movement acknowledges that the relationship between Dev and Ops teams is usually rather dysfunctional. It provides a space where Ops and an increasing number of Devs can provide ideas on how to repair the relationship.While IBM and Microsoft talk about Dev and Ops collaboration in generic terms and believe that such a collaboration has time to build up, the DevOps message is different in terms of focus (it is largely cloud computing centric) and urgency (it emphasizes the need to start at once).The DevOps debate talks about the convergence between Devs and Ops from various angles. One of the most important emphasizes the need for production systems (both physical and virtual) to be designed in the context of the infrastructure that underpins them and the Ops tools that manage them.
Your key questions answered
- What is the DevOps movement about? what are its strengths and weaknesses?- What are the chances of success for the DevOps movement, and why?- How does DevOps relate to ALM, Agile development, ITSM, and ITIL?
|
|
|
|
