►
From YouTube: End to End Visibility and Insights
Description
Learning Objectives:
How does GitLab provide "End to End Insight and Visibility" to customers and what is the value they can derive out of it?
What is Value stream management and our immediate roadmap?
Presentation: https://docs.google.com/presentation/d/1gGJP3cil0MNi2hMzJSXc-5MDLGuult2KncmuziEJ76w/edit#slide=id.p
Notes Document:
https://docs.google.com/document/d/1mn-29S_pIVbvekvzTouiFYs5WzxtQbguS4F9cooLf4I/edit?usp=sharing
A
All
right
team-
it's
12
noon
here
in
atlanta,
so
time
to
get
started.
I
wanted
to
make
a
really
quick
announcement
for
everyone
before
we
actually
jump
into
the
session
regarding
cobin,
19
and
tracking
impact
to
the
business.
So
I
want
everyone
to
take
a
look
at
this
handbook
page.
I
have
dropped
it
in
the
notes
document
under
action
items
here
at
the
bottom.
A
So
I'm
sure,
if
you
have
questions
on
this,
many
people
do
talk
to
your
manager
or
slack
sales
support,
but
we
just
wanted
to
make
this
quick
update.
We
put
this
out
in
a
couple
different
places
back
to
the
sales
enablement
session.
We
have
our
friendly
remote
marketing
experts
to
talk
about
end-to-end,
insights
and
visibility.
B
I
hope
you
can
see
this,
so
I'm
part
of
the
today
we're
going
to
cover
two
topics.
Actually
one
is
the
end
to
end
in
sight
and
visibility,
which
is
identified
as
one
of
the
defensible
differentiators
as
a
part
of
the
command
of
the
message
and
value
framework.
So
so
we
we're
going
to
dig
a
little
bit
deep
into
this
particular
differentiator
and
talk
about
what
it
really
means.
B
What
are
the
various
analytics
reports
and
dashboards
that
we
do
have
in
our
product
and
what
they
actually
value
they
give
to
the
customer,
and
we
so
I
also
have
cardmak
with
me
from
the
pmm
team
who's
going
to
cover,
then
a
roadmap
from
a
value
stream
management.
Point
of
view,
which
kind
of
goes
well
with
this
with
this
whole
topic,
because
value
stream
management
is
one
of
the
reports
that
we
talk
about
as
a
part
of
end-to-end
insight
and
visibility.
B
Okay,
so
we've
kind
of
classified
the
dashboards
reports,
essentially
all
the
insights
that
we
have
into
five
key
categories.
So
the
first
is
executive
insights.
It
basically
gives
insights
at
an
org
level
to
make
decisions
at
based
on
you
know.
The
devops
maturity
or
to
identify
bottlenecks
in
the
devops
processes
as
well,
so
we
there
are
four
reports
that
we've
identified
we'll
dig
down
into
that.
B
The
next
is
the
productivity
insights,
which
give
insights
more
at
a
team
level
in
terms
of
how
well
the
team
is
performing
at
a
group
and
a
project
level.
The
next
is
the
developer
insight
which,
which
gives
more
insights
into
how
in
each
individual
developer
or
account.
What's
what
is
the
contribution
from
a
developer
or
a
qa
person
to
the
overall
process?
Then
we
have
the
the
last
two
are
the
operations
insight
which
talk
about?
B
You
know
how
we're
doing
from
from
from
a
ci
cd
pipeline
point
of
view.
How
are
our
environments
doing
so?
We
have
some
dashboards
or
that
cover
that
and
then
at
the
last
is
the
security
insights
and
we
have
a
couple
of
reports
that
cover
that
so
I'll
dig
deep
into
each
one
of
these
for
a
bit,
but
as
you
can
see,
with
more
insight
and
visibility,
you
know
it
kind
of
aligns
with
the
outcomes
that
customers
are
expecting
from
us,
which
we've
defined
as
a
part
of
the
value
framework
itself.
B
So
the
increased
visibility
helps
customers
make
decisions
that
lead
to
faster
cycle
times.
It
also
helps
to
identify
bottlenecks
in
the
processes
and
therefore
solve
the
bottlenecks,
much
quicker
and
also
identify
security
issues
as
we
as
as
they
go
forward
with
their
processes
right.
So
it
very
well
aligns
with
the
value
framework.
This
particular
differentiator
gives
benefits
in
each
of
these
pillars
of
the
value
framework
as
well.
B
So
let's
dig
a
little
bit
deep
into
the
executive
insights,
so
here
we
have
about
four
reports.
The
first
is
the
devops
course.
So
essentially,
it
helps
a
customer
to
answer
the
question
of
how
are
we
doing
across
the
various
stages
of
the
devops
life
cycle,
as
well
as
how
are
we
doing
across
other
companies
who
are
actually
using
gitlab
itself
right?
So
this
is
based
on
some
data
that
we
collect
usage
ping
data
that
we
collect
from
customers.
B
We
are
able
to
identify
how
each
organization
is
is
performing
compared
to
another
organization.
Of
course,
it's
based
on
the
permissions
that
they
do
give
to
gitlab
to
kind
of
share
this
anonymized
information
as
well.
So
that's
so.
This
helps
to
determine
if
there
are
improvements
needed
or
if
there
are
additional
stages
that
we
need
to
start
adopting,
which
we
are
not
already
adopting
as
an
organization.
B
So
it
is
based
on
the
customers
kpis
that
they
can
actually
start
tracking.
You
know
the
performance
of
a
particular
stage,
so
it
helps
to
identify
any
bottlenecks
that
they
have
in
specific
stages
that
they
have
identified
and
also
how
long
it
takes
from
ideation
to
production.
Basically,
the
cycle
time
as
well.
B
B
The
next
is
the
roadmap,
so
this
helps
customers
identify
to
answer
the
question
if
they
are
building
the
right
thing
at
the
right
time.
So
here
we
are
able
to
map
it
to
specific
epics
and
as
a
part
of
the
roadmap
there
is.
There
is
a
plan
to
I
to
add
milestones.
There
is
a
plan
to
expand
the
ethics
as
a
part
of
the
roadmap
itself,
so
there
are
some
in
investment
that
is
actually
being
done
on
the
roadmap
visibility
as
well
as
we
go
forward.
B
So
next
category
is
the
product
productivity
insight,
and
this
helps
to
identify
insights
which
determine
the
productivity
at
a
group
or
a
project
level
productivity
of
the
team
at
a
group
or
a
project
level.
We
have
a
few
dashboards
over
here
as
well.
So
the
first
is
the
issue
analytics,
which
actually
is
at
a
group
level
which
which
talks
about
how
many
issues
are
created.
You
can
filter
it
by
the
by
specific
releases
by
author
and
so
on.
B
So
this
is
at
a
holistic
level,
at
a
group
level,
very
much
abstracted
information
in
terms
of
how
many
issues
are
created.
How
many
are
closed,
milestones,
release
and
filter
it
by
author
as
well,
and
the
next
is
when
you
want
to
when
a
customer
would
want
to
drill
down
into
that.
So
customers
obviously
use
labels
to
identify
to
to
track
specific
kpis
that
they
have,
it
could
be
the
it
could
be
bugs
it
could
be
strata,
strategic
investment
themes
and
so
on.
B
So
this
group
or
project
insights
actually
helps
to
track
issues
based
on
the
metrics
track,
based
on
the
labels
that
they
have
already
identified.
So
you
can
identify
how
many
have
missed
deadlines.
You
know
how
many,
how
many
have
had
regressions,
how
many
are
created
and
closed
and
so
on
as
well,
and
this
is
only
available
to
an
ultimate.
B
I
have
a
slide
towards
the
end,
which
summarizes
which
of
these
dashboards
are
in
startup
premium
and
ultimate.
So
that's
why
I'm
not
going
into
that
in
each
of
these
slides.
The
next
is
the
productivity
analytics,
so
this
so
the
first
two
dashboards
that
we
spoke
about
are
specifically
from
an
issue
point
of
view:
you're
tracking
it
by
from
an
issue
perspective,
the
productivity
analytics
tax
tracks,
the
metrics
from
a
merged
request,
point
of
view
right.
So
how
much?
How
much
time
is
it
taking
to
merge?
B
B
And
then
the
last
one
in
this
category
is
the
code
review
analytics
which
helps
to
identify
if
there
are
long-standing
merge
requests
that
have
not
been
removed
so
that
have
not
been
reviewed.
So
this
would
impact
the
cycle
time
and
that's
the
reason
why
this
report
is
there
to
identify
long-standing
requests
so
that
it
can
be
cleared
at
the
earliest
as
well.
B
The
next
category
is
developer
insights,
so
here
we
have
contribution
analytics
and
contributors
which
is
in
the
next
slide.
So
at
a
group
level
we
track
something
called
the
contribution
analytics
which
helps
the
customer
answer,
the
question
of
who
are
the
top
contributors
at
a
group
level.
So
you
can
also
see
the
total
number.
A
B
B
The
next
report
is
contribution,
charts
or
repository
analytics.
This
talks
about
you
know
what
is
the
preferred
language,
programming
language
that
the
developers
have
and
it
tracks
the
lines
of
codes
or
comments
that
have
been
made
based
on
the
language
and
to
help
determine
in
a
particular
repository
which
is
the
language
that's
being
used,
and
then
the
the
last
one
in
this
category
is
the
code
code
quality
report.
B
The
next
category
is
operations
insight.
So
this
gives
us
details
about
this.
You
know
the
environments,
the
ci
cd
performance
of
the
projects
and
so
on.
So
the
first
is
the
operations
dashboard
so
yeah.
This
is
a
customizable
dashboard
which
so
a
customer
can
select
specific
projects
that
they
want
to
track
and
that
and
as
as
a
part
of
this
dashboard,
you
know
they
get
a
snapshot
of
alerts.
You
know
the
pipelines
last
deployment,
the
pipeline
status
and
so
on.
B
So
essentially
it
helps
a
customer
to
track
the
health
of
various
projects
that
they
are
interested
in
in
a
single
dashboard
itself
and
then
the
environments
dashboard.
So
from
the
previous
slide,
this
the
the
selected
projects
would
also
come
on
the
environments
dashboard.
So
if
there
are
xyz
projects
selected
there,
the
environments
dashboards
will
also
show
the
environments
for
those
selected
projects
as
well,
and
here
you
could
have
staging
environments,
pre-production
production,
environments
or
list.
I
think
per
project.
B
We
show
a
maximum
of
three
environments
and
for
each
of
those
environments,
you
know
the
status
of
the
environment,
the
last
deployment-
or
you
can
see
the
review
apps
when
and
so
on,
is
actually
shown
in
the
environment
tab
and
then,
if,
if,
if
an
operator
wants
to
drill
down
further
into
a
specific
environment,
it
comes
into
the
environment.
Dashboard
itself,
which
shows
more
details
in
terms
of
the
environments
of
you
know
how
what
percentage
of
the
deployment
is
complete?
B
The
last
category
is
security
insights,
and
we
have
about
five
reports
here.
So
the
project
security
dashboard
summarizes
the
information
from
four
different
types
of
tests.
That's
a
static,
dynamic
test,
dependency
scanning
and
container
scanning.
So
from
all
of
these
four
tests,
it
brings
brings
forth
the
results
based
on
the
severity,
so
the
critical,
high,
medium
and
low
severity
results
are
are
shown,
so
it
helps
a
customer
to
determine
from
from
at
a
high
level.
B
What
is
this,
how
secure
secure
is
the
application
and
this
all
the
security
dashboards
are
only
part
of
the
ultimate,
and
then
there
is
the
compliance
dashboard
so
for
a
customer
can
actually
set
compliance
rules
in
terms
of
who
are
the
approvers
for
specific,
merge
requests
and
so
on.
So
the
compliance
dashboard
actually
gives
a
trail
of
audit
trail
of
that
which
shows
which
you
know,
which
mr
was
was
actually
merged.
Who
were
the
approvers
for
those,
mrs
and
so
on?
B
So
it
gives
a
track
of
what
kind
of
gating
has
gone
into
before.
The
mr
is
actually
merged
into
the
master.
Master
branch,
then,
is
the
license
compliance,
so
customers
can
define
policies,
and
then
this
particular
report
shows
the
compliance
to
those
policies
and
if
there
are
any
deviations
from
those
policies,
dependency
lists.
So
obviously
a
lot
of
customers
use
open
source
software
which
are
actually
also
dependent
on
other
other
software.
B
Well
and
then
we
have
the
last
report,
which
was
released
as
a
part
of
12.9
which
helps
to
determine
if
there
is
a
threat
exposure
or
to
the
application
itself,
so
it
it
kind
of
tracks
the
total
traffic
to
the
application,
as
well
as
the
block
traffic,
and
if
the
block
percentage
of
block
traffic
is
is
kind
of
high.
It
implies
that
there
is
a
higher
threat
exposure.
So
this
is
an
mdc
which
was
just
released
in
the
last
release.
B
So
to
summarize,
there
are
tons
of
reports
so
far
and
every
release
there
are,
you
know,
improvements
or
additions
made
to
this
list,
so
we
will
continue
to
maintain
this
tech.
It
is
available
as
a
part
of
the
in
the
sales
report.
Sales
resources
handbook
page
right
here,
so
you
can
actually
go
and
look
at
it
at
any
point
in
time,
but
this
particular
table
shows
you
or
the
list
of
dashboards
and
reports
that
we
have
as
well
as
as
well
as
which
tier
it
actually
falls
under.