►
From YouTube: 4. DevOps Roll Out Strategy
Description
Interview with an IT Agility Director
Question: What was your DevOps roll out strategy? Were there specific use cases or capabilities on which you chose to focus?
A
So
the
strategy
that
that
we
used
to
launch
our
DevOps
program
we
did
initially
you
know
we
use
the
consulting
company
to
come
in
and
help
us
do
an
analysis
on
where
we
were
at.
So
we
started
looking
at
sort
of
some
larger
DevOps
capabilities.
So
if
you
think
automated
deployments
automated
code
scanning
automated,
you
know
provisioning
of
infrastructure.
A
So
we
did
an
assessment
on
where
we
were
at
and
an
assessment
on
where
the
value
was
for
Duke
Energy,
and
that
assessment
went
on
for
probably
three
or
four
months
and
it
helped
us
lay
out
a
where
we
thought
the
most
value
was,
and
it
did
affect
the
way
that
we
ended
up.
Spinning
up
the
teams,
at
least
the
orders
that
we
spun
up
the
teams.
So
we
we
put
a
focus
on
a
couple
of
things.
Initially,
one
of
those
was
source
code
management,
consolidation
being
a
utility
company.
A
Duke
have
lots
of,
they
have
lots
of
mergers
over
the
years
and
one
of
the
things
that
was
never
consolidated
with
source
code
management
systems.
So
when
we
started
this,
we
had
13.
So
the
very
first
initiative
we
kicked
off
was:
how
do
we
do
a
consolidation
you
know
down
to
and
we
ended
up
going
down
to
two
actually
and
because
the
route,
one
of
main
reasons
we
want
to
do
that
first,
was
in
a
source
code
management
system?
A
Is
the
entry
point
into
your
DevOps
tool
chain
and
what
we
didn't
want
to
have
to
do
was
integrate
13
different
source
code
management
systems
into
our
tool
chain.
So
you
know
just
for
ease
of
use.
We
wanted
to
make
sure
that
was
first,
that
we
were
tackling
integration
only
to
two
source
code
management
systems
as
the
13.
The
second
thing
we
focused
on
was
was
really
infrastructure
provisioning.
How
do
we,
you
know,
look
at
how
quickly
we
can
spin
up
images
for
our
application
teams
and
then
that
managed
the
configuration
of
those.
A
So
that
was
one
of
the
the
second
team
we
ended
up.
Spinning
up
was
to
was
to
tackle
that,
and
then
we
then,
after
that
we
began
focusing
on
some
of
the
other
problems
that
came
in
automated
testing
was
one
that
came
up
real,
quick,
stinking
spun
up.
We
didn't
really
have
a
solution
in
place
for
automated
testing,
so
we
had
to
go
through
and
vet
and
then
stand
up
some
tools
for
that,
so
that,
as
we
went
through,
we
we
did
have
to
pivot
a
little.
A
You
know
if
you've
worked
with
any
consulting
companies
that
what
the
answer
they
give
you
doesn't
exactly
turn
out
to
be
100%
correct.
So
we
took
the
plan
that
we
laid
out
there
and
then
we
pivoted,
as
we
realized
new
areas
of
value
that
were
coming
in
or
things
that
were
higher
than
maybe
we
initially
thought,
and
then
we
did
get
into
some
work
where
it
got
ranked
a
little
bit
higher,
maybe
than
it
should
have
been.
So
we
ended
up
having
to
move
that
work
to
later
on.