►
From YouTube: Verify & Release UX Team Design Review | 12 May 2020
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
Awesome
so
first
thing
before
we're
gonna
dive
into
the
actual
discussion
thanks
Dimitri
help
was
a
really
good
topic,
but
I
also
left
a
message
in
our
team
slack
just
just
wanted
to
check
in
with
everyone.
You
know
like
him
about
these
sessions,
because
I
noticed
that
lately
we
don't
really
have
a
lot
of
active
content
to
talk
about.
However,
you
know
I
always
think
that
the
design
review
sessions
are
ways
for
us
to
give
each
other
feedback
to
share
some
what's
happening.
Is
it
the
visual
work
is
a
design
work
is
a
research
work.
A
You
know,
I
think
that's
kind
of
like
a
nice
conversation
to
have
in
place,
I
understand
that
the
team
is
getting
smaller
and,
like
everyone
is
getting
busier
and
busier,
so
just
to
reinforce
and
I
want
to
like
kind
of
here,
maybe
some
ideas
from
you
or
some
concerns,
maybe
that
you
may
be
having
around
this
session.
So
I
referred
everyone
to
go
to
the
retro
for
these
sessions.
Please
leave
me
a
message
or
feel
free
to
just
reach
out
directly.
A
A
C
So
you
know
I
mean
like
there's
gonna,
be
times
where
I
know
that
there
have
been
times
that
we
come
to
these
me
and
we're
like
oh
well,
there's
nothing
to
talk
about,
but
we
still
kind
of
get
an
update,
so
I
feel
we
should
keep
them
and
in
case
we
don't
have
anything
to
talk
about.
We
just
make
like
a
shorter
version
of
it
like
intentionally
shorter,
but
we
share
ideas
or
we
share
updates
and
whatever,
but
I
yeah
I
feel
those
lot.
It's
very
valuable.
So
I
don't
want
to
lose
this
lot.
A
That's
also
that's
a
proper
feedback
and
you
know
maybe
that's
just
like
in
my
mind,
like
it's
also
like
saying
hey,
you
know
you
come
down
this
our
variable.
Sometimes
we
need
a
break.
You
know
it's.
Maybe
just
in
my
head.
I
just
wanted
to
have
like
a
back
connection
with
you
or
you
know
that
I'm
not
like
pushing
this
out
of
like
hey
joy.
Everyone
subscribe,
that's
also
very
valuable.
D
Don't
have
like
anything
to
discuss,
we
can
just
cancel
or
just
say
that
we're
not
going
to
join
our
rather
habits
and
then
yeah
find
the
opportunity
to
just
talk
about
something
that
it's
completely
unrelated
to
the
Design
Review
per
se.
But
I.
Think
it's
bad
about
using
media
I'm
problem
session
is.
A
B
Yeah
no
problem
I
am
piggybacking
on
myself
proposed,
but
I
watched
his
video,
so
myself
created
an
issue
based
on
a
little
personal
walkthrough
of
the
merge
request,
widget
in
like
a
common
scenario.
That
is
not
that
you
know
out
of
the
ordinary.
He
recorded
it
and
you
know
showcase
a
little
made,
a
little
presentation
about
which
pain
points
he
kind
of
looks
at,
and
this
is
related
towards
the
OPRS
of
q2,
which
intend
to
improve
the
merge
request,
widget
amongst
issues
and
then
something
else
I
would
need
to
look
into
it
anyway.
B
The
video
kind
of
spoke
through
to
to
me
personally,
just
because
you
know
you
see
it
and
you
know
it's
there.
It's
just
one
of
those
things
that
you
know
it's
been
bugging
you
so
long
that
you
have
gone
numb
to
it,
which
you
kinda,
you
know,
gets
to
either
in
a
few
other
ways
inside
of
his
video
but
I.
Think
like
as
we're,
focusing
both
with
this
effort,
as
well
as
with
the
okie
art
on
request.
B
We
perhaps
can
now
put
a
pin
in
it
and
actually
get
something
done
then
create
like
I
craved
here.
A
little
length
create
this
sacred
did
a
whiteboarding
session
on.
You
know
the
issues
they
found
they.
You
know
they
discuss
some
ideas,
the
pain
points
which
ones
are
actually
very
important,
which
ones
are
less
and
they
make
like
this
priority
matrix
whiteboarding
session.
They
shuffle
them
around.
So
my
thoughts
are
here
too.
If
we're.
B
To
discuss
the
merge
request,
widget
see
hey
what
information
is
in
there.
First
is
the
actual
value
it's
giving
towards
the
end
users
and
then
see
like
hey,
which
current
research
corresponds
with.
You
know
the
things
we
jot
down
and
then
get
to
some
related
issues,
and
perhaps
if
we
got
ten
left
over
but
I
wonder
about
that,
you
know
do
a
little
bit
of
a
silver
white
morning
session
which
we
can
post
aux
Channel,
and
we
can.
B
A
Thanks
for
that,
intro
Dmitry
I
was
I'm.
Surely
here
there
okay
are,
are
that
that
creates
team
will
be
working
on
so
I
think
the
first
important
part
I
think
in
order
for
everyone
to
understand
what
the
what
the
issues
being
discussed
is
to
watch
the
video
and
the
issue
and
I'm
not
sure
if
everyone
because
have
come
through
that,
did
anyone
not
have
gone
through
that
yet
so.
C
A
Non-State
groups
categories
probably
and
then
Vienna,
probably
to
alter
the
mobs
as
well
and
like
to
the
pipelines
to
you.
So
it
sounds
like
there
is
a
lot
of
connections
to
our
stage
groups
in
any
way.
So
maybe
like
a
couple
of
good
questions
to
start
with,
is
you
know
like
do
we
have
some
issues
already
out
there
existing
that
are
pointing
to
Corrections
of
these
issues
that
we've
been
that
Marcel
is
colliding?
Have
we
ever
come
in
any
user
research
across
similar
feedback,
I.
C
Know
that
in
testing
we
have
at
least
a
couple
issues
that
are
both
bug,
fixes
I
mean
like
yeah,
but
things
that
are
meant
to
fix
the
functionality
that
it's
not
reliable.
We
have
a
couple
of
those,
then
we
also
have
an
issue
on
improving
the
overall
language
of
our
widgets,
make
it
more
clear,
sometimes
like
the
language
super
vague,
because
I
detected
only
from
the
source
branch
only
and
we
have
be
having
discussions
about
that
now
being
super
clear.
C
Security
has
definitely
a
couple
of
things
that
they
want
to
do.
I'm,
pretty
sure
about
that.
I
haven't
seen
the
issues,
but
I
know
that
I'm
tacked
on
one
that
usually
has
activity,
it's
probably
still
open,
but
security
is
looking
at
with
their
own
ways
to
fix
these
like
their
own
issues.
In
the
past
we
did
so
I,
don't
know,
I.
C
B
C
A
The
first
good
stuff
here
and
correct
me,
if
I'm
thinking
wrong
about
that,
maybe
we
could
collect
the
issues
that
are
existing
today.
It
could
be
in
a
way
to
meet.
You,
like
you,
proposed
in
the
mural
board,
to
kind
of
like
collect
everything,
that's
out
there,
and
maybe
we
can
make
a
plan
to
bring
it
up
with
the
PM's
in
the
appropriate
stage
groups
for.
D
Release
management
well
I'm,
just
asking
the
issue
it
was
created
yesterday.
That's
what
I'm,
not
good,
where
is
this
coming
from
I?
Don't
think
that
we
have
any
specific
research
that
talks
about
like
yeah,
if
the
data
or
what
it's
me
in
this
plate,
is
it
relevant
or
not?
We'd
have
use
cases
when
our
customers
we
just
want
an
easier
way,
for
example,
to
navigate
to
deployment
and
to
find
a
correlation
with
inquire
needs
from
the
large
requests
and
I
found.
D
There
are
some
user
research
in
size?
Well,
that's
I,
think
I'm
much
more
familiar
with
the
this
research
gives
cases
from
progress
of
delivery
from
things
that
we've
looked
into,
for
example
Baltimore's
trains
from
last
year.
But
then
you
know
me
to
dig
into
those
those
details
to
finds
anything
related
if
these
are
be
scheduled,
also
I'm,
not
sure,
but
I
think
for
these
management
yeah,
it's
a
it's
a
different
spectrum,
I
guess
and
it
doesn't
touch
much
merge,
request.
Widget.
B
D
E
And
I
just
did
a
I
just
searched
for
the
tag
merger
class.
There
are
like
94
pages
of
issues
related
to
merge,
request,
so
I'm
not
really
sure
I
need
to
figure
out
how
I'm
gonna
focus
my
effort,
so
I'm
gonna
meet
with
Marcel
next
week
to
talk
about
what
he's
done
and
all
of
this
cuz
it's
all
over
the
place,
and
it's
like
everybody's
finding
little
things
that
they
want
to
fix,
but
I'm,
not
I,
don't
think
anybody's
really
run
research,
I'm
sure
they
talked
to
people
and
got
feedback,
but
I,
don't
think
any.
E
C
One
thing:
I
wanna
mention
I'm,
pretty
sure
that
if
you
do
what
savvy
the
dive
in
into
the
issues
a
community
pro
community
issues
once
provided
by
the
community,
you
will
find
a
lot
of
reports.
The
problem
is
that
they
are
hard
to
find
because
customers
don't
refer
to
them.
As
mr
widgets,
that's
that's
internal
code
for
us,
you
know
like
they
don't
know
that
they
are
called
widgets
internally,
they're,
probably
referring
to
them
differently
like
the
equalization
of
the
pipelining.
They
are.
C
A
I
also
have
got
been
in
communication
with
data
team
and
like
we,
with
the
help
of
the
p.m.
and
the
e/m
of
the
needed,
dedicated
stage
group,
we
can
request
the
the
tracking
of
the
analytics
on
the
particular
parts
of
the
screen
like,
for
example,
how
many
times
what
was
a
certain
icon
or
button
oppressed
and,
like
you
know,
we
can
do
a
B
testing
and
stuff
like
that.
So
we
could
request
that
data,
but
I
try
to
look
into
that
to
myself.
A
B
Yeah
this
a
bit
of
a
they
say
it
is
such
a
interesting
UI
where
everybody
is
involved
with,
but
at
the
same
time
you
know
it's
it's
it's
so
hard
to
touch
as
if
you
change
something
it
will
change
things
for
everyone,
but
certainly
an
interesting
one
to
to
look
into
it.
But
I
looked
into
for
CI,
or
at
least
the
first
things
that
came
to
my
mind
were
like
a
bidding.
I
can
button.
B
Styling
I
was
like
this
thing
is
like
thread:
simplify
your
initiative
status
I
can
SVG's
like
giving
it
purely
CI,
because
I
I
would
very
soon
going
to
testing
area
and
and
other
stuff.
So
you
know
it's
it's
hard
to
find.
You
know
great
inspiration
from
CI
perspective
here,
but
I'm
all
ears
of
everybody.
If
anyone
else
has
suggestions
there.
B
A
Maybe
it's
a
good
point
to
start
from,
like
researching
from
the
stage
group.
Okay,
what
are
the
things?
What
are
the
feedbacks?
What
are
the
issues
that
are
already
out
there
today
and
then
also
documenting
some
of
these
ideas
like
going
into
the
community
forums
and
checking
what
feedback
that
we
received
there,
plus
the
research
that
Lori
will
be
doing
soon,
would
be
useful
to
have
a
look
into
that
before
probably
like
diving
into
any
solutions.
I
feel
like
we
need
to
be.
B
A
quick
question
regarding
that
so
I'm
all
for
creating
the
issue,
but
just
creating
issue.
It's
not
enough
right.
Just
the
issue
we're
not
going
to
use
it.
It's
gonna
float
around
there
and
until
it's
forgotten
and
not
not
like
it
does
them
any
use
anyone.
So
if
we're
gonna,
do
this,
how
we're
gonna,
how
we're
gonna
put
focus
behind
and
how
we're
gonna
push
it
well,.
A
Assigning
India
right
right
and
in
okay,
our
issue
that
I
linked
in
the
beginning,
so
Marcel
is
already
asking
for
involvement
from
the
other
stage
groups
and
we
fall
on
a
radar.
He
particularly
asked
for
our
help
because
hey
there
is
a
lot
of
dependency
into
that
see
ICD
part
of
the
platform,
so
yeah
I,
don't
think
I
understand
where
your
feedback
about
some
of
the
issues
being
lost
coming
from,
but
I
don't
feel
like
this
one
is
particular
I
feel
like
we
just
need
to
prepare
collect
some
information
before
making
a
plan
of
attack.
A
C
C
A
So
because
yeah
I
think
that's
gonna,
be
for
us
and
like
in
investigation
issues,
well
yeah,
so
having
it
to
the
separate
thread,
but
because
this
is
actually
an
epoch.
That's
that
I
put
here
and
that's
all
so
that
makes
sense
to
Cadillac
connecting
issues
to
the
epic
all
related
stuff.
To
my
perspective,
that
would
that
would
be
a
bit
better,
because
this
one
is
an
epic.
D
A
All,
for
example,
we
can
also
create
our
own
OPR
and
connected
to
to
this
one
right
like,
for
example,
the
the
queue
to
you
are.
Ok,
ours
they're,
really
directed
a
lot
into
the
create
stage
and
documentation.
If
we
want,
we
can
always
make
a
small
little
OPR
for
allergy.
For
that.
I
haven't
yet
open
an
issue
for
verifying
the
release.
You
asked
whether
your
PRS
but
I
could
do
that
and
conduct
this
contribution
to
that.
Ok
are
in
from
ours.
If
that
would
be
helpful,
I
don't
know
I.
C
B
A
I
hope
that
will
calm,
West
England
with
the
research
investigation
here,
like
you
know,
at
least
here
we
can
put,
can
put
them
fresh,
bold
world,
for
example,
for
testing
and
maybe
for
progressing
deliberate
work
that
contribute.
If,
of
course,
we
got
the
back
by
in
50
p.m.
but
we
can
see
how
to
tackle
an.
A
Thanks
Juan:
well,
that's
proposal
from
myself
and
like
I,
received
that
thumbs
up
from
Jimmy,
T
and
Laurie,
but
yeah
I.
Just
because
of
this
moments
right
now
their
product
is
happening
and
sometimes
I
feel
like
such
an
important
things
are
being
discussed
there
and
I'm
there
for,
as
opposed
to
move
this
meeting,
and
it's
it's
pretty
tough
due
to
pretty
busy
agenda
everyone's,
but
also
I,
don't
want
to
move
it
to
other
days
than
Thursday
in
Tuesday's,
because
I
feel
like
this
is
where
Demetri
works
among
us.
A
E
E
C
A
We'll
see
if
we
need
the
45
minutes,
you
know
we'll
see
how
this
works
one
yeah,
maybe
we
can
make
try
to
make
them
half
an
hour
and
then
we'll
see,
because
anyway,
from
the
feedback
for
this
session,
we
discussed
not
from
earlier
retrospectives.
We
discussed.
We
don't
want
to
cover
more
than
two
items
anyway.
Yeah
yeah
I
feel
I
feel
bad
about
this
honestly,
but
a
new.
C
A
Moving
is
such
a
painful
procedure,
but
I
want
us,
you
know,
like
yeah,
I
feel
good.
You
asked
close
and
with
the
product
and,
if
you
know
or
sometimes
I
want
to
make
an
announcement
and
I
really
want
to
be
there,
and,
if
you
like
me,
not
being
present
or
like
us
not
being
present
at
the
product
like
hides
the
visibility
of
that
so
I
feel
like
that's
when
it's
particularly
important,
if
anyone
has
any
better
date,
please
let
me
know
know.
C
E
E
So
that
helps
with
anything
I
know
or
eaten
Israel,
so
she's
just
she's,
probably
fine
for
you
Dimitri,
but
for
me
she's
just
a
little
bit
too
far
around
the
world.
So
we
try
to
meet
for
her.
So
it's
not
so
late
in
the
afternoon
or
the
evening
time
for
her.
So
you
just
let
me
know
you.
My
calendar
is
up-to-date
Dimitri.
If
you
find
something
on
the
calendar
that
you're
like.
Can
you
just
move
that
just
ask
me
and
I
sleep
like
you
super.
B
A
And
let
me
know
how
I
can
help
you,
because
I
started
all
of
this,
so
I'm
helping
you
to
get
out
of
that.
I
appreciate
everyone's
flexibility
and
openness.
For
these
thanks
a
lot
all
right.
Well,
also
Dimitri,
thanks
for
giving
this
a
no
and
issue
for
this
topic,
I'm
gonna
be
following
up
on
that
and
after
are
you
pretty
sure?
Oh
it's
nice.
If
everyone
goes
and
played
places,
their
links
to
other
things
that
might
be
helpful
might
contribute
to
this
kokr.