►
From YouTube: Progressive Delivery UX/PM meeting 2020-04-28
Description
Meeting to improve alignment between Product Management and UX for progressive Delivery
A
I
think
I
think
something
that
we're
missing
as
a
process,
and
maybe
also
documented
in
the
handbook,
is
that
some
of
the
user
research
effort
crosses
time
zones
and
it's
not
always
convenient
for
everyone,
and
we
talked
about
having
like
different
calendar
links
in
order
to
accommodate
different
time
zones,
and
I
think
that's
actually
a
really
good
idea.
I
mean
we're
all
part
of
this
research
effort.
A
It
shouldn't
fall
in
the
burden
of
one
person's
shoulders
and
especially
if
it
crosses
times
as
we
need
to
figure
out
how
we
can
help
each
other
yeah.
C
I
agree
with
you,
so
you
read
your
point:
is
that,
like
we
should
clearly
state
this
somewhere
that
you
know
that
we
are
helping
each
other,
the
team
to
cover
the
user
research
data
collection
across
the
time
zones.
We
should
not
like
make
it
problem
with
one
person.
C
And
what
do
you
mean
you
do
not
know
how
to
do
that
technically,
like.
A
C
A
C
B
All
right,
let's
jump
a
little
bit
to
the
beginning
of
the
the
meeting,
with
quite
a
few
things,
to
discuss
mostly
alignment,
and
then
I
have
a
few
other
tools
or
points
to
to
jump
into.
But
mostly
my
main
goal
with
this
meeting
is:
let
me
make
sure
that
I'm
aligned
with
with
you
or
it
on
the
things
that
I'm
busy
with
so
I've
put
in
here
some
links
for
the
13-0
planning
issue,
21
planning
issue.
B
I
noticed
as
well
that
some
of
the
issues
that
are
in
the
13.1
the
top
priority
deliverables
list
those
have
already
changed
in
terms
of
labeling.
So
I
think
that
list
needs
to
be
updated.
Is
that
correct.
B
Yeah
like,
for
example,
ad
ability
to
create
a
feature
flight
from
merch
request
that
has
been
a
release:
p3
label
and
release
p2.
While
it's
a
it's
a
it's
a
top
deliverable
for
13.1.
A
Yeah,
so
I
need
to
I
need
to
align
the
label.
First
of
all,
we
shouldn't
have
two
labels
and
that's
I
don't
know
some
mistake
that
I
did
along
the
way
and
and
if
it's
the
top
deliverable
it'll
be
a
p1,
the
thing
is,
I'm
a
little
bit.
I
think
this
specific
issue
issue
is
at
risk
because
all
the
feature
flag
things
are
like
coming
in
and
delay,
so
I'm
not
sure
it'll
stay
in
p
in
13-1.
A
Yeah,
I
mean
that's
what
I
would
like
to
see,
but
I'm
not
sure
that
the
team
will
be
able
to.
B
Okay
sounds
good
by
the
way
as
a
as
a
small
suggestion.
It
might
make
sense
for
us
to
create
the
to
make
the
release
priority
labels
into
scope
labels,
so
you
can
never
apply
more
than
one.
A
A
So
I
do
like
like
release
colon
p1
and
then
it'll
be
only
one.
B
Yes,
I
do
release
and
then
p
and
then
double
column
and
then
one
so
double
and
then
yay
double
call.
B
I
wonder
what
happens
by
the
way
with
issues
you've
applied,
both
labels,
to
which
you're
now
editing,
because
you
cannot
apply
both
at
the
same
time
or
will
they
stand
until
you
change
something,
and
then
it
will,
I
know,
fix
it
anyway.
It
doesn't
really
matter,
but
it
would
be
an
interesting
edge
case
side
question
for
the
boards
in
the
planning
issues
at
the
top
there's
always
the
boards
that
are
mentioned,
the
plan
board
the
schedule
board
the
billboard.
A
A
Board
nope:
I
have
only
one
board
that
I
look
at
and
it's
the
current
milestone
board
for
progressive
delivery,
which
changes
every
milestone
and
it
has
the
issues
that
are
in
the
current.
B
B
A
B
The
main
thing
I
want
to
get
to
these
are
the
issues
I
have
in
progress
right
now
on
my
board.
I
copied
them
here
for
easy
discussion
issues
in
reviews.
Those
are
the
things
that
are
currently
in
the
current
milestone
being
developed
and
then
issues
up
next
and
I
feel
like
I
might
be
missing
a
few
which
are
very
important
or
need
to
go
up
next.
As
soon
as
I'm
done,
I'm
figuring
out
my
availability
a
little
bit
still,
but
I'm
getting
there.
B
A
Yes,
so
one
of
them,
one
of
the
issues
here
is
the
post
deployment
monitoring,
which
I
created
into
an
epic
and
there's
some
activity
that
I
have
planned
for
13
1.
So
I
don't
think
right
now,
but
maybe
in
the
near
future,
go
into
it
because
some
of
them
need
some
ux
attention.
A
B
A
I've
been
dealing
with
it
since
I
joined
the
company
and
it's
something
that
the
community
is
is
really
looking
forward
to
and
waiting
for,
but
I
feel
like
I
don't
really
know
what
the
right
decision
to
implement
is
so
I
haven't
done
it
so
far
and
I've
been
annoying
the
community
because
I
keep
pushing
it
from
milestone
to
milestone
and
even
inside
the
issue.
There's
like
really
interesting
discussions.
This.
A
The
issue
that
I'm
talking
about
is
allow
allow
forked
pipelines
to
run
on
parent
project
and
there's
like
different
use
cases
that
that
users
want
for
this-
and
it
looks
like
this
issue-
is
going
to
give
birth
to
many
many
other
issues,
and
it
looks
like
there's
just
when
I
was
reading
through
it
today,
even
though
I've
been
answering
it
almost
every
week,
it
looks
like
there's
a
bunch
of
different
configurations
that
we're
gonna
have
to
have
there
and
I
don't
want
to
build
it
wrong
from
the
beginning
like
I
do
want
to
iterate
on
it.
A
B
Yeah
exactly
do
you
have
the
link
towards
that
issue
for
a
synaptic,
no.
B
B
C
B
Any
other
that
I,
that
you
want
me
to
work
on
asap.
A
So
I
told
you
about
the
postage
deployment
monitoring.
Let
me
get
that
link
too.
B
Just
one
minute,
yeah
I've
been
looking
into
that.
I
I
saw
you
were
gonna.
Take
on
the
research.
I
created
a
recruitment
issue,
but
we
would
need
to
work
on
the
on
the
getting
the
participants
questionnaire
out
there.
A
B
A
Yeah
we
have
items
coming
up
so
I'd
like
the
research
to
be
done
before.
A
Implementation,
the
reason
we
didn't
do
it
now
up
until
now
was
because
of
emily.
I
think
she
was
overloaded,
so
we
couldn't
recruit
before,
but
everything
has
been
in
place
and
just
waiting.
C
Yeah,
we
could
be
possibly
finding
the
ways
to
recruit
people
ourselves
if
emily
is
busy
yeah
just
like
using
our
own
powers
like
using
the
social
media
or
maybe
inviting
laurie
to
help
us
as
well.
So
let.
C
Yeah,
I
will
check
check
on
this
one
with
the
warrior,
as
well
with
laurie
and
emily.
B
In
terms
of
ad,
like
my
up
next
issue,
so
these
issues
will
flow
into
my
in
progress
as
soon
as
I
have
availability.
For
that,
I
have
add
confirmation
message
when
regenerating
feature
flag
instance
id
show,
error
rate
threshold
exceeded
on
deploy
board
and
then
as
well
allow
pipeline
to
work
on
four
projects.
A
A
Let
me
I
don't
know
how
to
phrase
this,
so
it's
not
necessarily
release
p1
issues
because
there's
different
reasons
why
we
want
to
push
so,
for
example,
the
message
on
the
feature
flag
is
a
rather
simple
issue
that
we
would
probably
give
the
new
front-end
engineer
that
is
joining
the
team,
so
I
want
to
make
sure
that
he
or
she
has
things
to
do
when
they
when
they
join
and-
and
you
know,
moves
some
of
our
stuff
forward.
A
A
Right,
the
truly
the
allow
for
pipelines
issue
is
the
most
popular
issue.
So
in
that
sense
it's
a
p1.
A
It
has
nothing
to
do
with
the
goals
of
the
team,
so
it's
not
in
the
quarterly
goals,
but
it's
still
something
that
I
want
to
make
progress
on,
and
I
think
that
if
we
don't
give
it
the
right
ux
attention
from
the
beginning
we're
going
to
have
a
large
ux
that
later.
So
I
think
it's
important
to
work
on.
B
Is
why
they're
yeah
yeah,
okay
yeah?
I
totally
get
what
you
say
now.
I
would
say
my
issues
up
next
would
should
align
with
your
thoughts
about
what's
going
to
be
in
next
releases
yeah.
So
what
we
want
to
do,
you
know
either
research
on
or
ideation,
or
we
need
to
have
like
a
lot
of
discussion
before
it's
going
to
be
in
a
good
state.
Like
I'm
I'm
saying
p1,
let
me
move
that.
B
Priority
to
give
ux
attention
asap,
that
is,
that
is
basically
my
up
next
issues
like
hey,
I'm
not
working
on
this
yet,
but
as
soon
as
I
have
availability,
I
need
to
work
on
this,
so
I'm
aligned
with
with
you
and
it's
going
to
be
done
before
we
even
get
to-
or
it's
right
done
when
you're
gonna
schedule
it
into
a
milestone.
B
All
right,
so
three
issues
in
that
right
now
are
any
issues
you
want
me
to
include
in
that
list
to
say
like
all
right,
hey
these!
These
are
the
ones.
I'd
say
like
hey,
give
those
your
most
attention
as
soon
as
you
can.
A
So
I
think,
what's
important
to
do
is
to
you
know,
work
with
the
q2
epic,
because
that's
static,
and
it
doesn't
really
change.
So
you
know
basically
what's
coming
up.
I
try
to
put
like
the
potential
milestone
in
there,
so
you
can
see
like
what's
urgent
and
what's
not-
and
this
is
like
the
guide
for
the
team
of
what
we're
gonna
focus
on.
So
I
think
this
is
a
really
good
one.
A
The
problem
is
that
a
lot
of
these
issues
tend
to
like
create
smaller
issues
that
are
not
necessarily
in
the
list,
and
sometimes
that
needs
attention,
but
the
majority
of
the
issues
are
are
actually
there
so
even
like
in
an
epic
level,
you
can
understand
like
what's
what
the
epic
that
we're
trying
to
to
see
and
and
try
to
understand
from
there
like.
What's
the
first
iteration
from
that,
I
usually
write
it
down
on
the
proposal.
B
Sounds
good
yeah
that
makes
sense
I'll
I'll
review
the
qt
q2
epic,
and
with
that
in
mind,
actually
put
it
up
later
here
as
well.
Like
hey,
are
we
still
in
line
in
terms
of
research
with
our
q2
goals,
we
got
the
a
b
testing
coming
up.
We
got
the
post
deployment
monitoring
coming
up.
A
A
A
Yeah,
so
the
idea
is,
we
have
cd.
Currently
it's
at
a
complete
level
and
the
next
move
in
maturity
is
supposed
to
be
to
lovable.
But
if
you
ask
me
objectively,
I
really
don't
think
we're
at
complete.
Even
so,
I
think
we
need
to
rebase
the
scorecard
based
on
user
input
and
not
our
own
I'll.
Give
you
two
examples
why
I
think
that
we're
not
a
complete,
so
the
quarterly
goals
at
the
moment
is
to
work
on
continuous
delivery.
A
In
two
aspects,
one
of
them
is
natively
deploying
to
the
cloud
and
the
second
one
is
increasing
our
advanced
deployments,
so
blue
green,
for
example,
or
everything
that
shinya's
working
on
right
now
for
the
load,
balancer
and
the
ingress
and
and
you've
seen
that
because
it's
in
your
list,
so
I
think
that
we
cannot
say
that
we're
complete
before
we
have.
You
know
numerous
kinds
of
advanced
deployments
and
have
the
ability
to
deploy
natively
to
the
cloud.
So
I
think
those
are
two
very
basic
features
that
we're
missing
at
the
moment.
C
Yeah,
maybe
just
like
a
a
question
here,
something
that
I
was
wondering
if
we
are
going
to
like
the
complete
maturity
for
cd.
It
also
sounds
like
a
quite
a
huge
piece
of
functionality
like
we
are
combining
a
lot
of
the
things
and
you
know
like.
I
was
just
brainstorming.
I
think
with
hyanna
earlier
and
we've
been
discussing
or
with.
C
It
was
marcel,
and
we
were
talking
about-
maybe
we
have
to
like
start
breaking
down
those
things
at
some
points
because,
like
it
will
also
be
very
hard
to
validate
the
maturity
like
with
only,
for
example,
like
our
maturity.
Scorecard
process
supports,
like
only
one
jobs
to
be
done,
and
it's
like
it's
impossible
to
select
one
job
to
be
done
to
represent
the
whole
cd
functionality.
For
that.
C
C
B
I'm
I'm
putting
it
as
my
up
next
for
now,
but
yeah.
There
will
be
a
lot
of
work
involved
with
that.
B
I
actually
got
something
lined
up
for
that
in
terms
of
like
jobs
to
be
done.
It
is
a
task
I've
set
myself
to
and
intending
to
finish
I'll
report
back
on
that
next
week.
If
I
can.
C
Into
like
I
made
this
point
here,
I'm
not
sure
if
you
want
to
add
something
else:
yeah,
alright
and
dimitri.
Let
me
know
if
so,
actually
I
probably
will
send
you
like
your
way,
some
of
the
information
on
the
jobs
to
be
done.
It's
not
it's
not
that,
like
it's
easy,
so
you
know
you
at
least
have
like
an
overview
on
what
to
expect
and
you.
C
We
are
not
being
afraid
of
this,
like
kind
of
like
of
some
unaware
dragon
yeah
and
I'm
here,
if
any
help
is
needed
with
that
process,
but
I
will
just
try
to
forward
something
easy
for
you
or
that
you
could
like
at
least,
let's
make
yourself
quickly
familiar
with
that.
A
B
All
right,
otherwise
any
deliverables
where
you
think
like
hey
this
needs
immediate
attention.
I
have
two
in
my
review.
One
of
them
has
to
do
for
me
so
I'll
look
into
that,
but
otherwise,
like
hey,
are
there
any
points
where
you
say
like
hey,
you
just
haven't
got
any
attention,
yet
you
really
need
to
look
into
that.
Otherwise
I
think
it's
fine.
B
And
there
was
another
one:
how
to
deploy
to
ecs
through
other
devops.
Those.
B
B
B
And
the
other
one
wasn't
a
edibility
to
this
p1,
but
it's
also
p1
what
is
done
this
dot
for
some
reason,
for
this
issue
wait
wait
a
second
I'm
gonna
post
it
here.
So
this
issue
is
add
ability
associate
feature
flag
with
contextual
issue
mike
is
assigned
to
that.
Still.
I
asked
him
to
review
all
his
assigned
issues
with
group
progressive
delivery,
so
he
will
get
to
that
somewhere
soon,
but
this
has
no
ux.
So
I
was
wondering:
do
you
know
what
that
is
about
because
it
seems
to
have
ux,
regardless
of
the
labeling.
A
I
think
he
he
added
mock-ups.
I'm
surprised
that
there
is.
A
B
A
B
C
So
it
sounds
like
we
are
discussing
quite
you
know
like
some
work
right
now
for
this
milestone
for
the
next
milestone.
I
just
want
to
make
sure
that
the
priorities
are
clear
to
you,
dimitri
and
you
kind
of
like
have
this
like
a
clear
linear
list
of
things
that
you
could.
C
You
know
like
go
through
to
make
sure
that
you
know
we
are
not
jumping
ahead
of
like
our
plans,
so
my
question
is
basically:
do
you
think,
like
the
yeah,
you
know
the
priorities
are
set
well
and
like
do
you,
you
know:
are
you
managing
well
with
the
amount
of
work
is
coming
any
help
on
that
needed
from
me.
B
So
I'd
say
for
now
I'm
quite
aligned
with
what
is
immediately
needed.
I
would
say:
like
hey,
I
wanna,
I
wanna
give
a
swing
at
this
a
b
testing
get
into
the
things
and
get
this
ball
rolling
and
only
say
two
weeks
from
now
I
wanna
start.
You
know
thinking
about
what
is
the
next
research
going
to
be
out
after
because
that's
the
only
thing
I
would
say
that
is
a
little
bit
unsure.
Yet
though
we
do
have
the
the
scorecard
coming
up.
B
B
I
would
say
so:
oh
yeah,
the
last
two
like
one
and
a
half
months.
For
sure,
though,
the
dag
issue
was
quite
big
and
it's
still
proven
to
be
like
some
involvement
there,
but
yeah
for
sure.
I
would
say
there's
for
sure
more
work
to
be
done
here
and
it's
also
more
clear
what
work
needs
to
be
done.
C
Awesome
sounds
good
yeah,
just
let
us
know
if
anything
will
be
coming
up
thanks.
B
B
All
right
I'll
put
the
other
topics
towards
next
week
and
then
thank
you
for
being
in
this
meeting.