►
From YouTube: Progressive Delivery UX/PM meeting 2020-06-02
Description
Meeting to improve alignment between Product Management and UX for progressive Delivery
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
B
B
A
B
B
A
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
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
B
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
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.