►
From YouTube: 2. DevOps Project Goals
Description
Interview with an IT Agility Director
Question: What were the goals of your organization's DevOps program?
A
Well,
the
two
largest
goals
that
we
had
when
we
launched
the
DevOps
program
were
reducing
the
time
to
market
time
to
markets,
not
always
the
best
for
utilities
company,
because
we're
not
racing
necessarily
but
just
reduced
the
time
of
code
development
to
deployment
to
production.
We
have
a
lot
of
our
main
applications
that
we
do
releases
quarterly.
A
So
if
you
look
at
our
end,
users,
they're
only
getting
new
features,
maybe
four
times
a
year,
so
it
was
a
definitely
a
large
initiative
to
figure
out
how
do
we
get?
How
do
we
put
more
features
or
fixes
into
production
environments
more
frequent
than
quarterly?
And
this
this
also
paired
with
there
was
an
agile
initiative
that
went
along
with
DevOps,
so
we
were
focusing
on
the
way
the
company
works.
You
know
how
do
we
just
more
rapidly
get
changes?
A
How
do
we
break
them
down
into
smaller
chunks
so
that
we
can
get
them
out
faster
and
that
there's
a
you
know
less
likelihood
of
being
in
an
event
when
we
do
a
deployment
you
know
being
when
you
do
deployments
and
frequently
they
become
so
large
that
the
risk
of
those
goes
way
up.
So
that
was
the
first
thing.
The
second
one
was
really
figuring
out
how
to
reduce
manual
effort
pretty
much
everything
that
we
did
there
SDLC
was
manual
code,
builds
code,
deploys
testing,
you
name
it.
A
Everything
was
a
manual
process
is
just
so
much
effort
spent
doing
that
and,
as
part
of
the
reason,
we
could
only
release
that
frequently,
but
the
second
you
just
allow
for
a
lot
of
human
error
in
that
process,
and
it
takes
a
lot
of
people
and
a
lot
of
time
to
do
anything.
So
the
cost
perspective
on
this
was
how
can
we
become
more
efficient
by
completely
automating
the
tasks,
especially
the
repetitive
tasks?
The
things
you
do
like
is
it
code
builds
deployments.
Those
are
things
you're
doing
multiple
times
a
day
on
a
project.
A
A
They
say
this
was
an
initial
focus
only
kicked
off
the
program,
but
it
became
pretty
obvious
if
you
looked
at
patterns
and
what
was
going
on
kind
of
globally
there
that
part
of
the
overall
one
of
the
core
tenets
of
a
DevOps
project
or
program
in
general
is
to
shift
left.
We
want
to
be
able
to
find
you
know
bugs
a
little
earlier
in
the
process
so
that
it
needed
to
include
security.