►
From YouTube: Manage:Analytics Weekly 2020-07-07
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
A
C
C
B
A
C
A
A
And
here
I
was
trying
to
be
already
cool,
so
adding
filter
results,
control
on
the
group,
value
stream,
analytics
that's
in
verification
in
production
and
I
guess
I
think
the
zekiel
was
leading
the
charge
on
verification
by
Adam.
Do
you
know
where
verification
stands
right
now
because
he
kills
in
here.
B
B
A
There
may
have
been
a
weird
problem
with
what's
what's
populating
into
the
autosuggest
like
when
I
was
testing
it
for
for
the
managed
project
it
looked
like
only
group
owners
or
project
owners.
I
should
say
we're
appearing
in
the
list
of
like
potential
authors,
for
example.
So
I
don't
know
if
there's
a
bug
there
or
if
it
was
just
weird
behavior
in
that
specific
project,
so
I
wanted
to
give
a
zekiel
a
chance
to
respond
to
that,
and
then
maybe
we
can
enable
it
forget
lab
org.
If
that
sounds
like
hey
everybody,
okay,.
B
A
D
Coming
along
hi,
do
you
actually
have
another
issue
specifically
for
the
front
end
with
a
workflow
label,
is
updated
to
in
development,
not
sure
if
it's
perhaps
not
popping
up
here,
because
it
doesn't
have
a
priority
label
label
assigned
I'm.
Sorry,
oh
it's
worth,
oh
well,
all
taking
that
off
to
the
call
but
I'm
busy
on
the
first
API
integration
call.
D
A
E
I
think
so
so
I
already
contributed
a
little
bit
too
to
the
backend
as
well.
That's
mainly
what
the
focus!
The
work
has
focused
on
right
now
and
I'm
slowly,
just
connecting
the
dots
to
add
in
the
JavaScript
that
we
need
in
there
for
the
embedded
page
as
soon
as
I
have
something
displaying
on
there.
We
can
actually
try
it
out
and
try
to
embed
it
in
and
see
how
well
that
works,
but
yeah
I've
split
it
up
into
subtasks.
E
A
I
was
just
gonna,
bring
that
up.
Actually,
so
normally
development
should
be
complete
by
the
18th
day
of
the
month.
So
that's
the
end
of
next
week.
So
my
question,
you
is
gonna,
be
do
you
do
you
feel,
like
you
know,
roughly
speaking,
you
feel
like.
We
have
good
odds
of
getting
in
the
last
piece
of
this
work,
all
the
way
through
code
review
and
merged
by
the
end
of
next
week,.
E
That
seems
a
little
too
like
too
much
of
a
stretch,
because
I
know
I'm
gonna
be
out
for
next
week
and
a
half
starting
starting
next
Monday.
Are
they
this
coming
Monday
so
I
mean
anybody.
It's
hopefully
made
in
such
a
way
and
described
so
explicit
explicitly
that
anybody
else
could
jump
in
and
contribute
on
that,
but
I
do
assume
that,
for
example,
both
Brandon
and
Ezekiel
I
would
expect
would
be
the
ones
picking
up
are
located
or
allocated
elsewhere.
So
I
guess
it's
a
little
bit
a
question
about
a
priority
at
this
point.
A
E
Yeah
yeah,
that's
that's
kind
of
the
the
conclusion
of
it.
I
think
it's!
It
would
be
a
strike
to
get
it
in
there
I'm
trying
to
get
as
much
done
during
this
week
as
possible.
I
would
say
that
I'm,
probably
not
at
my
most
productive,
because
I'm
still
learning
the
ropes
a
little
bit
so
so
I
do
run
into
some
hurdles
every
once
in
a
while,
so
not
quite
at
the
velocity
that
I
would
like
to
be
at
yet.
But
I
guess,
that's
just
the
nature
of
me
starting
sure.
A
E
Actually
update
that
one,
because
it
literally
just
merged
the
the
issue
that
was
blocking
that
I
implemented
a
general
loader
for
the
chart,
which
is
blocking
further
development
on
this,
though,
this
is
a
low
priority,
because
the
feature
is
in
it's
working
as
we
wanted
to
it's
just
a
nicer
experience
to
have,
like
a
nice
chart
motor
to
load
the
individual
charts
by
themselves.
So
it's
really
a
small
change.
I.
A
And
over
here
this
next
issue,
switching
between
value
streams
and
value
stream
analytics.
So
this
is
actually
a
13-3
issue,
but
it
seems
like
maybe
it
got
pulled
into
13-2.
For
the
estimation,
I
see
the
estimations
completed
and
I,
don't
know
how
much
more
stuff
like
that
we
have
here
so
I
know
we
can
ignore
this
issue.
A
C
C
We're
all
done
and
Ezekiel
worked
on
these
last
night,
so
I
just
need
to
get
an
update,
need
to
look
look
at
those,
but
I
think
the
estimates
came
in
on
those
two,
so
we're
doing
pretty
good,
so
this
is
sort
of
the
rank
order
of
what
we
have
planned,
and
these
these
two
estimates,
I
think
came
in
this
one
column.
Chart
supports
multiple
series.
C
C
The
other
thing
that
we
did
was
make
a
new
board
to
help
us
with
planning,
and
this
one
we
can
see
which
items
we
have
in
estimation
needed,
and
then
we
can
now
see
can
about
the
number
of
stories
and
points
for
the
back
end
on
the
front
and
as
far
as
the
plan
there
so
we'll
be
we'll
have
our
final
planning
meeting
tomorrow
morning
to
figure
out
where
we
are
for
thirteen
three.
So
thanks
a
lot
everyone
for
all
the
hard
work
you
put
into
the
estimation.
C
So
that's
been
great
as
far
as
other
updates,
I
have
updated
or
I've
got.
An
M
are
open
to
update
the
direction
page
for
vice
tree
management
and
I,
reworked
the
the
hierarchy
of
evaluate
stream
management
issues,
so
you'll
see
I'll
ping.
The
channel
when
that
gets
merged-
hopefully
today
or
tomorrow
and
and
I'll,
also
have
a
video
that
goes
through
the
direction
changes
as
well.
So
look
for
that
on
the
channel.
That's
all
I've
got.
D
Cool
next
point
is
mine,
just
not
exactly
sure
how
great
it
more
useful.
It's
going
to
be
discussed
in
the
small
Nick's,
not
on
the
call
so
probably
and
I
created
an
issue
to
discuss
this
I.
Think
I
just
wanted
to
get
a
bit
of
everybody's
thoughts
on
our
current
UX
approval
process,
which
works
pretty
well
when
we
work
on
larger
features
where
they
are
go
through.
The
old
pajamas
system
get
implemented
in
figma
and
then
implemented
in
gitlab
UI
with
prior.
D
You
explore
for
like
a
high-level
UX
department,
but
we
don't
really
follow
that
same
process
when
it
comes
to
smaller
changes
all
the
time.
A
recent
example
is
the
little
back
button.
If
we
were
going
to
add
to
the
report
page
something
that
seemed
super
super
simple
and
didn't
really
expect
any
pushback
on
that.
I
ended
up
spending
like
a
decent
amount
of
engineering.
D
Time
on
that
and
when
it
was
in
maintainer
of
you,
ended
up
getting
quite
a
lot
of
pushback
and
had
to
actually
close
the
merge
request,
which
I
was
just
a
little
bit
of
waste
of
time,
which
could
potentially
you
know,
be
avoided.
If
we
have
a
little
bit
more
flour
like
UX
approval
before
we
actually
start
on
front-end
work,
no
I,
don't
know
anyone
has
any
thoughts
on
that
or
what
just
creates
an
issue
to
discuss
that
alone.
C
D
D
E
Talk
a
little
bit
about
so
I
was
quite
stuck
on
some
r-spec
development
and
not
being
super
familiar
with.
That
I
can
really
recommend,
there's
a
course
on
Pluralsight
all
at
the
link
into
the
document,
and
that
definitely
helped
me
very
quickly
ramble
and
wrap
my
head
around
how
certain
structures
actually
work
and
bonus.