►
From YouTube: Release Management UX/PM Sync (24 August 2020)
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
I
love
it
all
right.
Okay,
hi
on,
I
think
the
first
item
on
the
agenda.
C
So
my
first
item
here
is
about
the
discussion
with
jackie
and
I
had
this
week,
ux
coverage
because
I'm
going
out
of
office
for
I
calculated
15
days,
that's
quite
a
lot
and
we
discussed
about
the
cic
director
dashboard
and
that
prototyping
will
be
reassigned
to
juan
during
this
period,
and
I
asked
if
not,
it
has
any
concerns
related
to
that.
So,
if
you
want
to
voice
them.
A
Yeah,
I
think
that
makes
sense.
We
discussed
this
with
jackie
a
bit
already
last
week
and
also
I
know
that
juan
was
very
open,
helping
other
stage
groups
in
ci
cd
and
also.
I
know
that
he's
super
fast
and
prototyping,
like
he's
a
guru
of
prototypes,
so
I
think
he's
really
a
suitable
person
here
and
also
he
had
acquired
some
experience
with
doing
dashboards
and
reporting
for
testing.
So
by
all
of
the
means,
I
think
he's
great
replacement
here
so
yeah,
I'm
totally
awkward.
A
That
question
that
I
had,
if
there
is
anything
that
I
can
cut,
had
to
say
catch
up
with
in
order
to
make
sure
that,
if
juan
has
any
questions,
I
can
help
we
have
jackie
still,
but
just
asking.
If
there
is
anything
that
I
can
be
supporting
you
with.
C
Yeah,
I
think
it's
best
to
maybe
we
can
do
a
like
a
tough
on
our
sink
just
to
go
over
it,
and
I
can
also
talk
to
him
a
little
bit
about
yeah
background
and
the
prototyping,
because
we
have
some
things
on
figma
and
then
yeah.
We
can
report
it.
A
Yeah
you
mean
also
inviting
juan
or
just
like
me
and
you
and
then
as
well.
I
would
love
to
join
that
yeah
yeah
yeah.
That
would
be
helpful.
B
And
I'm
not
quite
sure,
also
with
the
new
product
okr
and
push
to
focus
on
existing
usage
and
usage.
I
don't
know
why
I
just
slurred
my
words
there.
I
promise
I
haven't
been
drinking.
The
existing
usage
of
our
of
our
features
like
this
would
be
a
whole
new
offering
for
the
cicd
section,
so
you
know,
as
we
start
to
go
down
this
route
of
prototyping
and
investing
in
this
new
feature.
B
A
Do
you
mean
jackie
that
we
won't
have
the
components
existing
for
whatever
we're
going
to
come
up
with?
Probably-
and
this
will
go
against
the
ocr
that
we
have
like
100
of
new
features
created
in
q3
should
be
using
the
pajamas.
B
More
like
the,
we
should
only
be
prioritizing
usability
of
existing
features
from
a
product
standpoint.
There's
this
focus
from
a
noop
and
scott
that
product
managers
had
to
acknowledge
that
we're
going
to
be
focusing
on
the
usability
of
existing
features.
This
would
be
a
new
feature
addition,
and
it
is
also
super
cross-functional
between
verify
and
release.
B
So
we
are
able
to
like.
I
don't
know
if
we'll
end
up
prioritizing
the
cicd
director
dashboard,
given
the
new
the
renewed
focus
on
the
usability
of
existing
features.
I
see
yeah.
A
Yeah,
I
guess
yeah.
This
is
where
we
probably
are
looking
up
to
you,
jackie,
to
give
advice
here
and
then
I
will
follow.
I
guess.
B
Definitely,
I
think
it's
worth
still
prototyping
with
one,
but
as
we
start
to
get
down
like
the
actual
build
phase,
it'll
eventually
have
to
get
prioritized
between
verify
and
release
from
a
shipment
of
features,
so
that
turnaround
time
might
not
be
as
fast
as
we
would
hope
it
to
be.
C
Yeah,
I
think
here's
an
opportunity
for
us
to
have
a
conversation
around
design
for
the
dashboard.
So
even
if
we
don't
prioritize
this
now,
I
think
it's
yeah
half
an
hour.
We
can
quickly
go
over
it
one
and
then,
by
the
time
we
immerse
things,
there's
more
common
knowledge.
C
And
then
quickly,
I'm
just
gonna
invite
juana
dimitri
to
the
thing
or
one
slash
dimitri.
I
think
it
is
already
participating
in
some
of
the
thinking
sessions,
but
whoever's
going
for
me
just
a
heads
up
and
when
I
add
them
to
the
other
think
big
sessions,
the
other
team
calls.
I
don't
think
it's
it's
worth
causing
too
many
calls.
A
Yeah,
I
guess
we
may
wanna
make
this
well
known
to
juan
as
well
like
hey.
We
have
those
meetings,
just
maybe
he
wants
to
chat
the
notes
afterwards,
I'm
not
sure
if
that's
a
good
idea
to
for
him
to
join
every
meeting
but
like
yeah.
Maybe
he
wants
to
be
up
today
or
just
have
the
opportunity
to
have
all
these
goals
cincinnati.
B
Is
optional
I
can,
if
nadia,
do
you
want
to
like
flag
him
to
let
him
know
that
he'll
be
added
to
the
release,
management
meetings
and
they're
not
required,
and
let
me
know
I
don't
want
him
to
just
to
get
added
to
meetings
and
be
like
jackie.
Why
are
you
adding
with
all
these
meetings.
C
And
then
just
a
heads
up
that
immediately
will
be
out
of
office
as
well,
while
I'm
out
of
office.
That's
why
he's
not
covering
for
me
and
then
next
topic
is
to
jackie.
B
So
I
finally
finished
I
need
to
go
back
and
transcribe
the
feedback
that
I
put
in
dovetail
as
user
insights
inside
of
the
uxr
repository,
because
I
had
to
like
look
through
the
documentation
in
the
google
doc
and
the
handbook,
and
it
doesn't
look
like
research-
has
updated
the
handbook
yet
for
this
new
protocol
or
if
they
have.
I
don't
have
the
handbook
link
for
it.
B
So
I
just
need
to
create
those
insights
in
the
repository,
but
this
this
opportunity
canvas,
I
just
chatted
here
and
I'll
drop
it
in
our
agenda
is
the
justification
for
our
environment's
dashboard
redesign.
So
this
one
is
really
aligned
with
all
of
the
okrs
insofar
as
we're
instrumenting
pajamas
in
it.
We
are
focusing
on
usability
of
an
existing
feature
set
and
we're
driving
paid
smell
with
the
dashboard.
B
So
I
think
that
this
will
be
a
really
great
opportunity
for
us
to
focus
on
driving
tier
value
in
the
release
management
stage,
while
also
tackling
some
of
the
things
that
we
get
really
dinged
on
from
an
analyst
perspective
and
also
supporting
legacy
deployments,
which
is
a
weakness
that
we
have
in
gitlab,
so
really
excited
for
this
opportunity,
canvas
presenting
it
on
tuesday
to
a
new
and
hopefully
we'll
get
the
stamp
of
approval
to
start
working
on
this
to
redesign.
B
I
think
it's
going
to
be
like
five
milestones
worth
of
effort,
because
we
have
the
pagination
that
we're
going
to
deliver,
which
is
a
really
big
piece
of
scope.
Then
we
have
filtering
and
sorting,
and
then
we
have
changing
the
interactions
of
adding
an
environment
versus
a
project
to
the
dashboard
and
then
adding
a
heat
map
widget
and
then
creating
templates
for
the
environment's
dashboard.
B
So
those
are
all
like
super
huge.
Both
back
and
front
end
features
that
we'll
be
intensively
developing.
So
I
could
see
us
dedicating
teammates
to
that
after
we
get
the
designs
finalized.
So
over
the
next
two
milestones
three
milestones
ian
and
I
will
work
on
the
designs
for
the
work
that
isn't
already
designed
and
then
we'll
put
it
for
the
engineers
to
deliver.
The
engineers
are
going
to
be
subsequently
delivering
release,
notes,
features
between
now
and
13.7,
while
hyun
and
I
are
working
on
designs
for
the
environments
dashboard.
C
B
C
Because
there's
like
there's
a
sheet
profile
with
a
just
a
list
of
links
for
the
opportunity
canvases
for
everything,
but
I
don't
think
it's
the
best
way
to
organize
that.
So.
B
C
So
I
just
had
to
hear
my
weekly
plan,
my
personal
issue
and
just
went
up.
I
have
quite
an
influx
of
merchandise
since
last
week
because
he's
out
of
office
and
I'm
covering
for
him,
but
also
a
lot
of
pajamas
and
the
migration
things
to
review.
So
these
are
very
time
consuming
tasks.
So
just
a
heads
up
in
case
yeah,
I'm
not
super
responsive.
It's
because
gdk
is
a
pain,
but
then
I'm
following
the
top
bottom
of
the
stash
order
or
the
new
ux
review.
B
B
We
advise
do
you
advise
that
the
skeleton
loader
should
be
a
pretty
low
lift.
So
that's
why
we
have
that
one
above
the
13.6
feature,
and
then
I
have
expand
environments
per
project
on
the
environments
dashboard.
My
expectation
here
is
that
this
might
be
the
start
of
our
of
our
redesign
effort,
given
that
we
will
be.
This
is
the
second
part
of
pagination.
B
The
first
part
of
pagination
was
adding
more
environments
or
more
projects.
This
is
adding
more
environments
per
project,
so
it
would
be
interesting
to
to
prioritize
this
over
something
like
sorting
releases
by
date,
name
and
milestones.
I
also
think
that
sorting
releases
by
date,
name
and
milestones-
has
the
pajamas
spec
on
it
already.
So
this
is
more
like
in
your
cue.
So
if
jake
has
feedback
while
he's
working
on
on
it,
he
can
ping.
You.
A
C
B
And
then
the
last
thing
I
have
on
here
is
about
just
the
cicd
dashboard.
We
briefly
talked
about
it
before.
I
just
don't
know
if,
given
our
environments,
dashboard
redesign
release,
notes
with
dog
fooding
and
all
the
other
work
that
we're
having
to
do
between
vacations
and
that
stuff
that
we'll
be
able
to
take
on
the
cicd
dashboard
effort.
So
I
don't
think
it's
that
big
of
a
of
a
of
a
loss.
A
So
you
are
mentioning
jackie
due
to
the
like
the
the
product
direction
that
we
just
discussed
earlier
and
also
due
to
like
the
high
workload
and
like
some
take
it
taking
time
off,
etc,
etc.
So,
all
of
those
stuff.
B
Well,
just
all
of
these
things,
it's
just
poor
timing
for
that,
for
that
feature
set,
I
think
yeah.
A
I
see
yeah
anything
that
we
could
make
sure
that
we
don't
like
let
this
completely
fall
and
like
what
we
just
discussed
that
we're
gonna
at
least
try
to
do
the
prototypes
with
one.
Just
like
you
said
in
the
beginning,
right
yep.
C
C
B
B
My
expectation
is
that
this
is
effective
september
1st,
so
this
week
I
have
a
bunch
of
stuff
covered
so
that
I
can
help
to
help
strive
and
support.
Those
conversations
here
is
the
this
one.
So,
with
the
get
lab
china
project
stella,
the
chief
of
staff
is
going
on
office.
B
My
hat
was
thrown
in
the
ring
to
take
on
this
from
a
program
management
standpoint,
and
I
accepted
so.
I
will
be
the
program
manager
for
our
company's
initiative
to
create
a
china
entity
for
git
lab,
and
this
project
will
last
until
january
1st-
and
she
said
it
was
only
going
to
be
like
a
15
hour
per
week,
commitment,
and
that
is
exactly
like
how
much
time
I
spend
interviewing
customers
on
average.
B
B
If
you
wanted
to
run
them
by
customers,
I
think
we
would
need
to
create
like
a
ux
research,
recruiting
request
and
go
through
that
way
to
source
interviews.
And
of
course
I
can
try
to
like
work
with
our
internal
account
teams
to
find
people.
But
I
don't
I
don't.
I
don't
see
having
a
bunch
of
free
time
to
drive
interviews
with
customers
when
this
project
starts
picking
up,
but
we
can
play
it
by
ear.
I
just
wanted
to
flag
you
for
that.
B
C
And
then
for
the
which
ones
that
we
have
introduced
this
week
for
the
maturity
scorecard
you're
already,
including
like
in
your
until
september.
First
right.
B
Yeah
my
goal
is
to
have
all
of
our
interviews
for
the
maturity
scorecard
done
by
august
31st.
We
currently
have
five
scheduled
so
hopefully
we'll
be
able
to
like
be
line
that
maturity
scorecard
and
grade
it
and
then
move
secrets
management,
because
it's
due
in
october.
C
Okay,
I
just
want
to
see
quickly
here
about
the
maturity
scorecard.
B
Since
it's
a
minimal
move,
we
only
have
to
interview
internal
candidates
and
we
need
five
of
them
for
each
persona.
The
persona
that
the
jwt
is
built
for
is
for
software
developer.
So
we're
going
to
be
focusing
on
the
solution.
Architects,
here
at
gitlab,
who
are
software
developers
for
selling
our
product.
C
Do
you
want
to
kind
of
like
define
which
tasks
we're
going
to
share,
because
I
know
that
you
already
put
it
together
in
the
document,
so
I.
B
Just
want
to
align
what
do
you
want
to
line
on
sorry,
it's
already
written
down
like
we
have
the
scenario
built
out
like
scenario,
one
no.
C
I
need
a
task
like
because
you
have
to
document
the
things
and
write
all
the
the
insights
and
organize
the
data,
so
I
just
want
to
align
with.
B
You,
oh,
like
the
data,
the
data
part
yeah.
So
after
we
do
the
interview
we'll
have
all
of
the
the
grading
score
and
my
intent
is
just
aggregate
those
scores
and
update
them
per
hour
for
the
process.
So
it
doesn't
seem
like.
B
Like
document
success,
failure
flows
of
your
job
to
be
job
to
be
done,
scenarios
we
do
need
to
define
like
the
flow.
B
Yeah
because
it
looks
like
ux
light
scores,
success,
failure,
time
on
task
and
error
rate.
B
C
B
I've
talked
to
all
of
them
because
most
of
them
have
already
set
this
up
before
so
we're
giving
them
like.
The
scenario
that
I
have
written
down
here
is
your
software
developer.
Your
boss
has
given
you
a
link
to
gitlab's
new
documentation
for
setting
up
hashicorp
vault
show
us
how
you
would
set
up
the
jwt.
C
B
B
Okay
and
then
yeah,
so
I
think
when
we
take
notes,
we
just
need
to
make
sure
that
we
we
we
just
follow
through
on,
like
the
success
failures
and
I'm
not
quite
sure
where
exactly
we
document
these
other
than
in
dovetail,
it
doesn't
look
like
there's
other
instructions.
As
far
as
like
we
need
to
create
another
repository
for
user
insights
on
success
failure.
It
just
looks
like
we're
doing
it
in
dovetail.
C
C
He's
doing
it
so
helping
him,
because
if
someone
found
a,
I
don't
know
easy
process,
but
I
think
adoption
will
be
enough,
especially
that
we
have
this.
We
don't
have
a
flexible
question,
so
it's
not.
B
Yeah,
I
I
tried
to
really
like
hone
in
on
the
primary
job
to
be
done
here.
Looking
at
like
what
are
the
expectations
for
the
minimal
move
and
like
that
is
the
that
is
exactly
what
the
jdwt
is
for.
So
I
think
it
should
be
pretty
straightforward
and
lean.
B
Obviously,
though,
as
we
start
to
move
secrets,
management
to
complete
those
are
going
to
be
really
big
like
we'll
have
a
really
long
series
of
validations
and
probably
like
15,
people
will
need
to
interview
for
that.
C
Now
do
we
already
have
laurie.
B
B
Yes,
I
already
pinged
her
on
it
and
she
said
I
actually
asked
her.
Can
you
review
the
these
jobs
to
be
done
and
give
me
feedback
and
she's
like?
Oh,
they
look
great
to
me.
What
questions
do
you
have
and
I'm
like
awesome
all
right.
I
guess
that's
good
enough.