►
From YouTube: Testing PM/UX weekly - 2021-02-09
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
There
we
go
so
this
is
the
pm
ux
or
pm
yeah
ux
designer
chat
for
verify
testing
for
february
9th
2021..
B
Let's
see
so
jumping
into
the
agenda.
I
moved
the
follow-up
items
to
the
top,
just
to
make
sure
that
we
touched
on
those-
and
I
think
I
saw
some
to-do's
this
morning
that
where
you
had
pinged
me-
and
I
think
that
that's
probably
one
of
these-
maybe
okay
cool.
A
Great
and
I
also
had
a
chat
with
darren
on
what
does
ui
polish
entails
for
runner
and
I
apparently
opened
a
much
more
difficult
discussion
in
ux
department.
A
So
I
just
edited
merge
requests
here.
I
don't
know
that
we
can
have
the
definition
clear
definition
in
the
handbook,
because
now
we
only
talk
about
the
label,
but
there's
nothing
really
in
context
with
the
system
usability
score
and
and
there's
some
confusion
yeah
just
like
that
versus
polish
versus
enhancement.
B
Yeah
I'll
take
a
look
just
where,
where
my
mind
goes
to,
when
I
hear
you,
I
polish
is
that
the
existing
interface
and
experience
is
clunky
and
it
could
use
some
improvement.
I
think
we
talked
about
this
last
week
where
it's
like
the
button.
Color
is
wrong,
or
it's
not
centered
very
nicely.
B
Weird
line
wraps
stuff
like
that
versus
hey.
This
experience
is
bad
and
we
need
to
add
data.
Remove
data
change,
workflow,
that's
a
ux
exter,
yeah
user
experience,
enhancement
for
me,
so
yeah.
A
Yeah,
that's
also
what's
in
my
head
and
that's
what's
in
my
proposal
and
let's
see,
let's
see
what
we
got
from
that
I
just
for
context.
I
looked
in
adam
he's
the
research
lead,
so
I
think
they
are
working
on
also
some
definitions
on
the
research
department.
B
A
B
I'll
try
to
find
that
issue
again,
just
to
be
sure,
but
that's
just
a
heads
up
for
you
right
now.
It's
just
a
problem
or
an
opportunity,
research
project,
so
I
don't
need
any
assistance
there
at
this
point,
cool
so
jumping
into
new
stuff.
B
What
are
you
working
on
this
week?
I
have
not
looked
at
your
priorities
yet.
A
Yeah
so
I
put
in
both
like
look
into
enterprise
runner
management.
So
that's
a
big
heads
up
for
my
week.
I
had
a
conversation
with
that
there
in
last
last
week
and
of
last
week,
and
he
asked
me
to
make
some
room
to
look
into
his
proposal
for
jobs
to
be
done
and
runner
and
how
I
can
help
there
so
that
he
can
move
forward
with
something
big
sessions
for
the
team.
So
I'm
gonna
do
that
third
tomorrow,
but
they
still
go.
A
Oh
my
goodness
yeah
I'm
doing
that
tomorrow
and
on
thursday.
So
just
so,
you
know
other
than
the
items
that
we
are
probably
gonna
discuss
this.
I'm
not
gonna
have
a
lot
of
room
to
work
on
new
items
for
for
testing,
and
then
I
have
a
bunch
of
design
manager
tasks
because
we
are
doing
the
engagement
surveys
and
career
development
conversations.
B
My
daughter
is
awake.
I
saw
a
light
turn.
A
B
I'm
not
blurry
yet
today
I
will
be
later.
I'm
sure
I
have
a
lot
of
meetings.
Well,
yeah.
I
don't
think
we
need.
I
mean
the
things
that
are
above
the
line
for
you
139.
If
those
get
wrapped
up,
then
we'll
have
plenty
of
front
end
work.
I
was
digging
through
our
roadmap
yesterday
trying
to
find
some
impactful
things
for
front-end
engineers
to
work
on.
B
They
are
cranking
right
now,
scott
already
pulled
what
was
going
to
be
the
marquee
1310
item
into
13.9
and
it's
in
review.
So
I
need
to
pretty
quickly
find
some
more
work
for
front
end.
So
I
propose
two
things:
that
designs
are
wrapped
and
they're
ready
to
go
and
there's
a
whole
other
epic
behind
that.
B
My
only
hesitation
with
that
is
its
core,
not
premium
or
ultimate
features,
but
I
think
that
it
would
still
be
a
great
enhancement
and
it's
basically
front
end
ready.
I
think
so.
Those
are
the
things
that
I'm
going
to
let
them
loose
on
and
then
I'll
try
to
prioritize
making
sure
that
we
get
some
design
work.
Your
way
that
we
know
will
be
ready
to
go
for
front-end
folks,
so
they're
not
just
twiddling
their
thumbs,
which
there's
plenty
out
there
for
them
to
work
on.
I'm
not
too
worried
about
that.
A
B
Yes,
you,
you
tagged
a
bunch
of
things
you
I
polish
right.
A
Yeah
but
they
are
all
related
to
these
enhancements,
not
all
of
them
mostly
related
to
the
enhancements
on
the
immersion
quest
widget.
So
I
was
thinking
about
it
today
as
I
while
I
was
updating
the
prototypes
for
the
one
issue
that
I
have
in
my
my
update.
That's
maybe
I
should
just
work
on
everything
in
one
single
figma
file
thing
like
here's,
what
it
should
look
like
and
then
you
can
break
it
down
and
yeah
just
assigned
to
two
front
ends:
yeah.
B
That
works
for
me,
if
you
want
to
do
it
in
one
file,
just
get
everything
in
there
and
then
we
can
just
pluck
the
parts
out
and
drop
them
into
the
design
tab.
That
sounds
great.
A
And
another
point
on
that:
ui
polish
related
to
the
merchandise
widget,
is
that
there
is
so
much
content
already
that
they
create
that
the
secure
team
has
produced,
there's
a
figma
file
with,
like
all
the
states
and
how
the
view
should
look
like.
A
So
I'm
gonna
actually
add
an
action
item
here
for
myself
to
check
touch
base
with
them
with
the
team
if
their
proposals
are
ready
to
be
implemented,
because
I
don't
want
to
be
redesigning
what
they
have
worked
on
already
in
the
past,
but
up
until
here
those
five
items
they
can
all
be
in
one
design
proposal.
A
You
do
for
the
you
know.
I
mean
you're
being
asked
to
each
each
product
designer
is
being
asked
to
prioritize
and
with
the
pms
to
help
implement
three
of
these
changes.
Three
ufo
exchanges,
this
the
whole
quarter.
So
if
we
can
tackle
yeah
at
least
that
one
merger
class
widget
area,
it's
a
big
win
for
in
terms
of
okr,
but
yeah.
B
A
B
B
Okay,
yeah
I'll,
take
a
look
through
those
others
and
make
sure
that
we
have
them
scheduled
to
do
here.
A
And
then
on
the
usability
polish
topic,
so
I
updated
the
design
proposed
in
the
on
the
issue
for
the
result,
in
that
summary,
widget
researching
type.
So
I
applied
all
pedro's
feedback
and
but
there's
a
couple
of
couple
of
questions
right.
He
made
a
proposal.
You
actually
followed
up
with
the
cleanup
for
the
testing
widget,
but
also
I
noticed
while
I
was
looking
at
some
merge
requests.
A
I
noticed
that
he
probably
has
that
his
backlog.
Let
me
show
you
actually.
A
And
this
is
one
of
the
things
I
don't
want
to.
B
A
A
So
annoying
anyway,
so
if
you
on
this
merger
class,
for
example,
if
you
expand,
expand
the
metric
reports,
security
scanning
and
then
the
test
summary
areas
yeah
on
the
on
the
widgets
on
the
on
the
other,
the
overview
and
then
scroll
down
there
and
then
expand
that
gap
right
after
under
where
you
merge
the
button
yeah
and
then
you
have
the
expand
buttons.
There
expand
metrics.
B
A
A
For
example,
there
is
a
just
a
different
formatting
on
this
whole
content
section
and
I
honestly
don't
want
to
go
in
that
direction
where
to
make
a
whole
update
and
a
proposal
for
testing
and
then
having
to
rediscuss
with
the
whole
design
team
and
we
paid
their
own
where
they
should
be
placed.
A
So
my
point
here
is
that
for
our
cleanup
and
that's
what
you're
going
to
see
in
the
figma
file,
if
you
open
it
on
the
link
in
the
agenda,
is
that
I
just
want
to
make
sure
that
we
talk
about
the
hierarchy
of
the
items.
The
positioning-
and
you
know
the
ui
polish.
If
you're
gonna
move
things
here
or
there,
I
think
it
should
be
done
at
the
at
this
secondary
phase,
so
we're
not
blocked
by
this
small
nitty-gritty.
You
know
discussions
related
to
dui.
B
So
that's
just
to
make
sure
I
heard
correctly
we
want
to
have
in
this
metrics
report
and
probably
the
same
in
the
code
quality,
because
it
has
a
severity
component
as
well.
A
A
Yeah
and
then
okay,
we
do
that
in
the
next
phase
on
the
issue
that
you
created,
I
think
a
week
ago
and
I've
sent
you
here
in
the
chat,
a
link
to
the
figma
file
that
I
worked
on
today,
just
if
it
opens
the
right
right
view
yeah
yeah.
So
this
is
what
I'm
proposing
for
us.
So
it's
really
looking
feel
not
functionality
and
any
change
in
the
in
the
code
base,
as
in
the
logic
of
the
component.
B
A
B
If
you
have
one
of
these
specific
to
the
metrics
report,
that's
actually
one
of
the
issues
that
I
just
pointed
scott
at
yesterday
of
there's
an
open
issue
to
reorganize
and
make
that
widget
easier
to
read,
especially
when
you
have
thousands
of
metrics,
and
so
what
I'd
proposed
was
sorting
or
we'll
sort.
This
way
of
the
new
things,
the
change
to
things
and
then
the
same
things
organized
that
way
with
these
little
mini
headers
in
there
and
then
the
label
at
the
front.
A
B
Yeah
go
ahead,
the
workflow
that
we
were
using
previously
or
the
workflow
I'd
like
to
use.
I
guess,
is
close
that
ux
issue
reference
the
implementation
issue
and
then
we'll
drag
the
design
into
the
implementation.
B
There
should
be
for
the
design
there's.
I
think,
there's
actually
two
yeah
in
the
problem
to
solve
of
that.
The
two
that
the
two
open
issues
are
there
and
the
same
design
can
go
into
both
and
I'm
happy
to
move
that
over.
B
A
A
Sounds
good
it'll
be
nice
to
just
vocalize
across
the
the
pms
who's
the
pm
for
secure.
I
know
that
just
use
the
product
line
manager,
but
just
let
them
know
that
we're
gonna
make
them
updates,
are
gonna
affect
well
all
pms.
Actually,
that
are
gonna
affect
all
widget
areas.
B
B
I
can
drop
a
read-only
item
into
the
next
product
agenda
as
well,
we're
making
a
change
to
some,
mr
widgets
and
how
they
present
to
standardize
with
what
secure
has
cool
all
right.
B
So
are
you
going
to
close
that
ux
issue
and
move
the
designer?
Do
you
want
me
to
just
okay.
B
Awesome
so
I
have
my
weekly
priorities
there.
It's
mostly
research
issues,
trying
to
get
some
surveys
fielded
and
digging
into
some
data
from
one
of
the
post
purchase
surveys.
B
B
Yeah,
I
was
just
waiting
for
a
thumbs
up
from
you
on
that
comment.
A
Like
in
which
comment
in
the
proposal,
okay,
cool.
A
B
Okay,
we
this
one,
looks
pretty
tiny,
so
I
might
have
scott
pull
this
forward
and
just
get
it
knocked
out
depending
on
how
much
the
tooltip
will
impact
things.
B
B
B
And
then
my
last
thing
was
about
this
week's
ops
think
big,
which
I
don't
see
on
the
calendar
anymore.
So
that's,
I
think,
a
null
for
us.
I
don't
think
we
have
a
think
big
this
week
now.
A
That's
true
I'll
check
with
ian,
because
I
know
that
he
actually,
he
shared
something
in
slack
for
the
ux.
So
this
icd
box
team
asking
here
I'll
just
link
the
agenda
item
to.
A
A
B
All
right,
I'm
pretty
sure
I
can't
make
it
anyway.
It
conflicts
with
everything
else
I
have
that
morning,
so
I
won't
make
it.
What
is
actually
my
topic
here:
okay,
yeah,
so
you
just
won't.
A
Yeah
just
fine
most
contacts.
I
have
oh.
B
A
Of
course
related
to
release
management,
but
for
both
testing
and
runner,
I'm,
like
so
I'll,
say
I
don't
I'm.
I
cannot
join
anyways
on
thursdays.
I
have
a
doctor's
appointment,
but
it's
a
good
platform
for
me
to
learn
what's
going
on
in
the
other
stage
groups,
but
if
you
don't
have
any
items
to
add
there,
I
also
don't
have
anything.
Unfortunately,
okay.
A
B
This
is
the
it
looks
like
the
topic
is
about
group
level
features
and
just
thinking
about
what
we
have
at
the
group
level
right
now.
It's
just
that
group
test
coverage
feature,
but
we'll
start
creating
more
like
test
history.
Test
execution
falls
into
that
as
well
code
quality
at
some
point
will
roll
up
to
a
group
level
feature
so
just
thinking
about
those
and
knowing
that
there's
already
discoverability
problems
with
the
few
features
we
have.
A
Do
you
have
a
place
where
I
can
find
that
information
a
little
bit
more
filtered
like
if
it's
in
the
one
of
the
direction
pages
for
for
testing
or
if
you
have
like
an
epic
that
talks
about
improving
the
the
organization
or
the
hierarchy
of
testing
at
the
group
level?
I.
B
Don't
have
anything
yet
I
don't.
There
might
be
an
issue
floating
out
there
to
organize
our
reports
into
a
testing
tab,
the
direction
page
that
juan
worked
up
that
direction,
vision,
design,
that's
at
the
in
the
code,
quality
and
the
code,
testing
and
coverage
direction
pages
alludes
at
that,
but
we
don't
have
anything
carved
out
any
issues
created.
I
believe
I
can
create
an
issue,
though,
so
that
we
have
something
to
track
here.
A
A
B
And
then
on
that
think
big
topic,
the
last
thing
I
wanted
to
or
that
I
thought
would
be
a
good
one.
It's
an
item
that
we've
been
talking
about
for
deprecation,
but
we
won't
get
in
for
14-0
is
there's
two
ways
to
set
test
coverage
today,
either
in
the
settings
or
in
the
gitlab
ci
yaml.
B
And
how
do
we
think
about
that
as
a
stage
or
even
as
a
section
of
when
things
conflict
and
when
you
create
something
in
one
place?
How
do
you
reflect
it
in
the
other
yeah?
That
just
seems
like
a
big
meaty
topic
for
us
to
dig
into
as
a
section.
So
it's
something
that
we
can
propose.
I
don't
know
that.
There's
a
problem,
it's
just.
A
This
week
or
last
week
with
some
designer,
especially
nadia
pipeline
authoring,
because
yeah
configuration
and
ci
file,
not
that
mostly
file
falls
and
pipeline
altering,
but
there's
an
overlap
also
with
configure.
So
I
talked
to
auto
configure
in
relation
to
the
the
kubernetes,
the
not
just
the
cluster
but
anyways
that
affects
runner.
There's
too
many
topics
in
my
client
in
relation
to
the
runner
to
gitlab
runner.
So
this
is
the
ci
file.
A
It's
one
of
the
items
in
the
design
scope
that,
like
just
like
settings,
we
all
own
and
therefore
nobody
owns
anything.
So
it's
one
of
the
challenges
and
hopefully,
when
I
off
board
as
a
design
manager,
I
want
to
have
the
time
to
look
into
this
high
level.
Overlapping
items-
or
you
know
all
functionalities,
so
ci
file
and
settings
are
a
great
starting
point
for
our
discussion.
So
if
we
can
create
a
topic
around
that
to
just
gather
some
information
would
be
really
awesome.