►
From YouTube: Manage:Analytics Weekly Meeting 2020-05-12
Description
The Analytics group talks about blockers, "on deck" issues, and cool stuff from the past week.
A
Seems
like
we
have
to
agenda
items
for
today.
For
some
reason,
I
guess
the
one
I
created
earlier
was
just
a
copy
and
paste
from
the
template.
So
let's
use
the
one
that
on
top
of
our
template,
so
I
guess
besides
the
issues
that
are
just
fyis
dan
has
the
first
agenda
item
for
today.
B
I
can
unmute
myself,
so
some
of
you
may
have
noticed
a
friendly
new
face
in
in
our
little
gallery
here
on
the
zoom
call.
This
is
magda,
so
she
is
joining
us
as
a
backend
engineer
moving
over
from
the
spaces
team.
So
you
know,
I
think
we
already
announced
that
on
slack,
but
I
want
to
give
magda
just
an
opportunity
to
to
say,
hi
and
tell
us
a
little
bit
about
herself.
C
Thank
you,
then
hi
hi
all
nice,
to
meet
you
and
yeah.
With
some
of
you.
We
already
met
in
the
chat
and
then
I
also
schedule
calls
with
others.
So
I'm
looking
forward
to
talk
in
person
but
yeah,
I
I'm
joining.
I
guess
like
this
week.
It
will
be
my
first
week,
I'm
actually
ready
to
take
an
issue
on
I've,
been
with
gitlab
since
october
2019
and
has
done
that
I'm
moving
from
spaces
now
previously
before
gitlab.
C
I
was
working
with
consultancy
company
for
like
three
years
and
before
that
for
two
product
companies.
But
my
background
is
in
psychology
and
countries,
so
I
changed
careers
and
that
was
in
like
2014.
C
B
Thanks
magda,
we're
really
excited
to
have
you,
and
I
think
next
is
walking
through
blockers.
A
Welcome
welcome,
magda,
by
the
way,
thanks
for
the
nice
introduction,
looking
forward
to
working
with
you,
I
think
if
you
don't
have
any
blockers,
then
let's
move
to
the
on
deck
issues.
D
So
we've
got
as
before:
two
sections:
a
candidate
issues
section
and
a
selected
issue
section
and,
and
then
I've
I've
got
objectives
and
and
success
for
13
1.
D
The
goal
for
13.1
again
is
just
get
as
far
as
we
can
on
stuff
related
to
the
generics
metrics
api
and
and
the
report
page
that
we've
been
working
on
and
we've
made
some
good
progress
in
in
terms
of
breaking
this.
Generic
analytics
drill
in
page
issue
down
into
a
place
to
start,
and
we
we've
decided
to
start
with
the
recent
activity.
D
Charts
and
new
members,
I
think,
is
what
we
said
would
be
the
first
of
the
set,
and
we
have
talked
about
kind
of
some
specific
issues.
D
Regarding
the
scoping
this,
where
we
will
start
section
captures
some
of
the
agreements
that
we
had
in
conversations
yesterday
about
where
we'll
start
with
that,
which
basically
is
going
to
be
a
single
page,
where
we'll
display
the
chart
for
the
new
member
data
and
the
only
thing
and
and
that
there
will
be
some
kind
of
url
that
identifies
that
that
data
definition
that
tells
us
how
to
get
the
data
and
renders
the
chart
so
that,
once
that
first
page
is
finished
in
order
to
add
the
same
label,
the
same
level
of
capabilities
for
mr
or
issues.
D
The
other
things
that
we're
looking
at
is
tracking
the
amount
of
time
an
issue
is
spent
with
a
particular
label
and
some
instrumentation
for
the
north
star
metric.
D
This
northstar
metrics
instrumentation
is
an
okr
for
this
quarter
for
all
of
the
product
teams
to
have
some
new
instrumentation
for
those
north
star
metrics,
and
you
can
read
more
about
that
there
and
then
we're
also
taking
some
great
steps
forward
in
the
that
inbox
analytics
is
the
new
name.
D
I've
given
to
that
use
that
epic
used
to
be
called
like
embedded
analytics
or
error
embedded
to
do
pages
and
personal
pages,
or
something
like
that
inbox
analytics
is
actually
a
better
description
for
what
we're
trying
to
do
there
and
there's
a
set
of
issues
that
we've
already
scoped
down
and-
and
I
think
some
of
them
we
may
even
have
started
on
and
then
we'll
be
doing
more
research
on
two
news
with
inbox
analytics
and
then
also
contribution
analytics,
adding
the
approvals
column
and
then
adding
filters
to
vsa.
D
B
Sean
mason
two
questions
for
you,
so
I
think
that
on
contribution
analytics,
we
might
have
a
couple
of
blockers.
I
guess
this
isn't
a
question,
so
we
may
want
to
add
those
to
this
list
and
in
which
case
we
may
need
to
bump
actually
adding
the
approvals
column
to
13
two.
I
guess
that
would
be
if
we're
handling
the
blockers
in
thirteen
one.
My
actual
question
is:
do
we
have
a
a
planning
call
scheduled
for
this
week
for
the
final
plan.
D
D
D
D
Night,
I
I
mean
a
good
follow-on
question
we
can
take
offline
for,
for
you,
and
dan
is
how?
How
can
we
pick
a
time
for
this?
That's
you
know
fair
to
both
of
you.
I
always
struggle
with
with
scheduling
those
so.
B
D
D
I've
already
created
a
planning
issue
for
3-2,
but
there's
nothing
much
in
there.
Yet
the
way
that
I'm
thinking
that
this
is
going
to
play
out
is
we'll
make
our
first
mvc
of
this
report.
Object
page
see
how
far
we
can
get
with
it
and
then
three
two
get
it
to
the
point
where
it's
becoming
more
useful
and
we
can
start
leveraging
it
from
from
other
places
and
then
by
three
two.
D
We
should
be
ready
to
to
take
off
the
next
bigger
chunk
of
the
to
do
or
the
inbox
analytics
piece
and
we'll
also
start
scoping
some
stuff
related
to
inbox
analytics
for
for
sort
of
the
mr
inbox,
which
is
a
big
part
of
the
feedback
that
we've
had
so
far,
as
is
tracking
mrs
and
then,
after
that,
the
next
thing
that
we're
likely
to
be
starting
to
scope
on
in
three
two
and
three
three
starting
to
take
chipping
a
chip
away
at
it
are
things
related
to
helping
with
the
planning
and
tracking.
D
Agile
project
managers
will
not
use
it,
they'll
still
wind
up
doing
things
in
in
jira
and
and
that's
just
because
they
don't
have
the
kind
of
analytics
that
they
need
to
support
the
their
planning
exercises
so
that
that's
sort
of
the
next
big
piece
we'll
be
taking
a
look
at
while
we're
also
refining
kind
of
our
vision
for
where
we
want
to
go
with
the
vsa.
D
In
order
to
make
kind
of
where
we're
going
a
lot
more
clear
than
it
is
today
I'll,
be
working
on
updates
to
direction
pages
and
categories
this
week
and
reviewing
with
jeremy.
D
We've
had
a
series
of
these
collaboration
meetings
with
gabe's
team.
The
next
one
will
be
coming
up
and
the
agenda
is
for
that
there,
if
you're
interested
in
that.
So
with
that
I'll
I'll
hand
it
over
to
brandon,
unless
there
are
any
questions
for
me.
E
Cool
no,
so
I'm
gonna
share
my
screen.
Just
a
super
quick
demo
on
the
update
for
value
stream,
analytics
path
component.
E
So
if
we
were
to
select
one
top
on
the
vertical
navigation
that
will
be
updated
as
well,
the
same
feature
select
here
on
the
vertical
navigation.
The
horizontal
path
navigation
will
be
updated.
I
don't
have
a
lot
of
data
on
my
local
dev
environment,
so
a
lot
of
these
aren't
completely
updated,
and
this
is
also
behind
the
feature
flag
which
can
be
turned
on
and
off
last
thing
is
probably
just
to
show
that
it
is
responsive
and
that
slides
nicely
from
start
through
to
the
end.
A
F
And
the
mobile
responsiveness
works
works
really
well
as
well.
You
smash
that
mate
so,
based
on
the
on
the
new
region
design,
we
may
need
to
move
the
the
path
outside
of
the
gray
bit.
Is
that
relatively
easy
to
do.
E
A
F
Oh
god,
I'm
sorry
yeah,
like
based
on
based
on
the
recent
work
I've
done
on
the
filter
region.
Basically
we're
gonna
have
to
move
that
path
out.
So
I
can.
I
can
create
an
issue
for
that.
E
Cool
no
problem,
I
can
do
it
as
part
of
this
merge
quest
as
well.
If
it's
just
moving
it
up
shouldn't
be
much
finishing,
we
should
still
be
on
schedule
for
13.0.
F
So
I
assume
it's
may
now
I'll
share
my
screen.
A
Just
sorry,
just
one
quick
question
regarding
the
path
component,
so
what
we
saw
now
was
having
both
navigation
elements
being
activated.
At
the
same
time,
ideally,
we
will
just.
We
will
toggle
it
with
the
feature
flag
right,
so
my
understanding
is
that
we
will
most
likely
only
have
one
of
the
two
elements
being
active
right.
E
So,
with
the
initial
release,
there's
no
customization
options
for
like
dragging
for
editing
stages,
and
things
like
that
when
you
just
have
the
horizontal
navigation.
So
we
still
need
that
vertical
navigation.
Just
that
you
can
still
have
all
of
those
controls,
but
with
a
feature
flag.
You
can
basically
just
toggle
if
you
want
and
I'll
see
the
new
one
as
well
right.
A
Right
and
then
later
on,
once
we
have
drag
and
drop
support
for
the
for
the
horizontal
path
component.
We
should
be
able
to
just
turn
on
one
of
the
two
components
right
and
deactivate
the
other
one.
E
Yeah,
that's
from
my
understanding
the
approach
we're
going
to
be
taking
as
well.
F
F
This
right
here
is
basically
the
abstraction
or
generalization
of
that,
and
I've
started
to
document
how
the
how
the
report
object
would
look
and
then
I'm
also
gonna
in
the
in
the
process
of
creating
a
number
of
examples
of
that,
because
I'm
working
on
the
the
general,
the
sorry
my
head's,
all
screwed
around
here
the
group,
the
group
overview
metric
pages.
F
So
this
is
this
is
a
little
bit
of
what
I've
I've
designed
right
now,
and
it
would
be
great
for
for
anyone
to
give
me
their
feedback
on
the
documentation
to
sort
of
just
understand
from
a
high
level
how
this
works.
Basically,
the
documentation
is
broken
down
into
just
an
overview.
F
F
Creating
a
custom
report
and
and
structuring
structuring
stuff
in
this
way
will
allow
us
to
generalize
a
lot
more
and
allow
us
to
get
multiple
designers
to
focus
on
a
single
object
and
and
focus
on
improving
an
object
which
could
apply
to
the
entirety
of
gitlab,
rather
than
focusing
on
a
component
which
isn't
really
a
component
because
they're
not
put
into
the
design
system
in
different
parts
of
the
product.
So
this
is
hopefully
going
to
help
to
standardize
ways
of
approaching
stuff.
So
yeah.
F
If
you
can,
if
you
can
provide
some
feedback
on
there.
That
would
be
great
and
I
did
a
little
sketch
video
as
well
in
the
thingy
underneath
and
if
you
have
eight
minutes
and
30
seconds,
feel
free
to
to
look
at
that
video.
F
That's
basically
describing
a
like
the
john
mason,
and
I
we
had
a
bit
of
a
discussion
the
other
day
around
how
our
navigation
in
analytics
could
work
and
what
are
the
sort
of
steps
that
we
want
to
take
in
order
to
get
to
a
big
sort
of
open
home
page
of
of
analytics
reports,
dashboards,
all
this
sort
of
stuff.
So
this
is
just
a
condensed
video
of
our
conversation
of
me
explaining
sort
of
the
rationale
behind
what
we're
doing
and
why
and
why
objects
are
a
useful
part
of
that.
D
Know
if
there
are
no
questions
for
nick?
The
last
item
was
mine,
I'll
pause
to
make
sure
that
anybody
has
questions
for
nick
you've
got
time.
But
after
that
I
wanted
to
ask
how
we
can
make
this
meeting
better.
B
I
have
a
question
on
that
count,
so
we
haven't
been
walking
the
board
just
because
you
know
we
were
kind
of
thinking
that
you
know
the
labels
indicate
the
issue
status
and
that
kind
of
thing
does
anybody
feel
like.
Maybe
we
should
keep
walking
the
board.
I
mean
like
that,
was
an
experiment
to
stop
doing
that.
Has
anybody
not
liked
the
experiment.
B
Okay,
I
mean
feel
free
to
change
your
mind
in
the
future,
but
you
know
it
was
just
something
I
was
curious
about
like
should
we
should
we
be
walking
what's
currently
on
the
board
versus
just
assuming
it's
taken
care
of
in
commons.
A
I
guess,
instead
of
walking
the
board
what
we
added
instead
was
the
agenda
item
about
potential
blockers
right,
so
we
figured
it
might
be
more
useful
instead
of
walking
through
or
going
to
an
entire
board.
You
just
pick
particular
blockers
that
we
can
talk
about
so
so
far.
We
didn't
have
any
blockers
to
talk
about,
but
I
like
it
better
personally,
but
if
we
feel
we
need
to
walk
the
board,
I'm
I'm
I'm
open
for.
E
That
I,
like
the
new
approach-
to
be
honest-
I
just
forgot
the
other
day
or
what
we
were
supposed
to
do
on
an
issue
that
we
thought
might
slip.
So
I
just
had
to
go
back
a
little
bit
in
the
history
of
the
agenda
to
see
that
we
need
to
use
the
health
status.
So
maybe
just
a
good
reminder
about
the
health
status
attributes
on
issues.
If
you
think
that
might
slip.
A
So
should
we
do
that,
is
that
something
we
should
consider
adding
to
every
agenda,
or
is
it
more
useful
to
only
discuss
health
status
on
issues
once
a
month
like
before?
We
do
the
release
planning
for
the
next
milestone.
B
I
think
that's
a
good
idea,
so
I
guess
that
would
be
like
in
this
meeting,
because
I
don't
think
we
can
filter
for
health
status,
which
is
the
big
drawback
with
it.
So
maybe
we
can
just
use
the
meeting
right
before
the
final
planning
is
a
call
out
for
that
of
like
please
list
anything.
That's
that
has
a
health
status
of
at
risk.
B
E
E
E
D
Are
the
things
someone
beat
me
I've
struggled
with
this?
It
seems
like
often
in
in
my
past
experience
with
different
teams
oftentimes.
I
found
that
issues
that
don't
make
it
that
the
problem
often
happens
early
in
the
iteration
rather
than
late,
something
that
it
just
hasn't
gained
enough
momentum
until
too
late
in
the
iteration
to
get
over
the
line,
and
I
don't-
I
can't
figure
out
a
very
good
way
of
seeing
issues
that
I
would
expect
to
be
moving.
That
aren't,
in
other
words,
issues
with
no
activity
that
are
planned
for
the
release.
A
You
mean
to
identify
issues
that
haven't
had
any
movement
since
the
beginning
of
the
milestone.
I
guess
it's
that's
I
think.
Well.
A
Part
of
the
problem
is
probably,
if
you're,
if
a
developer,
starts
to
work
on
one
particular
issue
and
doesn't
get
blocked
on
that
issue,
but
it
just
needs
time
to
wrap
something
up.
Then
in
most
cases
he
wouldn't
start
on
a
new
issue
until
he
finishes
the
first
one
or
until
he
realizes
okay
at
this
point
in
time,
I'm
being
blocked.
So
I
can
pick
up
something
else
and
I
believe
in
this
particular
issue,
brenton
spent
most
of
the
time
working
on
the
past
component.
A
So
I
guess
what
the
only
thing
that
we
could
do
is
I'm
not
sure
if
we
can
use
the
updated,
add
status
to
identify
those
issues
but
updated
ad
will
only
change.
Would
that
also
change?
If
you,
if
you
add
a
comment
to
the
issue
or
if
you
change
the
status,
so
I
wonder
when
is
updated,
ad
being
changed
to
a
new
date.
E
Updated
at
will
update,
if
you
add
a
comment
to
the
issue.
A
Okay,
so
in
that
case,
since
you've
been
quite
active
on
the
issue,
it
wouldn't
have
helped
us
in
that
case
right
because
we
decided
to
split
it
and
then
you
looked
into
the
issue.
You
provided
some
feedback,
so
there
was
still
some
activity
on
the
issue,
but
work
hasn't
like
completed
or
hasn't
started.
So
I
wonder
if
that
would
be
like
a
helpful
metric
in
this
regard.
D
No,
I
probably
wouldn't
have
solved
that
issue
and
I
I'm
not
really.
I
wasn't
really
concerned
about
that
specific
one,
but
I
just
in
general,
that's
something
that
in
the
past
I've
tried
to
watch
is
you
know
every
24
48
hours
look
at
everything
and
see
which
ones
are
moving
and
which
ones
aren't,
and
I
just
I've
not
found
a
very
good
way
of
doing
that.
D
A
Guess
that
at
least
that
would
help
us
to
identify
issues
that
maybe
we
we
have
not
on
our
radar
or
somebody
like
missed
looking
at
those
issues.
That
would
definitely
help
us,
but
with
issues
that
where
there
is
still
activity
there
were
there's
still
people
commenting
on
the
issue
or
already
creating
mrs
for
it.
I
think
those
issues
would
still
slip,
but
I
guess
it
it
would.
A
It
could
still
help
us
to
identify
issues
that
are
maybe
not
assigned
to
developers
or
haven't
been
commented
on
or
updated
in
a
couple
of
days.
A
A
I
guess
it
would
still
help
us
to
like
keep
track
of
issues
that
have
like
a
high
potential
of
slipping,
and
then
we
can
make
sure
that
we
re
prioritize
them
for
the
next
milestone.
B
D
I
like
that,
I
just
updated
the
template
up
at
the
top.
A
Okay,
any
anything
else,
any
additional
bonus,
content
nope
all
right,
then
thanks
everyone
and
you
a
good
rest
of
your
day,
talk
soon.