►
From YouTube: Progressive Delivery UX/PM meeting 2020-05-26
Description
Meeting to improve alignment between Product Management and UX for progressive Delivery
A
All
right,
thanks
all
for
being
here
to
start
off
with
first
point
is
or
it's.
B
Yeah,
so
there
was
a
point
on
the
agenda
to
go
through
the
current
research
issues,
so
I
just
wanted
to
update
about
the
post
monitoring
deployment.
So
I
pretty
much
finished
interviewing.
I
interviewed
five
people,
two
of
them
weren't
that
great
so
we're
trying
to
recruit
another
two.
The
only
question
I
have
is
regarding
payment
because
they've
been
bugging
me
about
paying
them
and
I
think
emily
wanted
to
do
that
themselves.
Herself.
So
I
don't
know
who
I'm
supposed
to
nag
about
that
emily.
C
And
it
could
have
something
to
do
with
where
they
are
so,
which
country
or
something
like
that.
So
if
they
weren't
I've
seen
some
stuff
come
through.
Like
some
strange
I
shouldn't
say
strange
countries,
but
some
other
countries
that
we
don't
really
talk
to
people
from
that.
Much
are
more
difficult
to
pay,
sometimes
because
they
don't
accept
many
forms
of
money
except
money.
So.
B
It
was
interesting
because
almost
everyone
that
I
had
in
the
interviews
said
they
were
from
the
states,
but
I
interviewed
them
at
really
odd
times
in
the
day,
which
made
no
sense
for
for
them
to
be
in
the
states
and
and.
A
C
A
All
right,
then,
on
to
the
next
topic.
Next
topic
is
on
mike
nichols
being
derived
a
little
bit
longer
for
future
flags.
I
already
discussed
this
with
most
people,
but
now
lori
is
part
of
it
as
well.
A
So
as
the
work
for
feature
flag
is
being
pushed
out
a
little
as
I
heard
from
or
it
and
mike
has
been
been
involved
in
all
the
work
that
is
currently
still
ongoing,
nadia
helped
me
out
a
little
bit
here
and
said,
like
it
might
be,
makes
sense
to
keep
mike
involved
a
little
bit
longer.
A
The
idea
should
be
that
mike
will
be
involved
in
future
flags
work
that
is
already
existing
and
and
scheduled
in
a
way
or
about
to
be
scheduled
and
I'll
be
taking
on
any
future
flight
work.
That
is
past
that,
but
it
will
take
a
little
bit
of
time
before
we
can
get
to
that.
As
I
understood
it,.
B
Yeah,
well,
future
flag
has
been
postponed
just
so
you
know
not
because
of
a
change
in
priority
is
just
really
going
super
slow
with
development.
So
to
be
realistic,
I
don't
think
we're
going
to
achieve
what
we
had
planned.
B
D
B
D
A
Cool,
let
me
see,
I
think
this
was
already
discussed,
suggestion
to
create
a
new
category
for
a
b
testing
splitting
them
off
from
feature
flight.
With
word,
that's
explained
to
me
and
I
believe
in
the
101
that
we
are
limited
by
the
amount
of
categories
per
stage.
I
see
right
here.
It
is
it's
kind
of
funny,
though,
that
we're
limited,
but
it
is
that
strict
on
that,
but
hey
if
our
hands
are
tight,
our
hands
are
tied.
B
I
also
don't
think,
there's
a
good
enough
justification
at
the
moment
to
fight
it,
because
a
b
testing
currently
doesn't
exist
and
our
feature
flag
solution
is
there,
so
I
don't
see
why
not
to
tie
them
together.
It's
not
like
they're
humongous,
like
cd,
where
we
can't
get
our
heads
around
the
jobs
to
be
done,
and
it's
just
so
enormous
it'll
take
us
a
year
to
get
through
that.
So
really.
In
that
sense,
I
think
that
it's
okay
to
to
combine
the
two.
A
Awesome
all
right,
then,
on
to
the
next
one
I
saw
a
mention.
I
didn't
link
it
here,
but
I
love
being
included
on
the
direction
page
changes
you
mentioned
me
somewhere
in
merch
quest.
I
think
I
think
it
was
on
the
change
from
the
incremental
rollout
to
being
renamed
to
advanced
deployments
and
yeah.
I
would
love
to
see
that
trend
continue
be
like
include
like
product
design
everywhere
in
like
those
kind
of
changes
not
to
per
se
like
in
anything
like
approval
kind
of
way,
but
more
like
informative
way.
A
Sure,
thanks
for
that,
can
the
ux
kickoff
be
included
in
the
official
pm
kickoff.
So
what
we've
started
doing
from
this
milestone
onwards
is
as
the
ux
department
or
at
least
verifying
release.
We've
started
creating
a
ux
kickoff,
which
means
that
we're
showcasing
a
little
bit
telling
a
little
bit
about
where
we're
busy
with
for
the
current
milestone,
even
though
that
work
might
not
directly
touch
implementation
for
the
current
milestone,
and
then
we
got
feedback
immediately.
A
I
think
it
was
hayanna
that
got
feedback
that
it
might
make
sense
to
combine
them
and
in
that
way
expose
it
a
little
bit
more.
So
I
would
love
your
thoughts
about
that.
B
I
don't
really
have
an
opinion
if
that
makes
any
sense,
so
the
only
there's
two
things
that
I'm
a
little
bit
hesitant
on
saying
automatically.
Yes,
one
of
them
is.
I
think
that
all
the
stages
should
probably
be
the
same.
So
I
think
this
is
a
great
process
change
that
should
probably
be
decided
by
someone
above
me,
so
you
know
someone
who's
in
charge
of
all
the
stages,
because
I
think
it
would
be
strange
that
only
our
stage
would
have
like
some
kind
of
different
format.
B
B
and
usually
up
until
now,
not
that
I
think
it's
good.
We
have
been
negotiating
past
the
18th,
so
I'm
not
sure
logistically
how
that's
going
to
happen
like
I
think
it's
a
good
idea,
I'm
just
concerned
about
how
yeah.
D
And
so
like,
regarding
your
first
concern,
I
think
that's
a
very
valid
one.
I
don't
think
we
should
be
doing
anything
differently,
but
if,
like
I
think
what
we
should
try
to
do,
if
we
will
say
that
for
13.2
we
try
to
do
the
kickoffs
videos
together,
ux
accent
pm,
then
we
can
end
lift
yeah
and
probably
jason
and
kenya
will
help
bringing
this
to
the
other
pm's
as
well.
D
If
that's
going
to
be
working
out
nicely,
so
I
can
help
also
taking
care
of
that
together
with
jason
and
stuff,
because
initial
feedback
came
from
jason,
hey.
I
didn't
like
seeing
two
videos
similar
content
and
he
thought
it
would
be
a
cool
way
for
us
to
collaborate
between
management
and
the
user
experience
regarding
the
second
one.
D
What
we
are
trying
with
hayana
and
kwan
for
this
for
the
13.2
for
the
next
milestone
is
that
the
it's
basically
even
should
be
helping
the
pms,
because
the
ux
team,
the
user
experience
product
designers,
will
record
issues
that
are
ux
heavy.
So
they
will
do
the
the
kickoff
part
for
that
walking
through
record.
That
part,
then
the
rest
will
be
recorded
by
the
pm,
and
then
we
will
combine
the
videos
so
like
squeezing
two.
So
basically
you
should
not
be.
D
It
could
be
even
less
of
a
job
for
you
yeah.
Probably
it
will
be
a
little
bit
more
work
for
designers
in
the
beginning,
because
I
can
imagine
they
will
need
to
make
sure
that
they
understand
what
they
are
talking
also
about,
and
you
know
that
it's
more
or
less
in
the
same
format.
A
D
Each
other
yeah.
A
B
So
I
don't
know
our
planning
process
hasn't
been
smooth
at
all.
We
find
out
the
spillover
too
late
and
then
I
need
to
pull
out
issues,
and
I
don't
want
to
record
issues
that
I
know
we're
not
going
to
work
on
it's
something
that
I
talked
about
with
chase
and
we're
going
to
try
again
to
fix
this
in
13
2.
But
I
don't
know
so
far.
This
has
been
my
experience
and,
for
example,
because
we
release
on
the
22nd
every
month.
B
The
timing
of
the
day
of
the
week
is
really
crucial,
because
this
we,
this
time
it
was
on
saturday
and
I
think
the
kickoff
needed
to
be
ready
by
saturday,
and
I
don't
work
on
friday
and
there
was
like
some
holidays
so
like
there
was
a
lot
of
reasons
why
people
were
off
and
we
couldn't
really
talk
about
the
issues
and
we
were.
B
I
was
just
waiting
around
for
answers
for
like
a
really
long
time
and
then
I
ended
up
just
recording
something
with
answers
which
we
ended
up,
posting,
which
I
wasn't
very
happy
about.
So
I
don't
know
something's
wrong
with
that
process.
But
that's
regardless
to
this
specific
issue.
A
Okay,
that
does
make
it
a
little
bit
hard
to
overcome
that.
So
how
do
we
suggest
that
we
make
this
a
reality
like
like
we
both
record
a
video
and
then
we
combine
them
and
upload
them
to
youtube?
B
A
Can
you
repeat
one
more
thing,
so
the
planning
like
I'm
looking
for
the
dates
here,
the
date
that
the
planning
is
done,
the
date
that
the
spillgover
comes
in
then
the
date
that
the
planning
is
revised
and
then
the
date.
Then
the
videos
need
to
be
up.
B
Okay,
so
the
videos
need
to
be
up
by
the
18th,
the
planning
issue
I
had
a
date.
This
is
the
something
we're
trying
to
improve
the
process.
So
I
added
that
it
needs
to
be
done
by
the
13th,
which
gives
us
five
days
basically
to
record
the
videos.
B
Pillow
over
the
spillover,
sorry,
the
spillover
is
very,
very
tricky
because
we
have
a
few
different
times
where
the
code
can
be
accepted.
So
the
there's
an
official
code
cutoff
date.
It
changes
it's
on
the
15th,
but
I'm
not
sure,
and
basically
we
should
know
the
majority
of
the
issues
then.
But
since
we
have
deployments
going
once
a
day,
I
think
marin
told
me
there's
additional
time
slots
that
things
may
be
merged
and
they
might
not
spill
over.
A
B
Yeah
I'll
add
that
you
can
continue
to
the
next
next
point.
A
Yeah,
I
already
discussed
this
in
the
one-on-one
with
because
I
wasn't
sure
if
I
had
included
it
in
this
many
years
or
no,
but
we're
going
to
use
dovetail
going
forward.
A
Laurie
has
said
to
me
earlier
when
we
spoke
about
this,
that
sarah
o'donnell
is
working
on
handbook
resource
materials
in
order
to
make
everybody
proficient
in
this
tool.
Is
that
is
that
going
well
that
process
lori
yeah.
C
I
will
put
a
link
to
the
page
in
our
agenda
here,
so
she
went
ahead
and
pushed
it
all
of
the
researchers
haven't
used
it
yet
like
some
we're
in
all
in
various
stages
of
trying
to
use
it
for
the
first
time.
So
we
encourage
everybody
to
get
in
there
and
poke
around
figure
out
what
you
can
do.
There's
a
there's,
a
page
that
dovetail
has
created.
C
That's
got
like
a
welcome
to
dovetail
video
montage
and
that's
where
they
pointed
me
when
I
asked
them
for
additional
resources
to
share
with
my
design
and
product
management
team.
So
it's
it's
not
bad.
It's
just
not
in
depth,
but
it's
enough
to
get
you
started
so
ori.
You
should
have
already
gotten
the
invitation.
I
think,
last
thursday,
from.
C
C
B
A
B
C
Yeah,
okay
and
let
me
know
if
it
doesn't
work,
but
you
should
be
able
to
get
in
so
we're
gonna
use
that
now
the
biggest
change
is
that's.
Where
we're
going
to
be
putting
our
insights
so
no
longer
worried.
Well,
you
have
to
put
them
into
our
insights
repo,
we're
actually
using
dovetail
to
store
them.
So
it's
it's
easier
to
make
them
because
dovetail
will
help
you
to
tag
things
that
I
said
like
frequency
like.
Oh
five.
People
said
something
about
this,
and
this
is
what
they
said.
C
So
you
can
go
back
and
look
at
those
five
things
and
go.
Oh,
that's
it
that's
good
and
then
you
can
tag
it
as
an
insight
appropriately,
and
so
it
kind
of
attaches
itself
to
that
project
as
an
insight
moving
forward
so
and
that's
the
extent
of
my
knowledge
of
how
it
works,
I
really
need
to
get
in
there
and
play
around
okay.
A
Sounds
good
yeah
happy
to
try
that
out
going
forward,
especially
if
it
takes
automate
automate
some
of
the
stuff
right.
A
Then,
if
there's
no
for
the
comments,
let's
jump
on
to,
I
think
my
last
point
for
this
one.
So
earlier
today
I
had
a
discussion
with
marcel
and
nadia
on
ux
stepped
and
white
polish.
I
think
I
filled
you
in
orid.
I
asked
previously
on
the
triage
issues
like
hey.
What
do
you
think
about,
including
ux
that
thank
you
like
polish?
After
doing
some
investigation,
apparently
ux
depth
was
already
included.
A
However,
ui
polish
was
not,
and
I
did
some
experimentation
and
created
a
merge
quest
to
include
that
as
well
and
additionally,
heat
maps
are
now
included,
so
charge
report
is
a
little
bit
more
extensive,
though
it
looks
very.
A
Yeah,
it's
it's!
It's
pretty
nice,
however,.
A
Awesome
happy
happy
to
set
that
trend
forward,
so
the
the
the
thing
that
what
I
wanted
to
discuss
briefly
is:
what
is
your
process
in
terms
of
the
triage
reports
because,
like
we
have
them
and
I'd
say
from
my
point
of
view,
it's
like
there
to
for
us
to
make
sure
issues
are
triaged
and
we
maintain
you
know
the
balance,
but
you
know
I
saw
that,
for
example,
the
last
triage
report
for
press
delivery
was
already
you
know,
like
you,
didn't
you've
done
some
things
and
you
closed
the
issue
and
because
I
was
looking
for
the
issue
and
then
I
couldn't
find
it
because
it
was
already
closed.
A
B
A
B
So
that's
that's
a
great
question.
So
basically
what
I
do
there
in
the
report
is
it
basically
tells
me
everything
that
doesn't
have
a
milestone
scheduled,
and
so
I
look
into
it
and
I
schedule
a
milestone
now,
90
of
the
time
I'm
going
to
put
it
in
the
backlog,
I
think
the
only
time
that
we're
actually
going
to
schedule
a
milestone
for
those
issues
is
during
the
planning
when
you
suggest
specific
issues
for
planning
or
if
you
know
something
comes
up
and
you
think
it's
really
critical.
B
But
as
long
as
it
looks
like
a
p4
and
and
something
like
that,
then
then
it's
going
to
stay
there
I
mean
I
read
through
the
issues
I
even
commented
on
one
of
them.
One
of
the
issues
was
something
hayana
had
opened
like
11
months
ago
about
the
fact
that
there's
a
box
that
doesn't
look
right
on
one
of
the
one
of
the
message
boxes
which
we're
going
to
work
on
anyway.
B
A
B
Great
so
100,
I'm
with
you
on
that,
and
that's
why
I
said:
let's
push
them
on
the
planning
issue,
keep
in
mind
that
at
the
moment
we
only
have
one
front
engineer.
So
it's
going
to
be
hard
to
do
everything.
However,
once
the
new
front-end
engineer
comes,
which
is
rumored
to
be
this
month
sometime,
we
can
push
probably
a
bunch
of
ux
polish
and
take
that
and
easy
onboarding
issues.
So
we
can
get
a
lot
done.
B
D
And
that's
clear,
you
know
it's
kind
of
like
we
understand
yeah,
it's
it's
a
nice
guideline,
but
yeah
you
don't
have
resources
yeah!
That's
obvious!
Yeah.
A
Are
there
plans
to
increase
the
the
front-end
engineering
availability
for
progressive
delivery.
B
So
only
one-
and
that
only
happened
because
sarah
moved
over
to
ci-
and
I
made
a
lot
of
noise.
They
were,
they
didn't
want
to
backfill
her,
and
I
was
like
I
can't
work
like
this
blah
blah
blah.
Anyway,
we
got
the
backfill,
so
progressive
delivery
does
have
more
back
end
work
than
front
end,
so
I
think
that
the
ratio
that
for
two
is
okay.
A
All
right,
thanks
for
that
very
clear
and
then
on
to
nadia.
D
Yeah
final
point
morris
fyi,
I
think
well
already
dimitri.
We
have
been
talking
with
you
on
that.
I
also
just
wanted
to
update
lori
on
that
that
we
have
been
working
to
correct,
well
correct,
just
a
little
bit
the
way
how
we
plan
and
the
ux
work
and
the
research
work
as
well.
So
we
have
a
few
issues
that
we
have
updated
and
some
of
the
those
we
have
added.
So,
for
example,
we
have
added
the
ux
labels
to
the
quarterly
priorities,
issues
to
mark
those
ux.
D
You
ask
things
that
we
need
to
focus
on.
I
think
the
same.
We
should
do
for
research,
actually
maybe
using
the
same
label.
I
don't
know
just
like
to
give
us
some
visual
visibility
for
four
things
that
need
our
attention.
In
the
quarter
in
milestones
planning,
we
had
added
a
clear
section
for
ux
work
where
we
are
like
adding
the
issues
that
we
will
tackle
in
that
milestone.
D
We
also
have
created
the
need
ux
review
issue,
it's
similar
guyana,
to
the
release
management,
one
where
reid,
dmitry
and
sometimes
mike
will
be
like
yeah
discussing
the
upcoming
ux
work.
That's
not
really
clear
at
this
moment
yeah
and
possibly
assigning
that
to
a
milestone
or
possibly
a
aligning
on
the
first,
like
kind
of
like
estimation,
numbers
there,
yeah
and
also
we've
been
talking
about.
You
know
giving
a
good
attention
to
the
needs
weight
issue
for
the
engineering
yeah.
D
I
guess
the
plan
for
the
immediately
to
walk
through
those
like
I
don't
know,
on
a
monthly
basis,
to
make
sure
we
as
ux
we're
not
blocking
anyone
in
engineering
from
doing
any
work.
So
this
is
kind
of
like
more
fyi
items,
just
adding
a
little
bit
more
visibility
to
the
ux
issues
in
planning.
If
any
questions,
let
me
know
muting
myself,
because
there
is
a
car.
A
A
D
Yeah,
I
think
so
dmitry
reed-
I
think
you
have
been
discussing
this
already,
so
should
be
nothing
new,
but
just
wanted
to
kind
of
align
that
we're
by
the
way,
with
dimitri's
help
we're
working
to
bring
the
same
nci
and
actually
release
management
will
be
also
similar.
So
it
sounds
like
we're
even
more
or
less
like
going
to
be
using
similar
practices
between
piano
and
ux
in
the
stage
groups
in
the
release
and
purify,
which
is
cool.
D
A
All
right,
I
can
look
into
the
separate
section
for
research
to
highlight
a
little
bit
more
but
like.