►
From YouTube: 6. DevOps Program Challenges and Lessons Learned
Description
Interview with an IT Agility Director
Question: What were some of the challenges and lessons learned you experienced with your DevOps program?
A
A
You
know
I
think
if
you're,
if
you're
talking
about
a
developer,
especially
when
you
have
a
you-
know
disparate
set
of
tools,
you're
having
to
teach
them
how
to
use
a
handful
of
tools
and
that's
not
trivial
people
generally,
don't
like
change
anyway,
so
you
don't
want
to
make
the
change
more
complicated
than
it
has
to
be
so
when
you're
on
boarding
teams
and
you're
in
you're,
taking
them
to
to
a
place
where
they
have
to
learn
this
source
code
management
tool,
you
need
to
learn
these
scanning
tools.
This
is
your
continuous
integration
tool.
A
This
is
your
automated
deployment
tool,
it
becomes
overwhelming
to
them,
and
it
it
becomes
difficult
to
break
that
down
into
smaller
chunks.
I
think
part
of
the
issue
that
we
had
in
teaching
people
how
to
fish
was
just
getting
over
that
initial
inertia
and
fear
of
having
to
learn
all
the
new
stuff,
and
it
is
complex.
It's
it's
one
of
those
things
that,
when
you're
going
through
automating
a
pipeline,
the
end
result
is
fantastic
right,
I
can
commit
code
and
it's
going
to
end
up
being
deployed
and
I.
Don't
do
anything
else.
A
Don't
underestimate
how
much
effort
it
takes
to
get
from
point
A
to
point
Z.
There
there's
a
lot
of
effort
to
actually
build
that
the
first
time.
Another
thing
that
that
we
learned
that
we
ended
up
having
to
pivot
on
was
just
how
you
how
you
set
up
your
teams.
If
you're
on
the
you're
running
a
DevOps
program,
we
initially
set
up
our
teams
a
lot
by
capability,
so
we
would
have
testing
capabilities.
Would
be
this
team
infrastructure
to
be
this
team.
A
We've
determined
that
it
was
that
made
very
difficult
when
you
own
board
teams,
because
you
didn't
want
to
say
okay,
go
to
this
team
work
on
the
infrastructure,
then
go
to
this
other
DevOps
team.
The
help
with
testing
and
this
other
DevOps
team
will
help
with
your
CI
CD
challenges.
It's
just
too
many
handoffs
in
it
and
it
gets
complex
and
you
lose.
A
You
know
you
lose
a
little
momentum
with
those
teams,
so
we
ended
up
dividing
the
teams
up
more
into
a
customer
success
model
where
there
was
one
team
that
just
constantly
worked
with
the
application
teams.
They
were
focused
on
the
onboarding
throughout
the
entire
tool
chain
and
providing
support
to
them
when
they
had
issues
and
then
our
other
DevOps
team
was
more
focused
on
continuous
improvement,
maintaining
the
tool
chain
introducing
new
capabilities
and
features
to
the
to
the
to
the
tool
chain.
A
I
think
that
was
a
lesson
learned
and
then,
if
I
were
to
add,
maybe
a
third
thing
here.
It's
be
really
cognizant
of
who
you
put
on
the
teams,
in
other
words,
be
very,
very
picky.
You
know
you
want
a
certain
set
of
schools,
skill
sets
on
those
teams.
You
hear
the
term
full
stack
developer.
You
need
plenty
of
full
stack
developers
here,
so
you
need
to
make
sure
you
have
people
who
can
work
with
the
customer
teams.