►
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
B
I
also
discussed
individually,
but
I
just
want
to
repeat
a
lot
of
items
that
we
have
scheduled
about
seven.
So
this
is
specific
for
this
release,
but
it's
also
general
for
all
releases.
There
might
be
an
item,
that's
too
large
to
do
design
and
implementation
at
the
same
milestone
and
the
problem
with
with
that
is
that
when
we
do
a
release,
kickoff
its
Auto
generated
according
to
anything
that
has
a
label
and
has
the
milestone
on
it.
The
next
milestone.
B
So
it
looks
to
the
customers
as
if
we're
going
to
deliver
this
at
the
end
of
the
milestone.
So
it's
misleading
and
and
that's
why
I
only
want
to
leave
the
development
implementation
issues
within
a
milestone
excluding
from
that
is
everything
that
is
going
through
the
validation
track,
because
that's
only
our
job
and
that's
specific
to
a
milestone.
B
But
if
anything
that
involves
both
UX
and
implementation,
if
it's
too
large
to
be
in
one
milestone
that
what
I
want
to
do
from
now
on
is
put
the
the
issue
in
the
next
file
stone
and
have
the
designers
working
on
it
on
this
current
Mouse.
So
it's
a
little
bit
confusing
for
you.
But
what
is
something
to
keep
in
mind.
E
B
I
I
definitely
agree.
I
definitely
also
think
I
need
your
input
to
know
what's
really
large
and
requires
an
additional
issue,
because
a
lot
of
UX
issues,
just
like
you
know,
I,
had
a
tool
superior
milestone
there,
which
definitely
doesn't
require
a
new
issue.
So
if
you
feel
this
is
something
that
I've
been
encouraging
engineering
as
well,
if
you
feel
the
thigh
dam
is
too
large
for
one
milestone,
then
let's
open
another
issue,
it
shouldn't
be.
We
shouldn't
be
dealing
with
humongous
issues,
doesn't
matter
who
notices
you
hungry
and.
A
B
I
think
we
should
also
have
you
know
more
holistic
vision,
issues
which
will
probably
have
those
inside
like
I
just
something
very
similar
with
Mike
for
future
flags.
I
think
we
had
this
discussion
when
we
talked
about
all
the
different
features
that
were
thinking
he
put
all
the
mock-ups
into
one
issue
and
then
only
after
we
finished
that
did
we
actually
separate
it
into
individual
issues,
which
I
thought
was
a
really
good
practice.
You
know
I.
D
Think
it's
a
it's
a
good
best
practice
urbanize
for
us
to
try
it
out
with
some
of
the
issues
like
what
you
say
they
need
more
holistic
approach,
doesn't
have
to
be
for
every
small
detail:
I
agree.
Sometimes
you
don't
even
need
prototyping
or
anything.
Let's
draw
an
acceptance
criteria
or
a
description
sometimes.
A
Yeah
I
also
I,
really
like
what
your
ladies
are
discussing,
and
in
this
case
you
know,
if
we
will
be.
You
know,
oriT
you're,
saying
that
you
need
help
from
product
designers
to
understanding
what
speak,
what
small,
the
size
and
I
feel
like.
Also
product
designers
sometimes
have
questions
about.
You
know
like
more
the
diving
deep
into
the
problems,
and
you
know
maybe
competition,
maybe
you
know
business
goals,
etc.
A
So
it
all
goes
to
this
point
that
we
need
you
explaining
is
kind
of
like
your
XBMC
sync
ups,
and
this
is
free
and
goes
to
like
what
we
started
to
discuss
before
everyone
else
joined
I.
Think
maybe
we
can
leverage.
This
search
is
maybe
we
can
transform
them
basically
into
like
you,
acts
planning,
visual
discussions,
I,
don't
think
big
whatever
you
want
to
call
them
and
split
them
by
the
group,
so
I
feel
like.
A
D
B
B
D
A
A
D
My
suggestion
was
to
like
have
15
minutes
to
go
over
each
stage.
It's
see
subgroup
whatever,
so
that
we
can
keep.
It
focused
and
have
a
little
bit
more
of
a
sync
opportunity,
but
I'm
happy
to
try
anyways.
But
my
points
again
is
that
we
need
to
have
an
agenda
set
before
those
calls,
because
we
have
the
p.m.
we
have
the
engineering
manager
call
and
then
we
have
the
group
check-ins.
D
We
have
a
bunch
of
calls
that
happen
before
this
one,
and
then
we
end
up
not
really
discussing
everything
that
we
have
to
so
another
suggestion.
Maybe
we
can
move
this
instead
of
first
knit
Thursday
to
another
day
like
I,
don't
know
Tuesday
before
the
end
of
the
week,
but
yeah
or
it
doesn't
work
on
Fridays
right.
So,
yes,
I'm.
A
Afraid
that
15
minutes
can
be
a
little
short,
but
I
didn't
like,
like
from
the
side
I'm,
seeing
how
much
discussions
and
questions
can
happen.
I
feel
like
15
minutes
is
actually
10.
Well,
let's
put
it
this
way.
10
minutes
is
an
ideal
time
to
discuss
that.
One
issue
in
details.
You
know,
for
example,
like
taking
again
this
this
one
bottle
story,
Mike
that
we
discussed
today
in
the
morning,
so
I
feel
like
yeah.
Trying
to
separate,
though,
can
be
a
bit
more
beneficial
and.
D
D
D
I
know
it's
time
for
us
to
change
the
structure
of
this
call,
but
this
was
really
a
moment
where
Jane
and
I
would
just
go
over
the
board
and
that's
how
I
can
I
used
to
do
them
to
you
recently,
with
my
just
go
over
everything
and
see
the
status
of
the
milestones
like
at
a
health
check
and
I'm
gonna
link
here
the
issue
about
productive
meetings
and
because
I
think
we
already
have
some
ideas
and
inputs
there.
Maybe
we
can
follow
up
on
that
I'm
gonna
head
here,
but
it's
also
in
the
dock.
A
And
something
that
we
discussed
with
the
read
this
is
like.
The
second
point
here,
however,
like
I
definitely
agree
with
the
fact
that
we
should
not
like
it
would
be
nicer
to
not
place
that
design
the
the
issues
that
we
are
working
in
design
and
we
will
then
we
know
that
it
won't
end
up
in
a
milestone
in
this
current
milestone
in
places
like
last
one
milestone,
work
on
it
like
+1
miles,
so
I
was
thinking
that
it
would
be
also
amazing.
A
I
want
to
discuss
like
some
research
opportunities
and
like
planning
even
more
ahead,
and
you
guys
probably
will
kill
me
right
now,
but
talking
about
like
what
is
going
into
the
plus
two
milestones.
So
we
can
start
the
validation
even
earlier,
because,
if
you're
working
on
the
things
that
will
be
released
to
the
next
milestone,
that
we
should
be
doing
validation
in
all
the
things
that
will
be
released
in
two
milestones.
Pretty
much
I,
don't
know
if
that's
clear,
I'm,
making
myself
clear
so.
B
B
So
actually,
if
you
start
working
on
an
issue
and
you
go
into
the
epic
itself,
you
can
see
kind
of
the
roadmap
that's
planned.
Even
if
we
don't
follow
it
to
the
letter.
You
can
pretty
much
see
what's
coming
up
in
the
next
aisle
and
so
on
and
plus
two
plus
three,
so
you
can
get
wrap
your
head
around.
What's
coming
up
and
get
a
bigger,
better
picture
of
what
we're
planning
on
doing.
D
And
I
think
also
once
we
get
really
not
get
started,
because
we
already
we
already
doing
this,
but
we
did
think
make
sessions.
We're
gonna
have
a
better
overview
like
what
all
its
say,
outs,
the
issues
or
the
the
functionality
is
more
holistically,
and
then
we
can
break
things
down,
ordered
a
look
at
milestones
and
then
decide
what
to
build.
I
think
that's!
We
need
to
shift
that
approach
at
some
point,
but
that's
gonna
happen.
It's
natural.
E
Also
think
this
is
a
good
opportunity
to
utilize
the
Planning
Board
for
things
like
this
right.
Look
one
in
two
milestones
ahead.
You
know
we're
at
the
early
stages
of
that,
but
I
can
see
that
being
a
very
valuable
thing
is
on
that
planning
board
kind
of
having.
However,
we
end
up,
structuring
it,
but
some
way
to
visualize
it
on
that
board.
B
There
is
a
board
at
the
moment
that
exists
and
it's
called
release
roadmap,
and
it
is
one
board
and
I
want
to
keep
it
like
that,
and
that
way
you
can
see
everything.
That's
fine
for
the
release
stage,
especially
since
you
and
Ayane
aren't,
but
up
yet
so
you
can
get
a
bigger
picture
and
basically
I
think
you
could
check
there
by
filtering
either
by
design
or
by
UX
labels
and
see
what's
coming
up
for
both
groups.
D
And
a
comment
on
top
of
that,
but
the
board
I
think
would
be
a
very
good
accent
asset
for
us
to
have
a
better
sense
of
workload
and
also,
you
know,
I'll
just
think
ahead,
but
plan
ahead.
How
we
want
to
tackle
things
because
that's
the
thing
something
discussed
with
Jackie
yesterday:
that's
yeah!
If
we
split
that's
great,
but
what?
If
I
go
holidays
for
like
two
months,
it
can
happen
and
then
my
core.
D
D
I
mean
I'm
still
catching
up,
but
in
general
we
don't
have
a
way
indeed
blood
to
visualize.
We
don't
have
like
a
coma
board.
It's
everything
by
projects,
everything's
really
broken
down,
and
it's
a
yeah
there's
an
issue
to
fix
that.
But
even
if
you
have
personal
boards,
everything
changes
if
the
actual
board
or
the
label
changes
with
the
issue.
D
C
E
Was
this
what
we're
talking
about?
He
had
done
a
few
interviews
on
feature
flags,
but
we
hadn't
got
everything.
We
gotten
four
participants
in
two
of
them
work
right,
not
great
and
basically
continuing
that,
but
also
including
in
some
of
the
new
designs
and
actually
run
in
some
people
through
some
usability
tests
on
those
and
I
think
the
last
comment
on
it
was:
we
were
going
back
and
forth
was
when
we're
going
to
do
this,
and
my
answer
to
that
has
been
in
my
head
of.
Let
me
just
clear
out
the
12
stuff.
E
C
We
do
have
to
do
a
little
bit
of
pre-work,
because
if
you
plan
to
talk
to
anybody,
when
we
come
back
from
break,
we
need
Emily
to
start
trying
to
find
them
now
or
at
least
get
her
to
prep.
So
she
can
start
as
soon
as
she
gets
back
on
the
6th
of
January,
because
it
will
take
there's
a
reason.
We
only
have
that
many
people
to
talk
to
when
we
would
I
talk
to
them.
C
It's
gonna
take
a
while
to
find
people
and
if
we
need
to
get
this
done
and
rocked
up
by
the
end
of
twelve
seven,
which
is
like
what
the
18th
or
whatever
of
January
we're
gonna
need
to
start
at
least
thinking
who
do
we
want
to
talk
to?
How
many
of
them
do?
We
want
to
talk
to
and
get
Emily
going
on
that
because
otherwise
you're
gonna
be
you're,
not
gonna,
finish
top
seven
yeah.
E
C
E
Just
wood
needed
to
get
twelve
seven
stuff,
but
now
but
I
think
the
last
one
that
I
needed
is
pretty
close.
This
is
my
focus
so
today
and
tomorrow
really
looking
at
getting
a
plan
together
and
see
what
we
can
accomplish
and
again
with
the
holidays.
It's
gonna
be
what
it
is,
but,
like
I
said,
hopefully,
I
have
a
better
answer
tomorrow
than
I
do
today,
all.
C
E
And
the
upshot
is
I
mean
twelve,
seven
twelve,
they
would
be
great,
but
the
wave
feature
Flags
it's
kind
of
good.
Without
it,
there
is
work
being
done
in
twelve,
seven
and
twelve
eight,
but
it
it's
not
like.
We
can't
do
any
of
that
work
before
doing
that.
Obviously,
the
more
research
we
don't
run
for
cover
it
would
be
what
we
do,
but
there
is
lots
of
stuff
to
test
and
there's
lots
of
work
on
the
upcoming
milestones.
So
if
it
pushes
a
little
bit,
it
might
be.
Okay,
yeah.
C
B
B
C
B
D
Now,
for
a
total
of
8
right,
we're
talking
about,
we
have
an
issue,
a
link
here
and
also
in
the
docs
of
support
type
AWS
apartment
variables,
not
sure
how
much
research,
but
we
need
to
investigate
this
one
and
we
definitely
need
prototyping
and
there's
also
I,
think
configure.
Write
is
also
working,
something
related
right,
but
it
so
there's
an
overlapping
with
what
they're
doing.
How
far
are
they
I'm
not
familiar?
Do
you
know
what
it's.
B
B
B
B
D
But
I,
of
course,
the
this,
the
Reeboks
proposals
updated
and
I
think
we
need
to
validate
some
prototyping
and
check
with
what
the
other
teams
are
doing
and
I'm
not
familiar
if
they
are
doing
any
sort
of
validation
on
it.
So
if
they're
already
working
on
implementation
or
if
they
have
a
solution,
we
need
to
look
into
it.
But
my
gut
feeling
says
that
we
should
at
least
validate
the
prototype
and
Laurie.
Maybe
we
can
can
do
it
ourselves,
but
your
mentoring
is
awesome.
So
of
course,.
F
F
So
the
way
that
I
thought
about
it
is
we
would
give
two
months
to
conduct
all
of
our
research
and
validation
work
her
before
we
delivered
something
in
12.9.
So
we
started
the
research.
We
got
40
responses
to
our
survey
and
I'm
already
conducting
independent
interviews
with
different
users
and
accounts
with
Tam's.
So
that's
in
in
really
good
shape.
Right
now,
I
think.
A
All
right,
there
is
a
final
one,
so,
like
the
splitting
of
the
course
we
discussed-
and
there
is
a
final
item
on
the
list
about
the
same
big
session-
so
actually
I
just
wanted
to
suggest
if
we
should
start
doing
that,
but
apparently
Jackie
says
that
you
have
already
done
one
with
Ariana,
Nathan
and
John
I'm,
not
sure
if
we
have
enough
time
to
discuss
that
I
would
love
to
hear
more
details
on
that.
How
did
it
go?
Maybe
for
the
next
time
you
can
give
us
a
little
bit
of
a
pitch.
F
D
D
Maybe
not
maybe,
but
this
is
something
that
would
discuss
during
the
the
calls
that
you
know
for
us.
We
have
one
participant
like
one
specialist,
someone
from
tender
backhander
and
the
researchers
as
well
would
also
always
help,
but
this
one
was
for
release
management
and
I.
Think
that
what
we
did
like
discussing
the
the
overall
idea
of
release
management
was
really
valuable
because
we
have
all
the
the
assets.
A
Make
sure
that
I
will
go
through
that
thanks,
so
much
for
the
heads
up,
I
have
to
drop
to
the
next
session,
probably
as
many
of
us
as
well
yeah
I
will
go
through
this
yeah
think
big
sessions
exciting
to
hear
that
more
people
are
doing
that.
I
think
this
is
a
great
way
to
solve
issues
and
kind
of
like
do
the
collaboration
ideation
on
that.
So
it's
nice
to
hear
that
you
also
have
yeah
I,
don't
know
if
anyone
has
anything
to
add
a
little
last
minute.