►
From YouTube: Release Management PM/UX Weekly
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).
A
A
I
see
that
you
have
the
first
item
under
general.
Dashboard
updates.
B
Yeah
I
was
watching
the
the
recording,
but
I
just
wanted
to.
Oh
you
added
a
lot
of
items
here.
Just
wanted
to
hear
from
you.
It
was
like
the
final
decisions
for
the
direction
and
how
we're
going
to
prioritize
it.
Let's
see
if
you
can
yeah
vocalize
some
of
these
comments.
A
So
in
the
epic
we've
we
got
together
ori
and
I
and
we
decided
that
there's
a
couple
of
different
approaches
that
we
can
take
here.
I
think
that
the
first
nbc
will
be
creating
a
space
under
analytics
at
the
group
level
called
cicd
and
then
aggregating
the
existing
project,
metrics
that
are
in
the
cicd
analytics
page
to
the
group
level.
So
it's
pretty
much
copy
pasting.
The
exact
same
experience
that
we
have
at
the
project
up
to
the
group,
I'm
targeting
13.7
for
that.
So
we'll
be
designing
that
in
13.6.
A
My
hope
is
that
it's
lightweight,
because
it's
really
just
taking
the
exact
same
object
and
moving
it
up
to
the
group
level
longer
term.
We
have
aggregation
of
metrics
in
the
back
end,
so
we
have
one
of
those
scheduled
for
releases
and
deployments.
So
that's
scheduled
in
13.6,
I
believe
and
then
creating
widgets.
A
So
oriet
is
going
to
take
two
of
the
metrics
and
it
will
take
the
other
two
of
the
metrics
and
we'll
be
landing
them
on
that
group.
Cicd
analytics
page,
and
the
hope
is
that
by
separating
straight
down
the
middle
between
metrics,
we
won't
be
stepping
on
each
other's
toes
and
we
can
use
widgets
that
exist
today
and
then
create
pajama,
specs
and
instrument
them
later.
Just
like
we
discussed
with
the
cicd
director
dashboard.
B
B
So
it's
awesome
that
that
was
maybe
one
of
our
initial
thoughts
right
analytics
right.
So
it's
good.
A
Yeah,
my
hope
is
to
just
be
able
to
gain
all
the
efficiency
that
the
analytics
team
has
been
doing
and
not
diverge
from
that.
So
we're
just
going
to
continue
to
append
and
then
after
we
get
it
established
at
the
group
level.
That
will
be
the
ultimate
feature
set.
We
will
introduce
the
door
four
metrics
at
the
project
level,
but
it
will
only
be
metric
tiles
and
we'll
show
like
shaded
out
trend
graphs
to
be
like
if
you
are
interested
in
seeing
the
trend
over
time
for
your
dura
4
upgrade
ultimate.
C
A
We'll
talk
more
about
that
experience
like
in
13.9
14.00,
something
way
out
in
the
future,
but
priority
is
to
get
a
space
to
at
least
land
these
door,
four
metrics
in
the
near
future
and
then
actually
create
the
metrics.
B
And
then
what
about
validation?
B
Do
you
already
discuss
anything
related
to
solution,
validation
and
how
are
we
going
to
yeah.
A
So,
as
far
as
what
we
learned
from
the
ci
cd
director
dashboard
and
a
lot
of
the
research
that
I
ended
up
doing
out
of
that
and
why
we
haven't
shipped
an
nvc
for
ci
cd
director
dashboard
is
because
users
aren't
using
all
the
features
of
gitlab.
So
they
didn't
necessarily
see
value
in
having
something
separate
from
the
value
stream
analytics
and
they
hit
they
hit
homes.
They
wanted
to
see
industry
benchmarks,
which
would
be
dora4.
C
A
All
the
validation
that
we
did
around
the
ci
cd
director
dashboard
is
actually
coming
to
inform
what
we're
doing
with
these
metrics
and
the
idea
is.
We
just
display
a
point
in
time,
current
door,
four
score
for
each
of
those
four
metrics
and
then
show
the
trend,
graphs,
which
will
all
be
bar
charts
or
line
charts,
and
we
have
an
example
in
the
in
the
epic
that
is
an
analytics
mock-up.
That
plays
very
very
well
whenever
we
put
that
in
front
of
customers.
B
A
And
but
that's
a
that's,
a
good,
a
good
question.
We
we're
just
taking
all
the
learnings
that
we
had
from
you
know
nearly
a
year
ago
now
that
we
needed
to
have
more
comprehensive
analytics
and
we're
finally
rendering
them.
C
B
Since
I
don't
know
forever.
A
Because
it's
such
a
gap
in
our
users
experience
but
everybody's
doing
analytics
in
gitlab,
so
it
just
feels
foolish
to
continue
to
introduce
new
views
without
like
really
thinking
through
what
do
we
have
today?
What
will
be
a
natural
discoverable
experience
for
them?
And
then
you
know
we
can
spit
out
metrics
all
day,
but
if
it's
not
useful,
then
they're
not
going
to
use
it
so
yeah
really
tricky
and
then
kickoff.
Yes,
we
can
definitely
record
this
thursday,
so
I'll
drop
it
on
your
calendar
right
now.
Okay,.
B
And
I
was
looking
the
script,
I'm
like
okay,
you're
talking
about
all
the
design
things
so
I
feel
like
I
have
to
add.
You
know
I
don't
know,
get
some
cards
from
my
sleep
about
these
items,
but
I'll
look
into
the
the
knee
ux
review
because
I
didn't
I
didn't
review
it
yet.
A
Yeah,
all
of
those
features
are
like
we're,
delivering
all
the
work
that
you
designed
yeah.
So
it
can
be
that,
like
sorting
releases,
we
you
can
talk
about
the
breakout
page.
A
B
A
So
that
might
be
one
that
you
can
bring
up
here.
Let
me
add
here.
A
Have
not
so
that's
perfect,
perfect
opportunity,
because
this
is
all
about
visibility,
and,
what's
great,
is
that
I,
the
last
bullet
point
that
I
talk
about
is
if
I
can
find
the
script
and
the
last
bullet
point
I
talk
about
is
project
metrics
yeah,
so
that's
perfect,
yeah.
A
B
And
then
that
kind
of
goes
to
my
next
point.
It's
about
the
three-year
release
vision.
I
think
we
mentioned
this
last
kickoff,
but
I
had
my
one-on-one
with
dmitry
today
and
he
also
just
came
back
from
from
his
pto.
I
think
this
week
yesterday
and
we
just
wanted
to
align
the
next
steps
for
the
prototypes.
A
B
Time
I
see
yeah
because
dimitri
was
asking
what's
the
priority
and
I
say
last
week
this
is
supposed
to
write
for
the
first,
so
the
flow,
a
it's
reviewed.
I
can
look
at
it
to
get
sorry
flow
b.
You
can
look
at
it
again
and
see
what
else
can
be
polished
there,
but
I
think
next
steps
would
be
make
it
clickable
and
kind
of
do
this
final
presentation
review
with
you
and
audit
so
that
you
can
record
the
walkthrough
right.
A
Yes,
yeah.
That
would
be
ideal.
I
mean,
of
course,
we
can
kind
of
take
what
you
have
today
and
make
screenshots
and
put
it
on
a
slide
and
animate
it.
You
know
like
if,
if
dimitri
doesn't
have
bandwidth
to
flesh
out
the
clickability
of
it,
but
in
the
best
case
it's
clickable
you're
able
to
tell
us
how
you're
designing
it
and
then
we
we
being
orient-
and
I
can
walk
through
these
two
flows.
B
Yeah
and
then,
if
you
I
have
it
open
here,
but
if
you
look,
let
me
share
my
screen
quickly.
Yeah
wait.
It's
been
a
while.
A
B
I
love
that
comments
here.
I
didn't
review
them
yet,
but
I
can
just
apply
some
of
the
the
feedback
but
which
I
think
it's
minor,
and
then
we
have
flow
a
that.
It
hasn't
been
updated
since
the
last
presentation
that
we
had.
A
B
C
B
C
B
Make
the
flow
be
clickable
and
then
yeah
we
can
review
before
the
call
on
thursday.
B
So
let
me
add
an
action
item
here
and
to
make
it
like
this
magic.
A
And
then
hannah
on
thursday,
do
you
just
want
to
take
like
the
first
15
minutes
of
our
one-on-one
to
record
the
kickoff
okay
and
then
we
can,
or
I
can
set
up
a
separate
meeting
just
asking
your
preference.
B
If
you're
gonna
do
it
before
thursday,
it's
fine,
I
have
a
couple
of
personal
appointments
because
my
phone
is
dead,
so
I
have
to
go
to
the
apple
store
again.
Oh.
B
A
B
A
I
probably
added
like
the
next
three
milestones
worth
of
design
work
there
so,
and
some
of
them
are
assigned
to
a
milestone,
but
we
can
bump
them
out,
as
you
see
fit,
others
of
them,
I
think,
are
like
they
have
designs,
but
they
just
need
refinement
from
from
you.
Yeah.
B
That's
what
I'm
seeing
now
like
upload
upload
artifacts
a
lot
of
these
things
just
by
looking
at
the
titles
it
feels
like.
We
have
some
decisions
made
related
to
the
designing
thing,
big
sessions
or
we
already
discussed
before,
but
am
I
yeah?
I
might
need
to
just
go
over
the
prototyping
phase
again,
but
I'll
go
over
these
and
then
before
friday.
Before
thursday,
we
have
something
to
discuss
again.
B
And
anything
from
I
know
that
juan
pretty
much
didn't
have
to
do
a
cover
for
anything,
but
is
there
anything
from?
I
don't
know
engineering
from
front
end
that
you
think
I
need
to
be
looking
into.
A
Some,
the
releases
page,
we
had
a
dog
fooding
update,
which
was
adding
a
distinction
if
something
is
sass
only
or
self-managed,
only
it's
just
a
little
text
appendment
and
for
me
like,
since
we're
not
building
it
into
the
future.
It's
not
it's.
Just
a
it's
a
an
enhancement
to
make
it
easier
for
sales
to
use.
I
don't
think
you're.
You
really
need
to
spend
much
time
on
it.
A
For
me,
I
felt
like
it's
going
to
be
usable
and,
as
we
start
to
think
through
the
release
of
splash
page
then
sourcing
that
content
from
issues
that
formatting
may
change
anyways,
because
then
we
may
require
labels
instead
of
that
text,
pulling
it
in
from
the
release
post.
So
to
me,
it's
something
that
we'll
end
up,
probably
deprecating
in
the
next.
A
You
know
four
milestones
or
so,
as
we
build
out
more
functionality
to
populate
the
release,
notes
of
the
releases
page,
but
that
was
the
only
one
I
could
think
of
all
the
other
work.
I
think
jake
hasn't
created
any
mrs
for
front-end
review
yet
from
the
combo
box
perspective,
so
I
think
we're
in
good
shape
there.
A
B
A
I'm
trying
to
find
the
issue
right
now
because
he
just
pinged
back
and
said
like
oh
yeah,
this
is
done
so
I'll,
fine
I'll
find
it.
I.
B
C
A
B
A
A
And
it
will
get
worse
before
it
gets
better
because
we're
wanting
to
like
add
issue
descriptions,
and
so
the
expectations
from
the
release
post
process
have
kind
of.
We
have
to
break
some
old
habits
of
finding
data
and
information.
You
know
because
people
when
they
go
to
consumer
release,
notes
right
now,
they're
going
to
click
into
that
particular
feature
and
like
see
what
that
feature
is
about
if
we
provide
them
with
a
bunch
of
text,
they're
not
going
to
read
through
it.
So
we
need
to
be
mindful.
B
Exactly
I'm
really
looking
forward
to
this
one,
because
it's
going
to
be,
I
think
it's
going
to
the
splash
page
is
going
to
be
a
good
opportunity
to
be
creative
and
then
just
think
outside
the
box
a
little
bit
because,
right
now
an
initial
version
was
really
a
rip-off
of
what
github
has
for
the
release
page
and
that's
it.
That's
pretty
much
everything.
So
I
think
it'll
be
a
nice
exercise
for
us
to
play
around
with
the
big
vision.
I
think,
and
then
we
can
break
it
down
into
like
what
we
do.
B
Did
we
have
any
category
updates
jackie
while
I
was
away
or
anything
else
that
I
need
to
stay
on
top
of.
A
No,
I
I
did
do
direction
updates
in
september,
but
most
of
it
was
what's
next
and
I
did
ping
you
on,
like
I
did
ccu
on
them,
so
you'll
probably
have
them
in
your
to-do's
just
for
review,
but
october
will
be
coming
up
and
then
of
course
I'll
have
you
be
my
reviewer
of
those
before
I
merge
them?
I
just
merged
the
september
ones,
because
you
weren't
here
I
like
to
have
you
give
me
input
before
I
merge,
but
yeah
timing
just
didn't
shake
out
that
way.
B
It
was
good,
and
I
know
it's
a
bit-
maybe
it's
too
soon,
but
I
know
that
you
all
have
thanksgiving.
When
is
that
in
november
or
october,.
A
So
november
I'll
be
taking
some
time
off
that
week
of
thanksgiving,
it's
like
the
26th.
C
C
A
B
I'm
I'm
asking
also
because
I
have
interest
in
knowing
when
people
are
not
going
to
be
in
the
office,
so
I
can
so.
I
can
plan
my
things
in
and
do
some
focus
work,
but
I
had
this
conversation
I
think
with
dimity
just
now
about
holidays
and
they
say:
oh
yeah,
we
have
thanksgiving
coming
in
everything
gets
so
quiet.
A
I
mean
we're
doing
a
bug
milestone
in
december
to
january,
because
I'm
pretty
sure,
like
everyone
will
be
taking
time
off
and
as
a
result,
I
don't
want
to
like
want
to
give
people
space
and
opportunity
to
think
and
innovate
and
not
feel.
B
A
A
I
love
it.
Okay,
awesome
anything
else.