►
From YouTube: Testing PM/UX Weekly - 2021-03-16
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).
A
This
morning,
all
right,
so,
let's
jump
into
the
follow-up
issues
I
needed
to
update
the
code
quality,
mr
diff,
with
the
finalized
designs,
this
actual
inline,
where
we
paint
the
mr
diff,
which
I
did,
I
added
a
link
to
the
sigma
design
as
well
hi
on
it.
It
looks
like
you
added
a
link
to
the
design
issue.
Just
so
everything
is
all
linked
together
on
the
on
the
gitlab
side,
which
is
great.
A
B
Yeah
I
was
a
bit
confused
because
we
have,
I
think,
three
issues
that
are
on
the
same
team
and
I'll.
When
I
looked
at
it
at
the
this
one
that
you
linked,
I
was
okay,
which
one
is
the
source
of
truth,
because
we
have
the
implementation
of
the
nbc
and
we
have
another
one
and
the
design
issue.
So
I
was
I
wanted
to
ask
you
what
you
normally
do
is.
B
A
What
I've
been
doing,
let
me
just
I'm
going
to
share
my
screen.
What
I've
been
doing
is
what
I
did
where
in
the
proposal
which
I
didn't
do
here.
I
will.
A
This
is
the
right
one:
yeah,
oh
yeah,
in
the
further
details,
or
in
the
proposal
I'll
say
acceptance,
criteria
can
be
seen
here
around
the
the
design,
here's
a
link
to
the
prototype,
and
then
the
designs
are
included
below
to
try
to
dog
food
as
much
as
we
can
and
say,
this
is
the
design
that
is
the
single
source
of
truth.
A
B
Mm-Hmm
that
sounds
good.
That
clarifies
it.
I
think,
that's
my
confusion
was
what
you
were
considering
the
source
of
truth
there,
because
in
my
acceptance
criteria
talk
about
like
spacing
sizes-
and
I
think
in
these
cases
where
there
is
a
yeah,
some
specific
changes
for
front
end.
It's
good
to
refer
to
what
we
write
in
the
issue
and
not
the
mockups,
because
I
honestly
don't
do
pixel
perfect
prototypes.
B
So
if
we
can
yeah
continue
doing
that,
pulling
the
information
in
to
the
source
of
truth
for
the
implement
for
the
implementation
item.
That
would
be
great.
So
that
clarifies
my
question
thanks.
A
So
I
added
that
as
an
action
item
for
myself
all
right,
the
other
follow-up
was,
I
did,
do
a
horrible
sketch,
which
started
as
a
sketch
from
my
ipad
and
turned
into.
I
just
changed
it
all
with
preview
and
text
and
boxes,
which
is
all
I
really
wanted
to
do
anyway.
A
For
that
code
call
or
that
quality
dashboard,
mvc
yeah,
it's
not
good
where
it
would
live.
I
think
it's
yeah
it's
under
analytics.
If
it's
at
the
project
level
it'll
probably
be
analytics,
and
I
think
we
should
talk
about
a
new
subheading
there
of
quality
and
we
can
say
analytics
quality.
We
can
pull
test
coverage
into
that.
This
can
live
there,
as
maybe
that
first
click
and
it
would
give
you
kind
of
this-
is
your
overview
of
quality.
A
As
we
see
it,
and
eventually
it
can
morph
into
something
that's
closer
to
that
design,
vision,
design,
design,
vision,
mission,
design,
design,
vision
that
juan
and
I
put
together
that
has
all
the
different
tabs
on
it.
Where
you
can
then
drill
into
the
reports
from
there.
That
would
be
our
kind
of
top
level
and
we'll
probably
want
to
simplify
that.
So
it's
not
so
so
much
going
on
and
it's
just
you
can
start
to
drill
down
into
different
signals,
but
you
have
a
very
clear
one
at
the
top
of
this
is
the
current
state.
B
A
The
initial
the
initial
version
of
this,
I
think,
would
be
at
the
project
level,
so
it'll
still
be
an
ultimate
feature
and
then
we
can
level
up
from
there
and
say
we're
also
going
to
implement
this
at
the
group
level
as
an
ultimate
feature.
B
A
A
So
we
have
this
test
coverage
number
for
the
current
yeah.
We
we
have
the
historical
because
that's
what
we
track
and
then
this
this
click
to
see
full
report
would
take
you
into
that
test
coverage
report.
The
tests
run.
We
don't,
I
believe,
have
historical
data
for
it,
but
we
could
start
with
the
pin.
A
But
I
think
that
we
can
even
start
without
the
historical
and
say
here's
what
quality
looks
like
for
your
project.
We
can
really
take
an
iterative
approach
to
this
and
start
with
just
three
numbers
and
you
might
have
historical
data
for
the
test
coverage
and
then
we'll
build
out
the
historical
data
for
the
rest,
and
I
think
it'd
be
an
interesting
experiment
for
us
to
have
that
click
for
details,
and
it
takes
you
into
not
a
great
page
or
even
just
here's,
the
for
like
the
code
quality.
A
B
Sounds
good
and
when
you,
when
you
display
these
metrics,
are
they
because
I
know
that
your
prototype
is
very
low
level
infidelity,
but
is
this
like
last
24
hours,
less
30
days,
less
deployment?
What
are
we
seeing
on
this?
On
this
view?.
A
This
would
be
the
latest
before
you
do
default
branch,
so
if
you're
working
off
of
main
last
time
pipeline
ran
for
main,
this
is
the
test
coverage.
This
is
how
many
like
the
test
execution
for
it,
and
this
is
the
code
quality
for
it.
A
So
we
assume
that-
and
this
would
be
contingent
on
a
user
having
a
pipeline
that
is
generating
that
data,
so
we
may
need
to
include
instruction
or
something
about
you
know
you
can
schedule
a
pipeline
that
does
this,
even
if
it's
not
part
of
a
deployment,
because
you
don't
want
to
wait
for
this
for
a
deployment,
but
you
can
do
it
after
the
deployment.
There's
some
other
nuance
around
that
of
what
the
last
pipeline
is
that
ran,
but.
A
B
That's
good
for
me
because
also
when
I
think
about
an
empty
state,
you
need
to
yeah
understand
what
we
want
users
to
do
from
there.
If
they
don't
have
anything
like
this,
it's
set
up.
Here's!
Here's!
How
do
you
get
started
with
the
setting
up
all
your.
A
Yeah,
and
we
can-
I
mean
that
would
be
really
interesting.
I
gave
you
just
completely
a
happy
path
that
this
data
exists.
There's
historical
data.
Everything
is
built,
but
as
we
iterate
into
that,
and
what,
if
you
don't
run
the
code
quality
job?
Well,
here's
how
we
can
include
the
link
to
the
documentation
of
how
to
set
it
up
or
something.
B
Helping
users
always,
I
think,
it's
interesting
to
always
connect
them
through
the
flow.
That's
one
of
the
issues
right
now
with
the
whole
product
as
a
whole
is
that
yeah,
the
the
workflows,
are
pilot
in
some
areas
of
the
product.
So
that's
a
good
call
out
coolio
and
heads
up.
I
think,
if
you,
you
know,
if
you're
into
prototyping,
you
should
get
a
figma
or
a
balsamic
access
request.
We
have
the
tools
and
we
have
other
pms
using
and
you
can.
B
A
Although
I'm
sure
it's
changed
enough,
that
big
mo
would
be,
I
would
be
just
as
used
to
that
as
I
would,
with
the
song.
B
A
B
Used
to
do
it
in
in
a
google
doc
for
me
table
and
then
here's
a
here's.
B
B
Yeah,
I
don't
have
an
idea
because,
since
we
talked
about
my
transition,
I'm
like
okay
do.
I
need
to
prioritize
this
now
how
I
want
to
allocate
my
time,
let's
see.
A
A
A
The
I
need
to
talk
with
ricky
and
see
where
we're
at
with.
I
know
scots,
I'm
going
to
be
doing
some
work
for
runner
that
would
slow
down
our
need
for
front-end
design,
but
then,
depending
on
the
plus
10
percent
investment,
we
may
get
some
back-end
investment
sooner
than
later.
A
So
having
some
things
that
miranda
quickly
miranda
and
scott
in
his
capacity
could
quickly
work
on
that
might
push
up
some
of
the
stuff
that
we
just
looked
at,
because
that
would
be
the
next
highest
priority
for
us
is
that
code,
quality,
dashboard.
B
Yeah
and
it's
a
much
larger
ux
effort,
as
in
we're
going
to
need,
of
course,
as
long
as
we
don't
really
have
all
the
back,
the
data
in
the
back
end
to
to
pull
and
show
any.
Why,
then,
the
design
itself,
it's
quite
simple,
but
yeah?
We
just
have
to
see
how
we're
going
to
prioritize
that
in
the
menu
in
the
navigation,
how
we're
displaying
these
users
or
components
we're
using.
B
So
my
experience
working
with
analytics
and
working
with
this
type
of
dashboards
in
our
product,
it's
the
profits
it
gets
lower
when
we
have
to
align
with
other
people.
It's
not
necessarily
putting
a
proposal
out
there,
just
so
a
heads
up
to
you,
but
yeah,
that's
life.
B
B
No,
this
is
a
shorter
week,
so
I'm
I'm
powering
through
these
issues.
We
have
friends,
family
and
friends
this
friday
yeah.
For
me.
A
I'm
shifting
mine
to
next
friday
to
match
up
with
my
daughter's
day
off
school.
So
if
you
need
anything
I'll
have
a
good
chunk
of
time
on
friday,
then
I
can
power
through
stuff
cool.
Do
you
want
to
talk
through
transition
stuff.
B
Yes,
I
do
so
I
added
a
heads
up
here.
You
know
I'm
transitioning
fully
to
the
manager
product
design
role,
but
I'm
still
congratulations.
Thank
you.
I'm
still
going
to
be
a
designer
for
testing
and
running
until
we
backfill
the
position
till
we
hire
someone
for
the
two-stage
groups
and
just
to
give
you
also
another
heads
up.
My
priorities
right
now
are
into
completing
the
transition.
B
So
all
the
trainings
and
the
things
that
the
organization
requires
from
me,
the
next
two
weeks
and
also
in
hiring
a
new
designer
so
valerie,
let
me
actually
let
me
see
if
someone
replied
to
my
message,
not
yet
so
valerie's
off
this
week,
so
I
don't
think
we're
going
to
move
forward
with
opening
the
the
request
or
opening
the
the
vacancy
this
week.
B
But
I
wanted
to
touch
base
with
you
about
some
requirements
for
this
role
and
I'm
not
sure
we
can
record
this,
but
then
I'll
just
put
this
video,
as
in
private,
just
in
case
yeah
yeah
and
then
to
add
some
questions
here.
I
think
it
would
be
important
to
hear
from
you
and
darren
on
what
you're
looking
for
type
of
experience
in
testing
experiencing
research
for
this
candidate.
B
A
As
far
as
past
experience,
I
don't
think
testing
experience
is
super
important,
but
experience
with
the
developer,
persona
and
building
data
views.
I
think,
because
of
the
work
that
darren
and
I
are
going
to
be
doing
at
the
like
management
dashboard
level
over
the
next
year.
Having
some
experience
there
is
going
to
be
really
really
helpful
for
us
in
making
sure
that
that
ux
is
tight
in
the
first.
A
Is
there
anything
you
like
specifically
stream,
for
I
mean
I,
I
trust
that
you're
going
to
find
a
good
candidate,
someone
who
matches
up
with
the
experience
that
traditionally
not
traditionally,
but
that
we
look
for
from
for
gitlab
designers
and
we
get
a
get
a
good
person
in.
A
No,
I
just
the
I
was
working
back
up
through
the
list.
The
experience
I
think
I
building
those
dashboards.
I
think
that
somebody
with
that
who
has
some
sort
of
experience
there
of
building
data
views
for
that
director
persona
is
going
to
be
great,
especially
if
they
can
mix
it
with
I've
worked
in
workflows
for
developers
or
for
devops
teams.
A
So
I
know
that's
a
very
hard
ask
if
I
was
preferencing,
I
would
preference
for
someone
who's
built
those
data
views.
I
think
that
we
have
enough
experience
and
we
can
empathize
with
the
developer
and
the
devops
engineer
persona
enough
that
we'll
be
able
to
help
with
this
is
what
that
workflow
is
like
this
is
we
can
talk
through
this?
We
have
we
can
dog
food,
these
things
internally
really
easily
and
get
that
feedback.
It's
going
to
be
harder
to
empathize
and
get
research
for
the
the
director
persona.
I
think.
B
So
hopefully,
from
my
experience
and
also
seeing
the
type
of
candidates
that
we
get,
we
usually
get
people
to
have
some
sort
of
experience,
building
death
tools.
So
we
can.
We
can
look
into
that
and
I
also
added
here
what
experience
in
ux
research
do
you
expect
from
this
person.
I
have
my
opinions,
but
I
would
like
to
to
hear
from
you:
how
do
you
see
yeah
the
the
the
the
new
designer
fitting
in
in
this
role?
I.
A
Mean
someone
who
isn't
afraid
to
go
talk
to
customers
would
be
great,
not
that
we've
ever
had
that
problem,
but
I
don't
think
that
for
the
most
part
we've
taken
the
lead
on
the
research
and
it's
fine
to
continue
going
down
that
route,
a
partner
there
would
be
great,
but
knowing
that
they're
splitting
time
between
teams,
their
most
important
role
is
to
do
the
design
part
and
make
sure
that
we
have.
You
know
great
interaction,
a
great
experience
for
the
customer.
More
so
then
they're
doing
the
research.
A
B
Awesome,
I
think
that
clarifies
I
still
have
the
same.
I
have
a
document,
I'm
not
sure.
If
you
have
access
to
it,
let's
see
no,
not
the
honor.
That's
we
created
to
backfill
juan's
position
last
year.
I
think
a
lot
of
it.
B
We
can
still
reuse
as
in
terms
of
a
requirement,
but
once
I
have
this
is
going
to
be
an
issue
with
the
with
the
hiring
people
and
once
we
have
that,
helping
you
and
aaron
to
give
feedback
to
see
if
everything
is
in
line
and
we
can
kick
off
the
hiring
I'm
assuming
next
week
but
I'll
be
posted
great
awesome.
That
sounds
great.
A
All
right,
I
didn't
have
anything
I
wanted
to
talk
about
my
weekly
priorities.
What
are
my
priorities
this
week?
I
should
look
at
these.
A
I'm
trying
to
get
ahead
on
some
usage
ping
definitions
to
help
out
the
data
team
or
the
product
intelligence
team.
I'll
do
the
I
have
to
merge.
My
performance
indicator
update
that's
a
couple
of
weeks
out,
but
I
can
merge
that
because
we
won't
have
march
data
yet
by
the
time
it
happens
and
then
finishing
up
all
the
release
related
stuff
across
the
three
releases.
A
1310
release
posts
have
all
merged.
I
don't
know
that
I
pinged
you
on
very
many
of
those
there's
the
new
it's
optional,
but
it's
recommended
to
have
designer
review,
I'm
happy
to
tag
you
and
actually
assign
you
as
a
reviewer.
A
If
you
want
to
look
at
those
for
13
11.,
we
had
some
usability
improvements
and
we
rolled
all
of
them
up
into
one
secondary
item.
Did
that
before
the
new
introduction
of
usability
improvements
as
its
own
section
like
performance
improvements,
are
so
going
forward
if
something
isn't
quite
enough
for
a
secondary
post
on
its
own
and
it's
not
a
new
feature,
we'll
just
list
it
in
that
usability
area.
Awesome!
A
So
I'll
tag
you
on
1311
stuff,
as
it
comes
out
at
the
end
of
next
month
or
the
middle
of
next
month,
and
if
you
have
time
to
review
great,
but
if
you
don't
no
worries,
I
know
you
have
a
lot
on
your
plate
right
now,.
B
Yeah
I
mean
I
usually
review
these
or
used
to
review
this
with
jackie.
But
for
me
it's
really
about
the
time,
but
even
if
I
don't
reply
I'll
check
the
ping
later
on
and
I'll
read
through,
I
think
it's
always
easier
to
see
in
the
diff
and
really
see
what
has
changed
in
the
page.
So
we
don't
have
to
read
all
the
information
if
you're
changing
a
category
page
or
something
like
that.
So
please
pay
me.
If
I
don't
reply,
don't
block
it
because
of
me.
A
Awesome
join
us
switch
recordings
and
I'll
record
the
kickoff,
so
we
can
get
it
uploaded.