7. To make an error is human… To
propagate an error to all servers in an
automatic way is DevOps!
8. DevOps is a partnership between Development
and Operations that emphasizes
communication, collaboration and integration
Call it a culture, a movement
or a philosophy…
It’s not a framework, product or
technology!
9.
10.
11.
12.
13.
14. Myth #1
There is no direct
customer/business value for
adopting DevOps practices.
15. Myth #2
There is no significant return on
investment in applying DevOps
principles to legacy apps.
21. How ITIL, DevOps and Agile relate
Service
Strategy
Service
Design
Service
Transition
CSI
Service
Operation
Application Development
(Agile)
Application Management (Through the lifecycle)
Service Operation (Operational support activities)
DevOps
34. Pressure to deliver regular/frequent update to
apps vs maintaining stable high availability
service.
DevOps adds value by encouraging improved
levels of communication, collaboration and
accountability between development and
operations.
35. Development and Operations teams often report
to different senior managers within organization.
Secondary thought given to how other parts will
support. “The Service Desk will take care of that.”
DevOps adds value by helping overcome
organizational barriers between development and
operations teams.
36. Value is a product of functionality as well as
performance. It’s not only the what it does, but the
how as well. Operations need to ensure the whole
service is delivering value.
DevOps adds value by assuring a uniform
understanding of ‘value’ across IT service
functions. When used with ITIL it combines timely
development of new functionality and ongoing
performance.
37. Development groups are often focused on time-
bound activities to produce new functionality. Not
too concerned with the day to day operation of the
functionality.
DevOps adds value by ensuring early
participation of operations teams in design and
development activities. Service Design gets early
involvement from ops teams.