►
From YouTube: Deployment Direction Milestone Discussion
Description
Part of the monthly Configure, Release, Monitor PM discussion
B
Here
we
have
the
direction.
How
are
we
making
progress?
Are
we
making
progress?
It
feels
like
we're
not
or
you
know
we
don't
know
where
we
are
where
we
stand,
even
though
we
know
teams
are
working,
and
so
I
think
I
think
because
of
that-
and
I
think
just
also
for
now
that
we're
executing
it
could
be
a
good
way.
B
You
know
we
should
spend
some
time
thinking
about
what
are
the
key
milestones
that
we
want
to
highlight
and
drive
towards
between
now,
and
you
know
a
year
from
now,
maybe
and
beyond,
and
and
then
share
that
with
the
rest
of
the
team,
with
the
rest
of
the
org
to
show
progress,
and
then
I
have
a
few
like
just
a
few
ideas
of
what
those
milestones
could
look
like,
but
I
wanted
to
open
it
up.
I
wanted
to
raise
this
and
then
brainstorm
together
and
figure
out
what
those
could
look
like.
B
B
Certain
kpis
smile
or
you
know,
monthly,
active
users
of
different
stages
or
different
features.
It
could
be
category
maturity,
upgrades
for
certain
categories
that
we're
working
on.
It
could
be
that
maybe
we
highlight
specific
features
or
epics
that
you
know
that
are
key
to
the
deployment
direction,
or
maybe
a
mix
of
those
things
but
yeah.
C
That
would
be
awesome
if
you
can
come
up
with
something,
but
for
that
we
would
need
to
have
just
a
clear
goal
that
we
want
to
reach
because
right
now,
what?
What
comes
to
my
mind
is
that
even
we
don't
even
have
a
clear
idea
of
the
expected
user
flow
at
the
end,
so
we
can't
even
validate
even
in
terms
of
a
ux
maturity
scorecard
that
where
how
do
we?
C
C
A
We
kind
of
have
documented
some
of
these.
This
never
paid
attention
to
the
goals
and
frankly,
execution
has
been
the
start
of
it
has
been
really
slow,
so
we
couldn't
make
as
much
progress
as
possible.
So
maybe
we
can
just
kind
of
bring
starting
with
brainstorm
of
category
maturity
and
specific
I
mean
maybe
not
even
brainstorm
just
list
out
some
of
the
things
we
see
category
maturity
and
specific
epic
completion
as
part
of
this
exercise
now,
but
before
we
do
that.
A
A
Because,
given
maybe
it's
not
useful,
I'm
thinking
about
the
fact
that
we,
with
our
existing
people,
we've
been
just
keeping
the
lights
on
yeah.
Releasing
particulars
like
we
spent
most
of
the
end
of
last
financial
year,
trying
to
fix
pages
right
yeah
that
we
do
much
else
not
really
spend
q1
half
of
it.
Trying
to
onboard.
A
B
B
A
B
B
A
A
B
A
B
B
B
B
B
A
B
B
I'll
write
this,
but
then
we
could
debate
it.
I
was
going
to
say
like
well
like
well
connected
like
with
the
rest
of
the
tool
right,
I
think
that's
a
differentiator
like
deployments,
make
sense
in
the
with,
along
with
all
the
other
stuff
we're
doing
in
gitlab.
I
don't
know,
I
don't
write
that,
but
like
releases
and
environments
are
connected
and
like
verification,
it's
not
all
these
disparate
pieces,
like
I
guess
well
connected-
helps
facility.
B
A
B
A
B
A
B
A
B
B
A
A
Good
yeah,
but
it
doesn't
count
like,
for
example,
the
number
of
times
the
the
agent
is
syncing.
What's
it
get
versus,
what's
in
the
cluster,
like
you
may
get
that
to
measure
and
move
into
deployment,
yeah
kind
of
deployments,
yeah
that
we
get
really
close
and
then
we
add,
like
oh,
the
number
of
times,
gets
through
the
tunnel
to
do
something.
A
Probably
consider
that
a
deployment
yeah,
actually,
if
we
add
a
few
of
the
bigger
things
we
may
be
right
there-
maybe
that
might
not
be
true
and
then
we
can
have
a
chart,
as
is
the
number
of
deployments,
went
from
300
000
per
day
or
whatever
number
is
to
2.5
million,
or
something
like
that.
That'd
be
amazing.
B
We
kind
of
moved
away,
I
think
in
one
of
the
pi
meetings,
maybe
two
two
of
them
ago,
but
like
the
golden
journey
metric,
like
the
adoption
of
our
stages,
I
think
that's
probably
a
good
that
could
be
a
good
indicator
of
our
bill.
You
know
our
progress
towards
making
deployments
like
more
better
yeah,
I
guess
just
better
or
more
of
our
customers
adopting
it
too
right
and
all
all
these
are
correlated
anyway,
the
number
of
deployments,
and
but
that's
probably,
that
could
be
another
good
one
to
think
about
and
consider
yeah
yeah.
A
B
A
A
B
B
Like
like,
again
easy
to
say,
sort
of
like
like
kind
of
like
aha
magic,
like
aha
moments
or
like
just
even
the
lighters
right,
I
think
those
are.
I
think
that
could
be
another
approach,
that's
sort
of
like
products
code
of
ideas,
but
I
think
it's
similar
right,
like
you
know
what
makes
it
sort
of
magical
in
our
tool
versus
another.
A
B
Yeah
yeah,
I
think
you'd
want
them
to
feel
sort
of
yeah,
maybe
a
mix
of
like
surprise
and
some
sort
of
surprise
and
joy,
and
I
guess
it
depends
on
what
we're
talking
about
but
like
oh,
that
was
really
cool
like
I
think
those
are
sort
of
all
the
feelings
you
went
on
to
evoke
when
when
using
something
yeah
or
that
it's
like,
or
it's
like
it's
special
or
unique.
Maybe
those
are
another
thing
and
something
something
that's
different.
B
B
I
feel
like
it's
still
for
me.
I
feel
like
good,
aha
moments
for
git
lab
or
like
when
we
can,
when
really
when
I,
when
we
can
connect
stuff
right
like
there's
like
a
hypothetical
or
a
future
example
like
we
have
continuous
verification
which
discovered
a
bug
which
created
an
issue
right.
That's
that's
like
that's
magical
almost.