►
From YouTube: Fulfillment Release Kick-Off 12.9
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
Okay,
awesome,
okay,
so
it's
being
recorded
now
welcome
to
the
twelve
nine
kickoff
I
apologize.
If
this
meeting
goes
a
little
different
than
before,
because
I
don't
know
what
we
did
before
so
I
look
forward
for
any
recommendations
of
how
we
can
make
this
useful
or
if
you
don't
find
it
useful
at
all,
we
can
scrap
it
totally.
B
A
To
the
team,
so
let's
get
some
feedback
on
that
moving
forward.
I'm
gonna
dive
right
in
because
we
only
have
30
minutes
and
I
have
a
bit
of
stuff
here.
Just
some
things
to
highlight:
I
just
dropped
in
the
links
to
different
things
here
at
the
top.
But
let's
talk
about
priorities
for
12:9,
probably
the
most
important
thing,
which
everything
is
important
but
the
most
heartburn.
We
will
all
feel
if
we
don't
get
it
done,
whose
issue
number
191
four
to
eight,
which
is
essentially
not
allowing
a
self-managed
license
to
work
when
it's
loaded.
A
If
the
start
date
is
a
future
start
date,
so
from
a
business
perspective,
we're
constantly
renewing
customers
early,
that's
a
good
thing,
because
we
want
to
get
them
locked
in
and
move
on
to
other
things,
but
today,
when
they
get
a
self-managed
license,
they
can
load
it
and
it
immediately
gives
them
the
entitlements
regardless
of
the
date.
So
that's
a
real
bad
thing
on
the
onion
side.
So
everybody
take
a
look
at
that.
If
you
have
any
participation
in
that
issue,
please
make
that
your
top
priority
and
okay
other
priorities.
A
I
want
to
talk
about
how
I'm
conveying
priorities,
let
me
do
a
quick
share.
This
may
or
may
not
work
for
the
group.
I've
heard
that
it's
not
the
best
way
for
everybody,
so
right
now,
I'm
going
to
tell
you
what
I've
done
for
this
milestone.
What
I'd
like
to
talk
about
in
our
retro,
this
milestone
is:
how
else
can
we
do
this?
A
A
This
is
the
third
priority
when
you're
looking
at
a
list
view
of
the
issues
for
the
milestone,
you
can't
see
that
right,
I
can
search
by
milestone,
but
you
can't
see
the
fact
that
I've
said
this
is
my
number
one
priority
as
per
the
business,
so
just
something
that
I
want
us
all
to
be
thinking
about
you
know:
should
we
should
we
change
the
use
of
the
priorities
within
the
milestone
so
that
you
have
that
we
create
a
new
label?
Should
everybody
use
this
the
board,
other
ideas?
A
C
Yeah
Mike,
my
sort
of
idea
here
is
that,
like
once
it's
in
the
milestone
is
that
they're
kind
of
all
equal
priority?
Is
that
kind
of
not
the
right
thinking
here
about
this,
because
I
mean
we
could
I
mean
our
goal
is
to
pretty
much
try
to
finish
out
all
the
tasks
that
are
in
the
milestone
during
that
Mouse
and,
if
possible,
so
like
I,
would
assume
that
our
we
could
pull
from
that
milestone
in
any
order
that
we
want.
Is
that
not
correct
yeah.
A
But
those
are
the
things
that
are
like:
okay,
we
can.
We
can
deal
with
that.
I
picked
back-end
I
met
front-end,
but
basically
I
am
staff
staff
ranking
them
to
say
to
convey
to
your
team.
Okay,
start
in
p1
column
and
start
at
the
very
top.
That's
the
ideal.
The
exceptions
would
be
like.
Let's
say
this
particular
issue
also
relates
to
this
issue,
and
you
can
knock
those
two
out
together.
A
C
D
A
D
A
A
So
I
just
want
to
make
sure
that
two
men
Emily
are
on
the
same
page
with
the
things
that
are
assigned
to
UX
and
the
priorities
there
so
I'm
Tim's
plate
with
me,
the
big
hot
potato
that
everybody
should
be
aware
of,
which
is
that
don't
let
the
license
work
early
and
then
we
have
some
pajamas
reviews
for
the
front-end
team
that
we'd
like
to
get
moved
over
to
that
team
as
quickly
as
possible.
So
Tim
are
you
on
the
call
thank.
E
B
F
E
F
A
man
and
I
working
really
closely
so
I
think
I
think
we're
good
there.
What
we
have
in
retention
is
there
is
the
scorecard
for
renewing.
There
is
the
what's
new
notification,
which
Qin's
already
done
some
design
on,
and
so
that
shouldn't
be
a
huge
thing,
there's
an
item
to
add
a
link
to
the
portal
on
the
admin
/
license
page.
So
that
should
be
like
a
but
I.
Hopefully
that's
a
quick
one
and.
E
C
C
C
E
E
C
E
Well,
when
that
happens,
just
keep
in
mind
that
it
should
be
really
quick
and
when
it
happens
like
if
it's
not
quick,
it's
probably
because
there's
maybe
some
priority,
we
don't
know
about
or
the
designer
actually
doesn't
know
or
realize
they
miss
the
pain
or
something
like
that.
So
it
might
be
like
message
them
a
second
time
or
message
me,
and
we
can
maybe
see
if
there's
another
designer
who
can
do
the
review
as
well,
that
shouldn't.
We
definitely
don't
want
that
to
take
long.
Okay,.
E
Cuz
I
thought
those
were
all
done.
That
was
my
understanding,
so
there's
anything
that
still
needs
design
work.
Let
me
know
you
can't
get
that
done.
A
A
Jackie
after
this
meeting,
thanks
and
thanks
for
the
reminder,
it's
okay
desk
ly,
even
if
it's
more
than
once,
everybody
gets
busy
and
accidentally
deletes
the
email
notifications
that
you
got
ping
done.
Something
same
goes
for
me.
If
you
ping
me
once
or
twice,
don't
be
afraid
to
pick
a
third
time,
I
will
thank
you
for
it.
Yeah.
E
Yeah
I
mean
I
know
it's
not
like
we're
getting
people
in
trouble
or
anything
like
that.
We're
doing
a
good
job
and
it's
just
a
matter
of
sometimes
like
we
get
so
many
messages
and
notifications,
and
sometimes
things
get
buried.
Our
loss
so
and
I'm
happy
I
get
being
done,
something
that's
it
understood.
A
Alright
and
then
I'm
Emily's
play
the
we've
got
a
bunch
of
work
here
with
the
kind
of
showing
the
warranty
the
different
flavors,
of
showing
warnings
for
the
users.
If
I
have
this
a
little
bit
lower,
but
I
think
that
we
have
some
confusion
on
when
dev
I'm.
Sorry
when
design
is
complete
because
they're
still
assigned
to
the
issue
that
I
think
sometimes
dev
thinks
there's
something
outstanding,
I'm,
not
sure
I'm.
Making
that
assumption
I
just
want
to
clarify
that
our
UX
folks
will
continue
to
have
the
issue
assigned
to
themselves.
A
A
E
A
Emily
has
those,
and
then
also
in
our
p1
list,
opiate
towards
the
bottom.
We
have
the
SKUs
for
the
open
virtual
classroom.
That's
a
good
one!
That's
working
towards
our
okay,
ours,
giving
us
more
money
in
the
door.
So
anything
we
can
do
to
get
that
one
out
as
well
would
be
awesome
in
terms
of
I
wasn't
going
to
review
the
entire
board.
I
had
hoped
that
the
team
had
a
chance
to
take
a
look
at
what
was
on
there
before
this
meeting.
A
A
Moving
on
I
just
thought,
there
was
a
lot
of
really
helpful
feedback
in
the
12
8
retro.
One
of
the
things
that
I
thought
was
really
good.
Was
a
Mars
gamers
suggestion
about
taking
big
items
and
doing
a
review
between
front
end
and
back
end
right
in
the
beginning
to
become
more
efficient,
I,
don't
know
that
we
have
any
of
those
in
this
one,
but
I'd
like
to
kind
of
toss
it
out
to
the
team.
A
Also
I
saw
a
theme
where
folks
were
saying
towards
the
end
of
the
milestone
that
they
weren't
feeling
super
productive
or
they
get
bogged
down
in
research
or
just
different
kind
of
things.
That
happened
in
that
milestone
and
I
want
to
know.
Is
there
anything
that
anybody
on
the
team
can
do
to
remove
blockers
or
prevent
that
from
happening
again,
or
was
it
just
kind
of
a
one-off.
G
For
me,
it
was
probably
just
more
of
a
one-off
with
just
you
know:
getting
assigned
really
picking
up
the
tasks.
It
was
more
research
related
than
like
actual
code
out
but
like
creating
a
Mars
type
of
thing.
So
it's
not
list
not
necessarily
that
I
was
less
productive.
It
was
just
a
different
type
of
productive,
and
so
maybe
that
looks
differently
if
our
you
know,
if
so
the
metrics
that
we're
going
for
is
the
number
of
M
ours
that
are
getting
output,
so
it
maybe
feels
less
productive
in
that
regard.
A
A
Okay,
so
I
just
want
to
discuss
issue
assignments.
We
kind
of
talked
about
that
a
little
bit
just
you!
Well,
let's
back,
let's
wait
for
Jackie
to
come
back
after
she
talks
with
the
team,
and
then
we
can
go
from
there.
Maybe
we
can
discuss
this
ACM
planning
issue
and
then
I
wanted
to
highlight
for
UX
issues
moving
forward.
I
want
to
be
really
cognizant
of
indicating
if
the
deliverable
in
the
issue
is
just
the
design
and
we're
going
to
close
that
issue
and
design
is
done
and
create
a
related
issue.
A
I
want
that
to
be
very
clear
as
well
as
when
we
expect
the
deliverable
of
an
issue
to
include
both
design
and
oh
because
sometimes
it
can
get
confusing.
What
is
the
output
of
this
particular
issue?
Are
we
going
to
open
another
one
and
if
we
aren't
going
to
open
another
one
UX
need
to
know
that
so
when
they're
prioritizing,
they
know
that
okay,
somebody's
waiting
on
this
issue.
A
Then
lastly,
I
just
want
to
give
a
heads
up
on
some
labels.
I
think
that
we
agreed
in
the
planning
issue
that
we're
not
in
use
the
deliverable
it
label
anymore,
because
it's
kind
of
giving
us
a
false
output,
because
it's
being
used
inconsistently,
if
there's
a
desire
to
use
it,
that's
fine
too,
but
let's
just
get
everybody
on
the
same
page
with
using
it,
so
that
the
metrics
make
sense,
but
I
think
as
of
this
minute,
we're
not
using
it
and
then
two
new
labels.
A
This
one
I
mentioned
in
a
different
four
and
app
ecosystem
is
for
any
work
that
is
likely
to
touch
our
effect.
Enterprise,
app
salesperson
or
straight
mark
head.
Oh
and
another
new
label
which
I
or
other
product
managers
will
be
applying.
Is
growth
deliverable?
That's
just
two
track
items
that
are
hitting
our
growth:
okay,
ours.
A
This
is
not
to
be
confused
with
the
deliverable
legal
that
we
just
talked
about,
so
it
doesn't
mean
anything
necessarily
different
to
you
other
than
this
is
this
is
to
help
with
our
locators
and
then
the
last
thing
I
had
was
I
know.
Everybody
is
eagerly
awaiting
the
kitchen:
sink
user
I've
been
waiting
on
access
requests,
they
just
started
been
getting
filled,
so
hopefully
I
can
get
in
there
and
actually
I'm
going
to
have
access
from
staging
or
sandbox
Salesforce
to
our
customers
at
get
lab,
calm
and
I.
A
E
If
we
circle
back
to
the
UX
question
about
visual
reviews,
I
actually
posted
a
link
that
can
take
a
look
at
it.
We
have
made
a
hymnbook
update
a
couple
of
weeks
ago
about
visual
reviews
and
it
says
that
it
says
that
we
as
unassign
the
UX
serve
once
design
is
done
and
then
dev
reassigns
new
york,
so
so
there's
a
already
written
in
there
and
we
excited
about
it
more
in
the
context
of
the
acquisition.
E
But
I
think
you
should
just
apply
to
all
the
growth
teams
like
we
should
do
the
same
thing.
So
if
you
all
want
to
take
a
look
at
that,
if
you
have
any
other
suggestions,
you
can
make
another.
Mr
we
can
talk
about
it
a
sink,
but
I
think,
probably
for
now
we'll
just
go
with
and
I'll
give
the
designers
a
chance
to
like
reread
it
and
make
sure
you
keep
firm
that
that's
how
we
want
to
do
that
from
now
on,
I.
A
Think
that's
great,
just
just
having
the
clear
expectation
of
who
owns
what
I
think
will
be
way:
more
efficient
and
less
confusing
mm-hmm
r18
I
did
the
majority
of
the
talking
here
so
I'm
gonna
ask
is
this
meeting
an
official
I?
Can
I
can
write
out
an
agenda
and
you
can
reference
it
async
for
future
meetings,
or
do
you
like
the
idea
of
the
discussion
thought
time
on
this
meeting
in
general?
Changing
it?
What
works
for
you,
but.
C
I
think
it
might
be
good
to
try
to
get
it
sooner
like
right
after
the
last
sprint
ends.
That
knows
the
first
time
we've
done
it,
but
we're
already
kind
of
like
a
week
into
it
like
honey.
Even
the
development
already
so
I
think
just
getting
it
out
of
it
right
at
the
beginning
of
the
spring.
Are
the
perfect.