►
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
So
yeah
this,
the
the
master
on
an
issue-
words,
violence,
March
now
something
as
far
as
would
be
discussed
less
last
week.
There's
no
bill.
There's
been
no
changes
in
in
terms
of
a
thing
we
can
go
ahead
with
this,
as
as
the
embassy
essentially
I,
do
have
one
question
as
a
follow-up
and
that's
related
to
to
a
prep
for
the
team
captains.
A
Essentially,
I
was
going
to
file
the
demand
stones
at
marketing
level,
and
that
mentioned
is
to
to
the
now,
because
they
have
been
using
this
for
growth
and
for
corporate
as
well,
and
one
thing
that
she
was
asking
us
whether
we
was
whether
we
could
file
the
milestones
rather
than
at
the
marketing
level.
One
level.
B
A
Daniel
was
asking
you
got
the
number
because
certainly
manages
the
website
now,
and
they
would
want
to
use
the
same
set
of
milestones
for
that
as
well.
I,
don't
have
a
strong
opinions
on
these
I
think
it
would
be
tied
here
to
have
it
under
under
the
marketing
scope,
but
at
the
end
of
the
day,
if
there's
no
other
way,
they
can
arrange
their
and
their
project
I
think
we
should
facilitate
them
using
to
ask
for
your
thoughts,
I
think.
B
It
makes
I
again
like
I'm
a
mark
of
a
proponent
of
keeping
the
milestones
at
a
higher
level,
because
I
think
it
builds
a
cohesiveness
of
working
with
other
teams,
but
I
know
that
that
was
something
that
John
was
feeling
strongly
about.
Having
at
the
project
level
like
the
specific
group
level,
I
was
thinking
about
this.
On
my
like
I
ended
up
running
a
half
marathon
I,
just
like
was
thinking
about
the
project
management,
for
so
much
of
it
and
I
was
like.
Why
are
we
hitting
such
a
roadblock
and
I?
B
Think
it's
because
we
originally
weren't
planning
on
doing
milestones
at
all.
We
were
gonna
recommend
that
that,
as
a
phase
two,
and
so
when
that
became
a
requirement
for
the
scope
of
this
project,
it
introduced
a
really
big
theoretical
conversation
around
how
we
organize
milestones
and
how
we
work
as
a
team
and
how,
like
the
overarching
marketing
department
and
what
the
goals
really
are
of
this
project
like
right
now,
the
epic
still
had
I
actually
have
up
that
it
updated
it.
B
Yes,
something
I
thought
a
while
back,
but
like
working
cohesively
seems
to
be
the
top
priority,
which
is
what
Todd
mentioned
like
in
one
of
the
first
calls
less
so
the
the
like
executive
visibility
with
that
in
mind.
Well,
with
that
in
mind,
it
does
feel
like
they
should.
The
milestone
should
be
at
a
higher
level
and
work
as
they
use
all
the
teams
working
out
and
they're
the
same
milestone
and
then
using
the
issue
boards
to
be
able
to
break
those
out.
My
team
I
don't
know.
A
I
mean
to
me:
it's
also
getting
a
VC
out
of
the
door.
I
think
we
can
always
build
on
what
we
proposed
right
now.
I
mean
one
thing
to
consider:
is
it
if
we
need
to
move
milestones
and
if
we
need
to
move
issues
out
of
Matheson's,
it
might
be
a
bit
of
a
pain
and
lots
of
email
notifications,
but
I
think
we
shouldn't
constrain
ourselves
to
get
it
perfect.
A
The
first,
the
first
time
around
I'd,
rather
see
that
we
provide
something
that
simple
and
that
we
can
build
upon
that
so
yeah
I
mean
I,
don't
feel
strongly
to
be
honest
about
them
being
at
the
bottom.
As
long
as
we
use
them
consistently.
I
do
see
identity,
advantages
of
moving
I
think
on
this
particular
one.
A
We
agreed
last
week
that
we
would
be
doing
them
at
at
the
top
and
then
John
actually
Marie
said
that
that
in
March
I
think
we
just
committed
to
disagree
on
this
one
and
to
essentially
see
what
week
that
we
get
from
much
fuel
usage.
From
from
that
we
might,
we
might
end
up
regretting
the
decision
if
that
doesn't
work.
B
B
A
B
A
B
C
I
think
the
confusion.
Well,
we
we
have
customers
reminded
us
all
the
time
when
we
use
the
word
for
those
of
us,
not
engineers.
When
we
say
project
we
mean
like
an
agreed-upon
chunk
of
work,
to
accomplish
a
goal
right.
What
happens
in
our
product
is
when
we
say
project
folks
immediately.
Think
repo,
because
that's
how
we
have
the
product
structured,
so
I
think
just
make
sure
we're
clear
on
what
turned
reason
there,
when
you're
communicating
just
yeah.
B
B
C
C
B
B
A
B
C
They're,
a
different
flavor
of
milestones
right,
so
at
high-level
milestones
will
operate
like
we've
been
using
them
in
the
product
or
having
the
product
for
now.
Iterations
is
going
to
add
in
additional
data
on
tracking
work
completed
inside
of
that
spring
up
with
some
better
analytics,
but
I
mean
it
essentially
is
just
a
another
milestone
implementation,
but.
C
B
A
And
when
one
thing
to
to
mention
and
I'll
just
mention
it
as
what
sort
of
it's
under
on
the
record
is
that
as
far
as
I
understand,
once
we've
cooked
milestones
and
iterations
as
a
feature
then
we'll
be
able
to
have
let's
say:
we've
got
an
issue,
and
that
issue
is
part
of
the
overarching
milestone
and
also
a
part
of
that
of
the
of
the
iteration
right
now
as
we're
not
using
iterations.
We
cannot
get
have
that,
so
we
cannot
have
initially
both
part
of
the
overarching
muscle
and
the
iteration
yeah.
B
A
B
A
C
A
I
was
actually
going
to
mention
something:
there's
also
the
ability
of
measuring
better
as
well,
because
one
of
the
things
that
we're
doing
in
those
guidelines
is
discouraging
people
to
have
multiple
or
nautical
or
long
lists
of
a
lot
of
checklists,
essentially
and
of
actual
issues.
And
then
we
can
see
when
these
are.
A
B
And
I-
and
maybe
we
can
take
this
as
like
a
different
call,
Keenen
or
like
if
you
can
join
to
I
I-
want
to
touch
back
on
that
project
that
you
were
describing
in
a
call
like
a
week
or
two
ago,
where
you,
you
I,
think
you
were
mentioning.
You
could
have
issues
for
different
projects
built
into
like
a
template
and
then
cloned
as
projects
like
the
get
lab
technical
project.
It.
C
C
B
B
B
I
know
it's
kind
of
a
reflection
of
what
John
has
in
his
Google
Doc,
but
it's
Google
Doc
epic
issue
creation
works,
because
when
he's
opening
those
they're
all
in
the
same
project,
but
when
I
or
when
my
team
is
doing
campaigns,
they're
opening
in
like
every
project,
so
we'd
end
up
having
to
do
the
upload
multiple
times,
and
it
almost
is
just
as
easy
to
follow
the
manual
steps.
So
I
wanted
to
try
like
out.
If
projects
could
actually
do
some
of
what
I
would
need.
B
A
B
A
A
B
A
A
A
The
next
one
just
quickly,
the
next
point
on
the
guidelines
for
Matt
and
Jackie
I-
think
it's
about
that.
The
tomorrow
that
you
filed
and
the
question
was
whether
willing
to
have
the
explanation
of
the
future
recommended
as
the
first
section
or
at
the
last
section
to
me.
I,
don't
really
mind
where
what
it
is
that
was
actually
formatted.
The
term
proposed
I
find
it
useful
to
have
it,
but
regardless
of
where
it
is
and
I
think
we
should
use
the
consistent
format.
B
I'd
be
a
proponent
for
putting
the
how
we
actually
are
using
the
feature
at
the
top
of
the
page,
because
the
point
of
the
page
is
to
understand
how
marketing
is
using
the
different
pieces
of
project
management
and
I
I
feel
like
a
lot
of
people
might
get
really
like.
Did
you
get
into
the
weeds
on
the
actual
product
functionality?
B
You
can
get
kind
of
lost,
but
if
you
just
need
to
know
what
assess
is
you're
using
or
labels
using?
How
are
we
using
epics?
How
are
using
issues
I
think
it
will
cause
less
confusion
as
someone
who's
not
as
deep
in
the
weeds
on
knowing
the
product
functionality.
That's
just
how
I
I
think
most
of
marketing
wait.
Yeah.
B
A
Yeah
I
mean
I
think
for
some
for
some
things
it
might
be
more
critical
than
others
to
understand
whether
a
pig's
can
be
filed
that
groups
only
not
at
projects,
for
instance
that
might
be
critical
for
someone
to
to
know,
but
at
the
same
time
we
can
always
point
them
to
the
commendation.
I
don't
feel
strongly
about
it.
I
mean
if
you
feel
that
that
we
should
I
mean.
A
B
So
superfluous
that
like
searching
just
to
get
there,
so
we
can
always
just
keep
it
as
is,
and
that
could
be
a
question
for
feedback
and
see
if
they
agree,
because
three
things
we
do
need
to
flag,
and
maybe
we
could
like
the
pin
he
directives
for
those
pieces
like
that.
That's
a
really
critical
one!
If
you
put
it
up
the
too
low
of
a
level,
you
can't
it's
so
hard
to
move
it.
You
have
to
open
somewhere
else.
B
A
A
C
I
believe,
if
that's
not
part
of
the
initial
MVC,
that
is
a
fast,
follow
Gabe's
planning
on
yeah,
because
I
mean
the
whole
whole
idea
for
iterations
is
team-based
development.
So
we
need
it
at
the
issue
board
level
for
it
really
to
to
matter
to
the
right
people.
But
let
me
follow
up
on
that
see
if
there's
a
specific
issue.
A
A
A
B
Okay,
I
kind
of
a
kind
of
plant
or
discuss
that
earlier
in
the
call
just
about
like
milestones
really
that
was
increasing
the
scope
significantly
for
this
campaign
for
this
marketing
project,
not
from
a
seed
project
and
so
I
I
think
when
it
comes
to
like
did.
We
do
be
complete
the
agility
project
because
we
do
end
next
week.
I
would
say
status
is
like
we're
close
I,
don't
even
I,
don't
even
think
I
want
to
yet
give
this
over
to
Kent
captain's
until
we're
really
confident
that
we're
ready
for
them,
but
I,
don't
know.
A
Was
following
the
same
train
of
thought
as
you
were
then
again,
I
think
I've
changed
my
mind
and
I
think
we
should
just
realize
and
be
honest
that
that
this
is
an
MVC.
It
will
be
rough
RT,
HS
I'm,
not
just
at
the
edges,
but
I
think
it'd
be
good
to
get
it
in
the
eyes
of
the
of
the
team
captains.
Even
if
they
tell
us
this
is
actually
not
working.
Alright,
then
we'll
have
some
some
more
focused
feedback
on
things
that
we
should
definitely
address.