►
From YouTube: Value stream analytics - Pipeline Authoring
Description
https://gitlab.com/groups/gitlab-org/-/analytics/value_stream_analytics?created_after=2022-02-24&created_before=2022-03-25&value_stream_id=1284&label_name[]=group%3A%3Apipeline%20authoring
A
Okay,
I
want
to
caveat
this
heavily
with.
I
have
no
idea
what
I'm
doing,
but
I
thought
it
was
pretty
cool.
I
saw
this
this
feature
years
ago
and
it
was
in
his
infancy,
but
like
this
is
kind
of
useful.
Now
there
was
a
comment
from
from
nadia
in
in
one
of
the
the
retros.
I
can't
remember
what
it
said
to
be
honest,
but
it
was
around
how
long
do
we
spend
doing
something,
and
it
got
me
thinking.
A
A
Design
plan
breakdown,
ready
for
development
in
devon
in
review
and
all
it
does
is
checks
all
our
issues,
for
you
know
how
long
were
they
in
design
and
I'm
defining
that
based
on
when
the
design
label
was
added
and
the
design
label
was
removed.
So
it's
the
amount
of
time
between
these
two
things
same
for
planning
breakdown,
ready
for
development
in
dev
and
in
review,
all
sorts
of
other
things
you
can
do,
but
I'm
starting
here
I'm
starting
small
because
there's
a
lot
of
confusing
data
here.
A
To
be
honest,
there's
all
these
things
about
tasks
and
stuff.
I
don't
know
what
that
is,
so
I'm
going
to
skip
over
that
lead
time
cycle
time
whatever.
A
So,
if
you
go
into
actually
in
dev,
is
a
good
one
to
look
at
for
us
big
spike
here,
where
the
average
time
for
completion
is
328
issue
less
days,
and
we
can
see
there.
It
is.
I
think
we
all
expected
this
one
to
be.
The
outlier
retrain
failed
I'll
cancel
job,
so
this
has
been
in
dev
for
almost
a
year
which,
which
is
rough,
but
it's
good
that
this
points
this
out
right.
A
I
don't
know
oh
okay,
right
yeah,
so
the
other
downside
to
to
this
is
because
in
this
case
we
got
some
levels
wrong
and
and
quickly
changed
them.
A
So
as
far
as
value
stream
analytics
are
concerned,
this
only
spent
one
minute
in
in
development,
because
it's
the
time
between
us,
adding
and
removing
the
label,
but
whatever
it
gives
us
kind
of
a
bit
of
a
view
in
what's
potentially
problematic
and
roughly
how
long
we're
spending
in
these
things-
and
this
seems
about
right
to
me-
it's
it's
taking
the
median
which
is
helpful
for
these
outliers.
A
We
have
a
week
in
design
19
hours
in
planning
breakdown,
which
is
pretty
good
three
weeks
in
ready
for
development
yeah.
I'm
not
sure
how
useful
this
one
is
because
there's
some
issues
that
can
sit
and
ready
for
development
for
a
long
time
until
they
get
prioritized
in
dev
about
a
week
and
in
review
about
a
week.
These
all
sound
about
right,
but
yeah
I'll,
send
you
the
link.
I
have
a
play
about,
and
let
me
know
if
there's
there's
anything
useful
in
here.
A
A
A
Mr
was
closed,
created
the
first
commit
first
deployed
to
production,
there's
all
sorts
of
stuff
in
here
and
then
you
can
go
through
and
add
them
in,
and
it
just
creates
a
new
stage
up
here,
which
is
pretty
nice
again,
not
sure
what
this
overview
is.
I
would
like
insight
into
why
this
spike
is
here.
Can
I
actually
let
me
do
that?
A
I
just
I
don't
know
what
this
is.
Whatever
these
ones
are
cool,
though,
to
then
you
know,
you've
got
a
timeline
of
whatever.
If
we
go
back
to
a
little
start
of
the
year,
we
can
see
roughly
how
well
we're
doing
again,
there's
big
spikes
january
28th.
Don't
know
why
that
is.
I
don't
know
if
this
will
update
to
no,
it
will
won't
tell
me
but
yeah,
it's
still
kind
of
in
this
infancy,
but
pretty
cool.