►
From YouTube: Manage:Analytics Categories and Direction
Description
Jeremy Watson (https://about.gitlab.com/company/team/#jeremy) shares his thoughts on the direction for Analytics in GitLab.
Previous video referenced at 0:11: https://www.youtube.com/watch?v=g3RGch5m454
A
Hey
I'm
Jimmy
once
and
I'm
a
product
manager,
gurgle
AB
I'm
here
today,
to
talk
a
little
bit
about
our
direction
strategy
when
it
comes
to
analytics
and
our
product,
as
always,
feedback
is
welcome.
I
recently
created
a
video
on
analytics
where
I
did
a
brief
whiteboarding
session
I
received
some
questions
and
wanted
to
share
some
more
thoughts
about
what
this
means
for
our
strategy
and
especially
what
this
means
for
our
categories
for
the
analytics
group
of
the
manage
stage
so
without
further
ado
share.
A
A
There
is
some
output
of
our
SDLC
that
is
resulting
in
something
that
is
valuable
and
I.
Think
that's
the
way
that
I'd
like
for
us
to
think
about
this.
We've
refactored
one
of
our
categories
into
what
we
call
value
stream
management
to
kind
of
represent
that
in
the
end
journey
and
I'd
like
to
see
this
reflected
exclusively
in
our
product.
We
are
currently
planning
and
working
on
renaming
cycle
analytics,
which
currently
does
this,
but
we
want
to
go
deeper.
Well
actually,
like
have
a
analytics
feature.
A
That's
reflective
of
the
full
value
stream
across
the
entire
product.
I
have
that
tie
back
to
specific
features
like
in
the
gitlab
application
and
have
this
at
the
project
group
and
instance,
level.
At
the
moment
cycle
analytics
we
have
a
version
that
is
at
the
project
level.
We
have
a
more
premium
version
of
cycle
analytics
at
the
group
level,
but
ultimately
we
want
to
represent
this
value
stream
management
and
the
DevOps
lifecycle,
it's
very
explicitly
in
the
product.
A
So
I
think
there's
an
opportunity
for
us
to
deep
dive
and
every
single
one
of
these
stages
at
the
project
group
and
instance,
level,
and
we
already
have
some
features
and
capabilities
in
each
of
these
areas,
but
I
think
that
I
would
like
to
concede
us
expand
on
them
and
so
that
we
have
explicit
features
and
capabilities
for
every
single
stage
that
tie
back
to
our
overall
value
stream.
And
what
I
mean
is
you
know
for
plan?
For
instance
I'd
like
to
introduce
a
category?
That's
explicitly
called
planning
analytics
and
again.
A
We
already
have
some
of
this,
where
we
have
currently
you'll
see
some
features
that
are
in
italics,
which
are
which
link
to
issues
that
are
currently
planned,
but
things
that
are
not
in
italics.
We
already
have
like
group
level
issue
analytics,
which
is
a
current
feature
that
is
relatively
minimal
at
the
moment,
but
it
tells
use
of
information
about
how
many
issues
are
being
created
at
the
group
level,
we'd
like
to
introduce,
as
the
product
level
eventually
we'd
like
to
introduce,
like
instance,
level
kind
of
planning
analytics
to
help.
A
You
better
understand
predictability
in
planning,
at
kind
of
the
instance
in
portfolio
level,
so
I
think
that
that
a
aligns
really
nicely
with
our
buyer
model,
where
we
have
you
know
primarily
core
and
starter
features.
It's
kind
of
the
project
level
we
have.
You
know
group
and
instance,
levels
instance,
level
features
that
apply
to
larger
enterprises
kind
of
in
in
in
higher
tiers,
but
it
also
really
aligns
well
with
Lycan
of
the
information
architecture
for
our
application,
where
we
have
series
of
features.
A
That'll
sit
at
the
project
group
instance
level,
so
I
think
planning
analytics
is
something
I'm
really
excited
about.
I
would
consider
this
category
minimal
at
the
moment,
but
I
think
that
you
know
we'd
like
to
go
deeper
into
planning
analytics.
So
this
is
something
our
customers
are
really
excited
about.
I
think
the
next
category
is
right
around
code
analytics-
and
you
know
we
introduced
a
feature
in
our
last
release:
12.7
around
project
level,
code
review
analytics
to
take
the
create
kind
of
phase
of
your
development
lifecycle
and
then
double
click
into
it.
A
It
also
kind
of
helps
you
find
merge,
requests
that
are
that
need
unblocking
so
again
like
connecting
back
to
the
value
stream
that
we
have
at
the
that.
We
would
like
to
create
at
the
project
group
an
instance
level
in
this
kind
of
end-to-end
flow.
We
want
to
be
able
to
double-click
and
to
create
theater
understand
like
how
your
developers
are
pushing
code
which
merge
requests
in
code
review
and
our
stalled
and
code
review
at
the
project
group,
an
instance
level.
A
I
think
you
want
to
do
more
than
that
and
show
more
advanced
quality
metrics
where
you
can
see
like
how
your
code
quality
is
changing
over
time,
which
pipelines
are
and
jobs
are
taking
a
really
long
time
to
run
again
of
how
that's
changing
over
time.
Again,
you
want
to
show
that
at
the
project
group
at
instance,
level,
so
you
can
get
insights
into
kind
of
like
how
your
CI
CD
is
going
to
working
across
your
organization,
so
that
leaves
a
gap
in
the
ops
section
and
I.
A
A
Development
lifecycle
are
are
are
adding
to
your
deployed
applications,
but
in
the
meanwhile
there's
a
lot
we
can
do
that's
more
fundamental,
like
just
showing
the
value
of
what
gitlab
itself,
via
your
value
stream,
is
delivering
to
your
organization
with
things
like
an
instance
level
overview
like
s
like
an
assessment
of
like
individual
project.
Health
in
terms
of
you
know
a
better
DevOps
score
to
be
able
to
understand
at
the
instance
level,
a
what's
the
value
that
gitlab
is
actually
delivering
for
your
organization
and
then
B.
A
What
is
the
value
that
your
software
development
process
is
actually
adding
to
your
applications
that
are
so
fundamental
to
your
business?
So
that's
kind
of
my
thoughts.
That
means
so
at
the
moment.
Those
are
the
five
categories
that
I'm
kind
of
proposing
and
at
the
moments
like
the
areas
that
were
most
interested
in
focusing
on
our
around
value
stream
management
just
showing
and
that
value
end-to-end
value
stream
in
the
application
and
again
I
want
to
have
my
vision
is
to
have
you
know,
analytics
features
if
you
could
double
click
into
it.
A
Every
single
stage,
that'll
roll
back
up
to
V
it
to
value
stream
management.
So
TSM
shows
you
the
high
level
of
how
you're
delivering
value
throughout
your
with
your
sdlc
and
then
you're
able
to
have
these
deep
dive
analytics
features
like
code
review,
analytics
and
others
that
kind
of
help
you
better
understand
bottlenecks
and
concise
and
specific
stages
across
the
organization.
So
that's
kind
of
my
thoughts,
that's
where
we're
going
really
excited
to
to
continue
to
iterate
on
this.
With
your
help,
thanks
for
the
time
Cheers.