►
From YouTube: Release Management UX Definition of Done
Description
Review of the UX Process fo Release Management
https://gitlab.com/gitlab-org/ci-cd/release-management-group/release-management/-/issues/21
C
A
B
B
D
B
Rush
that
because
just
for
the
sakes
of
me
Sookie
I
know
that
we
have
to
delivery
or
whatever
but
I
record,
we
don't
work
on
the
plan
during
the
next
milestone.
The
current
milestone
then
executing
it
is,
for
the
sake,
soft
executing
it,
because
we
know
that
things
are
going
to
change
and
improve
next
month,
so
it
definitely
starts,
but
yeah
yeah
I.
D
Talked
to
Kenny
and
I,
and
the
same
kind
of
justification
and
data
that
I've
shown
in
that
one
908
issue
I
think
we're
viable
according
to
the
old
definitions.
So
really
I
completely
agree
that
we
can
check
that
okay
are
off,
given
that
it
was
in
flight
from
if
Christy
has
a
big
heart
of
heartburn
over
this,
we
can
figure
it
out,
but
I
just
wanted
to
to
show
you
what
I'm
seeing
from
a
product
side,
we
have
some
UX
insights
that
we're
able
to
tie
into
that
plan.
So
hopefully
we'll
go
from.
D
D
T-Shirt
sizing
doesn't
really
translate
I
agree.
I,
think
that
would
be
weird
I
mean
like
what
would
be
as
a
medium
versus
a
large
for
a
design
project.
I
feel
like
that'd,
be
very
strange
for
me
to
try
to
conceptualize
as
well
the
biggest
the
biggest
goal
that
I
have
here
is
that
I
really
want
us
to
find.
What's
the
result
that
we're
trying
to
get
out
of
design
activities
and
make
that
a
concrete
relationship
to
an
output?
D
D
Understanding
and
reconciling
story
points
to
how
engineering
is
waiting
and
if
something
has
a
really
high
design
proposal,
and
it
has
a
really
low
engineering
effort.
Is
there
something
wrong
with
our
weights
and
estimations?
Because
when
we
look
at
total
effort,
I
just
want
to
make
sure
that
we're
being
mindful
of
that
right,
I
think.
B
B
B
D
A
D
D
So
then
we
would
break
it
down
to
several
issues
and
then
I
think
that
the
engineering
teams
like
okay,
so
there's
five
components
here,
I
get
to
edit
all
these
components
in
one,
mr
and
it
becomes
a
very
like
comprehensive
evaluation
of
total
team
effort
for
a
feature
or
for
an
NBC
and
I
think
that
that
could
be
really.
That
could
be
a
really
great
concrete
way
to
evaluate
UX
effort
versus
engineering
effort.
D
But
I
do
understand
that
changing
components
and
designing
components
is
not
necessarily
comprehensive
when
we're
looking
at
the
design,
time
and
effort
right,
because
you're
on
called
you're
interviewing
customers,
it's
like
if
I
had
to
wait
issues
I
would
come
up
with
an
abstract
p.m.
task
and
I
would
then
say
like
1:00
p.m.
task
is
equal
to
about
two
days
and
that's
how
that's
how
I
would
do
it?
D
B
B
A
D
A
A
D
C
B
So
I
was
going
to
say
that
I
think
it's
very
interesting
having
this
idea
or
having
this
concept
of
breaking
down
into
village.
Ripples
like
mocks
or
components
or
whatever,
because
whatever
that
we
not
just
you
and
I,
but
together
with
John
and
Nathan,
we
identify
us
more
like
components:
I'm
gonna,
just
gonna,
say
components
right
yeah.
So,
for
example,
this
thing
is
to
become
a
few
components,
but
for
that
we
need
the
design
marks.
So.
B
In
my
acceptance
criteria
that
we
all
agreed
on,
they
defined
that
there
will
be
certain
front-end
effort.
It
means
that
all
my
work
is
going
to
be
translated
into
a
front
end
issue.
So
it's
nice
to
have
this
relationship
between
my
gasps.
We
have
yeah
I,
like
that
and
I
think
one
ways
one
of
the
ways
to
achieve
that
is
actually.
My
last
point
to
the
agenda
is
to
perhaps
having
a
definition
of
done
for
us,
because
that's
when
we
can,
you
know
look
at
the
stats.
D
Love
this
idea
we've
been
kind
of
doing
this
organically
with
this
so
like
our
our
release,
management
needs
UX
review
if
I
was
to
throw
like
a
definition
on
when
we
take
one
of
these
issues
out
of
the
UX
review
epoch
and
we
put
it
back
in
its
natural
epoch
and
move
it
to
the
active
board.
The
the
criteria.
Let
me
even
start
writing
in
this
issue
so
that
we
can
just
kind
of
document.
As
we
go,
I
would
say
it
has,
has
a
prototype
or.
B
Something
like
this
is
to
keep
working
with
user
stories,
because
from
the
moment
that
we
identify
that
users
are
going
to
need
to,
you
know,
perform
different
actions
will
have
different
flows.
It's
when
we
can
break
this
into
different
deliverables
for
developers
well
create
only
through
UI
or
then
you
also
have
the
backstage
right.
That's
a
completely
different
user
story
and
the
acceptance
criteria
is
different.
So
for
nathan's
that's
a
separate
backwards.
Oh
I
see
that
about.
D
B
D
A
A
A
B
Because
from
I
need
from
most
recent
experiences,
what
means
taking
the
longest
is
the
first
step
is
that
defining
scope
is
this
story?
This
is
the
criteria,
but
it's
not
even
creating
them,
because
I
can
just
look
at
this
skull.
You
know
limitation
discussions
and
come
up
with
a
proposal,
but
is
it
refine
it
and
that's
the
process
that
he
said
it's?
A
D
A
D
A
D
Criteria
for
ready
for
development
scope
has
been
defined,
user
stories
have
been
weighed
in
are
less
than
five,
mrs,
so
once
it's
moved
into
development
in
order
for
it
to
be
done,
engineering
has
a
bunch
of
tasks
that
we
already
we
understand,
and
we
know
but
I'm
interested
in
hearing.
If
there's
like
a
closeout
task,
we're
like
UX
must
sign
off
on
the
front
end
effort
exactly
and.
B
B
B
And
that
that's
part
of
the
their
workflow
or
already
that's
a
criteria
for
them
yeah,
but
then
I
think
that's
when
we
also
spots
opportunities
to
create
new
issues,
or
you
know,
make
updates
on
on
the
current
scope,
the
scope,
things
or
change
criteria
and
exactly
what
you
put
there
update
the
source
of
the
source
of
truth
or
create
new
issues
or
the
changes
that
they
have
identified
there
either
I
expect
them
to
do
them,
if
not
themselves.
Sometimes,
if.
A
B
A
B
B
B
D
Maybe
this
is
done
with
you
and
I
when
I
create
the
milestone
planning
issue,
and
that
way
we
can
have
like
UX
issues
that
you
wait
beforehand
and
then
we
assign
them
to
the
engineering
team.
Does
that
so
that
we
have
like
their
capacity
reserved
I
mean
it
would
be
it's
an
extra
list,
because
you
and
I
would
then
be
co-creating
the
planning
for
the
milestone
and
I'm.
Okay
with
that,
that's
not
like
it's
just
next
to
lift
for
you.
D
It
takes
more
time
out
of
your
day
to
then
come
into
the
product
process
and
plan
out
what
we're
gonna
be.
Delivering
I
also
want
to
get
ahead
of
this
a
little
bit
more
now
that
we've
added
all
of
the
UX
front-end
labels.
Maybe
this
is
like,
although
we
have
a
good
idea
of
like
what's
happening
in
our
roadmap,
it
I
feel
hesitant
to
get
too
far
ahead
because
of
how
sometimes
things
shift
out.
We
talked
about
that
paradigm.
D
C
D
Dot,
11
or
13
I,
don't
know.
If
we've
made
a
decision
on
that,
yet
it
will
add,
it
will
push
out
the
major
release
to
Juna.
Don't
you've
made
that
decision
yet
so
we
can
test
out
using
this
search
or
twelve
dot,
eleven
thirteen
and
kind
of
go
from
there.
We
already
have
those
issues
to
find
so,
for
example,
like
the
CI
CD
dashboard
effort.
That's
no.
B
B
Right
so
I
think
what's
going
to
happen,
is
that
at
some
point,
I'll
just
go
into
the
issues
with
you
or
by
myself
and
come
up
with
an
admission
wait,
and
then
we
find
that
together
to
understand
from
that,
you
know,
sighs.
What
can
we
actually
deliver
and
what
what
do?
We
will
actually
want
to
focus
on
the.
A
B
D
So
I've
been
doing
this
with
our
engineering
to
kind
of
reconcile
like
how
well
are
we
estimating
things
and
for
the
items
that
go
through
the
tech
evaluation
process?
We're
within,
like
you
know,
90
percent
right
so,
like
we
probably
have,
maybe
one
more,
mr
that
wasn't
included
in
the
weight
additionally,
but
for
issues
that
didn't
go
through
the
technical
review.
Sometimes
we
have
five
times
the
amount
of
mrs
that
were
originally
side
when
they
picked
up
the
issue
like
the
the
delete
in
environment
via
the
UI.
Oh,
my
god
that
one.
B
You
axis
a
bit
more
fluid
right:
it's
not
it
can
be
merger
class,
but
then
I
think
in
a
way,
that's
how
they
understood
engineers
understood
and
how
complex
the
problem
became
or
or
whatever
reason
right
for
that
where's
your
class,
but
also
to
me
if
we
don't
have
like
a
set
base
to
end
the
design
process.
It's
difficult
to
measure
velocity
at
four
at
the
class
of
eight,
and
we
don't
have
that.
We
have
to
the
point
where
something
Lots
hand
out
to
the
developers
ready
for
development,
but
it
doesn't
end
there.
D
This
is
why
I
added
the
entry
criteria,
because,
for
example,
this
might
enter
into
ready
for
development,
but
then
it
gets
passed
back
to
design.
So
it
can
be
very
cyclical,
and
right
here
is
where
you
would
need
to
re
estimate
the
effort
once
it
gets
passed
back
to
you.
So
that's
that's.
Why
I
took
a
step
back
and
looked
at
like
entry
and
exit
criteria
so
that
we
could
understand
like
how
do
we?
D
How
do
we
approach
this
as
an
infinity
or
like
the
double
diamond
instead
of
just
a
waterfall
approach,
because
it's
not
waterfall
perch,
we
should
be
iteratively,
designing
and
thinking
about,
and
estimates
are
only
a
snapshot
in
time
and
they're
expected
to
change
as
we
learn
new
information.
So
what
we
should
be
capturing
are
the
transitions
of
when
we
put
something
into
design,
and
we
said
it
was
going
to
be
you
know,
and
this
is
where
I
get
back
to
the
concreteness
of
it.
D
B
Awesome
because,
for
example,
the
same
way
we
can
be
I
know
they
wear
so
many
mock-ups
for
deploy,
freeze
and
then
I
just
do
something:
funky,
clap
CI
right.
So
we
measure
30
points.
They
should
design
an
effort.
But
then,
during
the
refinement,
this
the
scope
has
been
defined
and
criteria
for
ready
for
developments.
We
change
that,
but
I
think
it's
a
good
way
for
us
to
be
able
to
measure
that
and
also
will
help
us
apply
and
identify
where
it
gets
goes
on.
When
similar
issues
come
on.
A
D
A
B
B
B
D
B
Sense
and
I
think
especially
Nathan
and
the
ones
are
you
so
much
involved
in
the
UX
process.
They're
going
to
definitely
want
to
give
any
person
might
be
able
to
help
us
identify
some
of
the
steps.
Because
to
me
it's
it's.
Even
if
it's
difficult
to
put
like
a
sex
hard
set
of
steps
because
I'm
it
just
happens,
I
don't
know
it's
just
so
fluid
right,
I,
don't
follow.
B
1
2,
3,
4
5,
for
example,
I
avoid
prototype
into
the
last
minute,
because
I
know
that
this
cope
is
going
to
change
right
now
until
the
moment
we
respond
besides
that
they're
gonna
start
coding
or
that
I
can
post
a
prototype,
but
they
are
also
working
on
the
that
attack
evaluation.
The
research
issue
and
my
prototypes
are
not
valid
anymore.
So
it's
it's
a
gamble.
Let's
see
but
I
think
it's
a
good
start.
A
B
B
D
Once
it's
reviewing
the
review
app
for
the
release
post,
any
any
any
item
that
was
in
the
release
place
that
had
a
front-end
component
he's
like
I
want
to
screenshot
so
like
that's
so
hard
for
product
managers
because
sometimes
like,
if
the
features
are
right
up
into
the
line,
so
awesome
well
Thank
You
Hana!
For
this
conversation,
this
was
really
good.
I
appreciate
your
your
effort,
you're
awesome,
yeah.