- [Instructor] Enter devops where the barriers
between dev and ops are lowered
along a number of dimensions,
including objectives and responsibilities
across dev and ops in the whole lifecycle
and functional and nonfunctional service requirements
along with values and principles,
methods and practices,
culture and mindsets,
incentives and rewards,
knowledge and tools,
and environments and visibility.
In devops, dev and ops share the same core objective,
fast time to value with quality and continuous improvement
and they share it across the entire lifecycle
from strategy to design to transition
to operation and continual improvement.
Instead of them versus us, it's just us.
Lastly, in a devops shop,
releases tend to be more digital in nature
and smaller and more frequent
and the level of automation is higher.
This is due in part to the devops culture of striving
for more frequent releases and to automate everything,
but also because digitization lowers the transaction cost
of moving forward or rolling back releases
making devops possible.
That's why some people say devops and the cloud
are tied at the hip.
So what's enterprise devops?
First of all, it's devops.
Dev and ops with one single objective
and responsibilities across the entire lifecycle,
faster time to value with quality
and continuous improvement,
with lower barriers between dev and ops,
so they share many of the same
objectives and responsibilities,
values and principles, and so on.
So enterprise devops is devops,
but a special flavor of devops
as it is practiced in an enterprise IT environment
which is categorized by two key elements.
The first of these is the presence
of enterprise IT challenges
including enterprise-level change and release gates,
legacy regulated and non-automated environments,
disparate siloed teams with different objectives,
mindsets, knowledge and tools, and massive scale.
That's the first.
The second is the presence of ITIL-driven practices.
This blog post on plutora.com said it best I think.
You can think of enterprise devops as
devops when your IT department is still focused
on ITSM and ITIL.
I'd add that it's also when your target environment
is a hybrid of traditional and cloud mobile platforms.
So enterprise devops is devops applied
to a hybrid environment,
moving from physical legacy environments towards the cloud.
So it's characterized by relatively more digital
and smaller and more frequent releases
and a higher level of automation
than traditional IT shops on the cloud side,
but relatively more physical, larger,
and less frequent releases
and levels of automation on the legacy side.
So it's still devops,
but enterprise devops has two very important differences
from cloud native devops,
the presence of ITIL-driven practices
and enterprise challenges
including a hybrid target environment.
So enterprise devops is the intersection of devops
and enterprise IT shops with ITIL-driven practices
and enterprise challenges.
Given the nature of the typical enterprise IT environment,
enterprise devops cannot equal devops.
You could think of enterprise devops
as devops where you do what you can
to adapt devops values, principles, methods and practices
for ITIL-driven practices and enterprise challenges
and adapt ITIL-driven practices
and factoring enterprise challenges for devops success.
I think it's important to consider one more subject
before we get on examining how to make these adaptations
and that is what do devops and enterprise IT have in common
and how do they differ?