►
From YouTube: Progressive Delivery UX/PM meeting 2020-06-02
Description
Meeting to improve alignment between Product Management and UX for progressive Delivery
A
It's
the
ada
okr,
it's
this
thread
to
read
through
there
was
this
process
lined
out
that
we
have
changed
we're
now,
at
this
step,
setup
prioritization
session
with
your
pm
and
em
to
go
over
the
collected
issues
for
your
stage
group
from
table
above
before.
A
A
B
B
What
I
think
our
first
step
would
be
is
to
have
the
engineering
team
weigh
them
because,
as
I
said
at
the
moment,
they're
not
ready
for
dev.
So
I
think
that
would
be
our
first
step.
So
I
I
think,
if
you
or
if
you
want
to
do
this
together,
it's
also
okay,
let's
choose
like
the
top
three
and
add
them
to
the
engineering
needs
weight
and,
according
to
the
weight
that
they
give
and
the
capacity
that
we
have
for
the
next
milestones
we
can
see
if
we
can
push
something.
A
Yeah,
so
that
that
seems
like
a
good
idea
in
order
to
get
those
to
those
top
three.
We
do
need
to
have
a
discussion,
though,.
B
B
A
B
But
to
be
to
be
fair
since
we're
at
the
end
of
3
13
1,
we
need
to
add,
we
would
add
this
to
the
needs
weight
issue
to
13
2..
So
probably
we
wouldn't
have
something
in
this
immediate
quarter.
Maybe
maybe
we'll
have
like
one
issue,
but
we
can
start
thinking
about
it
for
thirteen
three
and.
B
A
Yeah
I'll
I'll
relate
this
information
back
and
we'll.
Let's
see
how
far
we
can
get,
any
progress
is
better
than
no
progress
right,
yeah
and
then
I
see
your
yours.
Your
point
is
next
one.
A
B
Okay,
so
what
I
did
today
was
I
we
had
a
whole
discussion
about
recruiting
new
people
for
spinnaker,
and
I
was
really
really
pleasantly
surprised
about
the
fact
that
we
actually
have
a
lot
of
responses
that
are
good
responses.
Last
time
we
talked
about
this,
there
were
four
respondents
that
said,
yes,
they
were
using
spinnaker
and
now
we're
at
a
22..
B
So
that's
a
big
difference
and
when
I
went
through
the
issues
and
I
kind
of
consolidated
them,
I
found
a
really
really
interesting
data.
So,
first
of
all
lori,
I
saw
your
comments
and
I
will
create
a
discussion
guide.
B
Okay,
I
do
think
it's
it's
worthwhile
to
continue
exploring
and
actually
getting
like
a
conversation
with
these
people
and
not
only
a
survey,
probably
not
one
yeah.
B
Because
it
was
really
interesting
david,
so
I
I
put
here
like
a
bunch
of
the
insights
that
I
found,
which
was
interesting
so
like
in
the
terms
of
the
persona
we
have
like
a
clears
persona
that
are
using
it.
It's
devops
engineers
or
site
reliability,
engineer
which
I
don't
think
we
have
this
persona
in
in
gitlab,
but.
B
Most
of
the
respondents
deploy
to
the
production
multiple
times
a
week.
The
majority
of
the
respondents
are
using
rolling
upgrades
as
a
deployment
strategy,
which
is
really
interesting
because
we're
putting
a
lot
of
effort
in
that
regardless
to
this
spinnaker
research.
So
it
definitely
gives
you
validation
that
we're
on
the
right
track.
B
B
Majority
of
respondents
applied
to
a
single
public
cloud,
so
we're
at
the
moment
doing
native
deployment
to
cloud.
The
next
point
was
that
the
vast
majority
is
using
aws,
so
it
was
a
good
choice
to
choose
aws
first
and
regarding
the
previous
question,
it's
really
good
to
know
because
there's
a
big
trend
now
to
deploy
to
multi-clouds
and
it
doesn't
look
like
that's
the
case,
so
I
think
it's
okay
to
hold
off
on
that.
B
Rollbacks
are
not
a
pain
point,
so
when
I
was
looking
at
what
we
could
do
to
win
over
users
that
are
using
spinnaker
or
not
gitlab,
it
doesn't
look
like
that's
a
good
place
to
start,
because
it
looks
like
most
of
the
time
people
are
not
dealing
with
rollbacks.
Maybe
there's
like
one
respondent.
That
said,
they
were
using
it
up
to
20,
but
the
best
the
the
majority
of
the
people
are
not
also
it's
pretty
easy
to
find
out
the
root
cause
of
the
problem.
B
So
that's
not
something
we
should
invest
in
majority
of
the
groups
on
this
have
another
way
automated
way
to
verify
successful
deployment,
which
is
interesting
both
in
terms
of
what
we've
found
out
in
aws
and
also
what
we're
doing
about
the
post-deployment
monitoring
in
terms
of
rollbacks.
There's
a
need
to
support
both
manual
and
automatic
workflows,
which
is
also
something
that
came
up
on
the
post-deployment
monitoring
research,
which
is
that
there's
really
no
cut
clear
way
and
you
can
see
it's
pretty
much
distributed
evenly.
B
Of
effort
that
we're
doing
now
regarding
load,
balancers
and
advanced
deployments-
and
it
looks
like
the
vast
majority-
are
using
load
balancers.
So
that
was
a
validation
for
me
that
we're
also
investing
the
right
effort
in
that
majority
of
respondents
are
using
a
config
file
to
manage
their
deployment
scaling.
So
this
is
very
kubernetes
oriented.
B
This
is
more
interesting
for
jackie,
but
still
interesting
to
know
that
majority
of
respondents
have
deployed
freezes.
So
that's
the
time
where
you
can't
deploy-
and
I
also
share
this
information
with
jackie
and
what
we
call
white
periods,
so
certain
dates
that
you're
allowed
to
deploy
on.
So
that's
that
was
interesting.
B
This
is
an
opportunity
that
I
found,
so
the
majority
of
respondents
said
that
they
leave
the
spinnaker
app
and
go
to
the
cloud
provider
dashboard
multiple
times
a
day
and
people
hate
that
they
like
to
stay
inside
the
same
tool
and
get
whatever
information
that
they
can
and
when,
when
we
were
doing
the
validation
for
aws
deployments
and
most
of
the
people
there
that
responded
were
using
jenkins.
B
B
Most
of
the
users
wanted
an
integration
between
gitlab
and
spinnaker
so
that
spinnaker
could
trigger
a
pipeline.
So
that's
interesting
feedback.
B
Spinnaker
firewalls
is
something
that
they
write
a
lot
of
blogs
about,
and
it's
like
a
main
feature,
but
it
looks
like
no
one,
not
really.
The
the
majority
of
people
are
not
using
that
feature.
So
I
don't
really
think
that
we
need
to
deal
with
feature
parity
at
the
moment
with
this
and
then
there's
a
bunch
of
text
here
of
why
people
chose
spinnaker
over
gitlab,
which
is
really
really
interesting
and
which
features
would
we
need
to
get
to
implement
in
google
cd
in
order
for
people
to
leave
spanker
and
use
our
solution?
B
So
it's
very
complementary
to
the
question
above
and
it's
an
interesting,
read
and
then
the
last
question,
which
is
also
very
interesting
for
all
ops.
Not
only
release
is
ranking
of
spinnaker
features
from
one
of
from
one
to
ten,
where
one
is
the
highest
and
it
was
interesting
to
see
like
deployment
strategies
which
we're
heavily
invested
in
in
progressive
delivery.
It's
like
the
top
item,
is
number
one,
so
that
kind
of
gave
me
a
validation
that
we're
on
the
right
track
again.
B
So
take
a
look
at
this
document.
I
thought
it
was
really.
B
No,
I
just
finished.
I
just
finished
it
finished,
making
all
these
graphs
like
half
an
hour
ago.
It
took
me
a
long
time.
Okay,.
C
Well,
I
will
say
this
is
what
20
22
people
and
it's
a
good
data
set
to
start
asking
qualitative
questions
from
to
try
to
figure
out
like
why
aren't
they
using
that
spinnaker
firewall?
If
they're,
not,
why
not
those
kinds
of
questions?
So
I
think
this
is
really
great.
I
just
caution
against
making
broader
broader
decisions
and
applying
it
to
bigger
bigger
spots
of
people
yeah
when
you're
spending
two
people.
B
Yeah
but
overall
I
thought
it
was
really
good
data,
because
before
I
can
use
anything-
and
here
I
could
really.
C
And
do
you
want
rupert
and
emily
to
continue
to
try
to
find
people
for
our
survey,
or
are
we
kind
of
done
with
the
survey
at
this
point?
No,
I.
B
Think
that
I
think
this
is
good
enough
data
and
now,
if
I
actually
pursue
real
interviews,
I
think
we'll
have
enough
to
go
on.
A
It
is
would
wonder
like
what
they
say,
for
example,
with
because
spinnaker
is
well
organized,
requires
less
effort
like
in
what
way,
but
also
yeah,
there's
there's
some
other
questions
given
in
there.
A
It's
funny
that
they
say
like
yeah,
because
netflix
is
that
works
well.
B
You
that
when
you
have
a
good
reputation,
people
follow
you.
It's
actually
a
great
response.
I
thought
yeah,
it's
a
copy
paste.
B
And
when
you
think
about
it,
netflix
is
really
amazing.
They
have
thousands
of
deployments
a
day
and
they
actively
experiment
with
their
users,
segmented
users
and
they
roll
out
later
like
if
they
do
really
really
cutting
edge.
B
B
So
the
next
steps
is
I'm
supposed
to
reach
out
and
get
some
recruitments
for
actual
interviews
lori.
I
did
ask
rupert,
I'm
not
sure
how
to
do.
I
just
send
an
email.
Do
we
have
a
template.
C
B
B
A
Yeah
so
like
will
you
start
on
a
discussion
guide
for
those
interviews
or
it
says
already
done.
A
Sounds
good
yeah
I
would
love
to
be
included
on
the
discussion
guide.
Get
some
get
some
questions
in
there
and
let's
go
from.
There
sounds
good.
B
A
Then,
for
now
nothing
more
for
me,
but
anybody
else
has
any
questions.
Otherwise,
I'll
give
some
time
back.
B
I'm
good,
no,
the
only
thing
is:
I'm
still
waiting
for
two
replacements
for
the
post
deployment,
monitoring
people
so
I'll
bug,
emily
about
that
or.
A
C
B
A
Then
okay
sounds
good.
Thank
you
so
much
and
see
you
very
soon.