►
From YouTube: Plan stage weekly meeting - 2019-11-13
A
Oh,
okay:
this
is
the
plan
stage
weekly
meeting
for
the
13th
of
November
2019,
I'm
Shaun
and
the
engineering
manager
for
the
project
management,
back-end
team
looks
like
I've
got
the
first
item
on
the
agenda,
which
is
just
that
Gabe
to
the
project
management
p.m.
posted,
the
kickoff
video,
which
is
about
five
minutes
long.
So
it's
pretty
quick
watch
if
you
want
to
check
it
out
and
see.
What's
going
on
that
sort
of
covers
what
he's
put
in
the
release
planning
issue
as
well
for
project
management's,
we're
doing
a
lot
of
work
on
milestones.
A
Basically,
you
sort
of
need
to
ship
together,
which
is
milestone
types
of
multiple
milestones.
So
we
want
to
allow
multiple
milestones
on
an
issue
or
merge
request,
but
only
where
they
have
different
types
and
types
of
user-defined.
So
we
could
ship
types
first,
but
it
doesn't
really
do
anything.
And
then,
if
we
shipped
multiple
milestones
first
without
shipping
master
and
types,
then
you
know
you
could
end
up
in
an
unbalanced
State
once
you
started,
adding
milestone
types
and
then
burn
up,
charts
are
kind
of
a
slightly
side
thing,
but
obviously
still
related
to
milestone.
A
So
basically
we're
gonna
spending
a
lot
of
time
on
milestones,
coming
up
and
then
there's
some
sort
of
future
things
I
listed
in
the
dock
as
well.
So
you
know
making
the
sidebar
update
in
real
time
having
the
issue
boards
API
supports
in
graphic
URLs,
so
that
the
front-end
refactor
can
use
that
and
some
design
work
on
first-class
tests
within
issues.
So
you
know
at
the
moment
we've
got
tax,
listen
markdown.
This
would
be
sort
of
an
enhancement
of
that,
probably
not
using
markdown
syntax
of
the
way
you
create
them.
A
Yeah
sorry
I
should
have
mentioned.
The
reason
Gabe
did
this
earlier
is
because
he's
some
yeah
he's
a
person
yeah
he's
on
the
CEO
Shadow
program
at
the
moment.
So
he's
like
you
know,
he's
working
the
next
couple
of
weeks,
but
he's
he's
not
working
on
his
day
job.
Most
of
the
time
there
so
yeah
Sean.
A
Be
yes,
so
I
think
the
example
I've
been
thinking
of
these
is
like
you
might
have,
and
we
might
do
this.
For
instance,
we
might
have
a
milestone
for
a
sprint
and
a
milestone
for
a
release.
So,
like
you
know
one
of
the
confusion,
confusing
things
we've
had
in
the
past,
it's
not
so
confusing.
Now
that
our
deployment
process
is
more
continuous
but
like
in
the
past
we
sort
of
had
a
development
month
that
wasn't
exactly
aligned
to
when
it
released,
because
we
had
a
feature
freeze
at
the
end.
A
So
you
know
we
might
be
an
issue,
might
be
a
regression
in
12.5
and
we're
working
on
it
in
the
12.6
sprints
that
giving
the
same
name
and
having
the
same,
like
object
used
for
both
of
those
is
kind
of
confusing,
there's
also
some
user
feedback
in
the
multiple
milestones
per
issue
issue
that
that
gives
some
other
examples
of
where
they
might
want
to
use
that
and
we're
sort
of
discussing,
starting
with
these
constraints
and
then
potentially
relaxing
them
in
future
and
do
that
their
help.
Yeah.
C
The
reason
I
ask
is
what
we're
doing,
at
least
on
the
marketing
sides
were.
Were
you
sorry?
We
use
milestones
much
more
assertively
to
manage
both
teamwork
and
backlog,
work
within
the
team
and
strategic
marketing,
but
I've
just
started
running
to
the
case
where
same
issues
are
being
included
in
other
teams
milestones
and
all
of
a
sudden.
C
C
C
A
And
actually
backlog
could
be
a
type
of
milestone
as
well.
Now
you
mention
it
because
you
might
want
to
state.
You
know
we
have
these
milestones
that
I'm
personally,
not
a
huge
fan
of
where
they
say
sort
of
next
three
to
six
releases
and
obviously
that's
kind
of
like
the
Alice
in
Wonderland
Jam.
Tomorrow
thing
where,
like
you
know,
you
never
start
on
it,
because
it's
always
three
to
six
releases
away,
but
you
could
say
that's
a
backlog,
type
of
milestone
as
well.
So
yeah
I
think
Gabe's
thought
about
this.
D
B
C
And
probably,
what
we've
been
doing
so
far?
This
is
our
first
iteration
of
focusing
on
milestones
as
a
way
to
manage
our
backlog
in
our
work.
We
have
a
quarter.
We
have
a
milestone
for
the
quarter.
Basically,
so
we
can
get
to
the
end
of
the
quarter
and
say
how
have
we
done
with
all
the
things
that
people
asked
us
to
do
and
we're
seeing
how
that
works
so
I'm
eager
to
see
us
come
together
so.
D
D
So
we
thought
a
little
deeper
about
this
and
where,
where
we
might
start
and
we're
thinking
and
I
won't
speak
for
Gabe,
but
starting
with
milestone
types
might
be
a
little
bit
easier
for
users.
They
can
go
in
probably
in
settings
again.
This
is
pretty
rough
too,
but
since
it's
a
group
level
setting
and
it's
something.
D
Especially
when
they're
deleting
these
milestone
types,
we
want
them
to
calculate
of
what
that
means.
So,
probably
settings,
maybe
some
permissions
there,
they
go
into,
let's
say
milestone
types:
their
default,
milestone
type
is
milestone.
So
when
they
go
into
an
issue,
they
don't
see
any
difference
there,
but
they
can
add
up
to
five
milestone
types
again
rough,
but
I
was
thinking.
We
could
do
something
along
the
same
vein
as
labels,
so
I
go
in
there
I
could
set
my
own
type.
I
could
set
a
description.
I
can
edit
it
deleting.
D
It
is
probably
the
trickiest
thing:
I
think
Shawn's
even
talked
about
this,
but
what
does
that
mean
if
they
delete
it,
because
then
that
takes
it
out
of
any
milestone,
that's
using
it
and
also
take
it
out
of
issues.
So
we
have
to
be
really
really
explain.
What's
going
on
there
and
I'm
still
thinking
through
that,
a
bit
yeah.
A
We're
still
discussing
that
in
the
issue,
I
think
late
because,
like
you
could
say,
like
deleting
a
milestone,
type
deletes
all
the
milestones
of
that
type,
but
that
might
be
a
bit
unexpected,
but
the
problem
is:
if
we
just
make
them
all
the
default
type,
then
it
might
put
some
issues
into
an
invalid
state.
So
yeah
we
might
pun
on
that.
Officially
yeah.
A
Alexis
that,
thanks
for
that
and
with
the
idea,
then
the
easier
way
to
add
multiple
milestones
would
also
come
to
labels
in
future,
because,
like
labels
and
milestones,
would
have
the
same
kind
of
like
you
know,
you
can
add
multiple
of
those
both
of
those
to
an
issue
right
now.
So,
like
I'm,
the
sorry
on
the
issue,
sidebar
view
not
on
the
settings
for
you
and
when
you
were
talking
about
how,
like
the
experience,
wasn't
a
great
right
now,
you.
A
I
was
just
saying:
if
we're
gonna
make
any
enhancements
here
like
how
these
drop
downs
work.
Would
we
then,
like
feed
those
into
the
labels
drop-down
in
future?
We're,
like
you
know,
you
have
a
similar
kind
of
setup
and
I
think
we
have
some
issues
with
how
that
works
at
the
moment
like,
for
instance,
there
you've
got
their
little
X
next
to
the
milestones
to
allow
you
to
remove
them,
whereas
to
remove
and
label
from
an
issue.
A
D
D
D
D
D
D
It
would
have
to
be
a
sweeping
change,
so
we're
thinking
a
little
more
deeply
into
dropdowns
in
general,
for
instance,
kind
of
cleaning
them
up
here
so
that
there's
not
a
bunch
of
inputs
of
the
chopped
down
I,
don't
know
if
you'll
notice
that
but
there's
a
of
applied
labels
on
this
drop-down.
So
just
thinking
sweeping
changes
to
the
sidebar
I
think
we're
stepping
back
and
thinking
about
how
to
prove
that.
D
So
I'm
not
exactly
sure
how
we're
gonna
proceed
with
the
that
little
X
in
the
sidebar
right
away,
but
yeah
we're
thinking
about
it
and
I
would
say
that
if
we
improve
it
there,
it's
definitely
gonna
fly
to
you,
labels
and
other
various
parts.
There
I'm,
probably
working
with
create
and
other
designers
as
well
just
to
make
sure
they're
involved
in
the
sidebar
changes.
That
was
a
long-winded
answer
to
your
question.
Sean
I
need
coffee,
no.
C
That
seeing
that
it's
grateful,
no
no
I
agree
totally
helpful,
really
good
to
see
and
I'm
gonna
I'm
gonna
reach
out
to
ty
Davis
I.
Don't
have
ties
on
the
call
or
not,
but
I
want
to
make
sure
that
he's
ahead
of
the
game
on
building
out
demos,
to
help
tell
the
story
around
this,
because
this
is
a
big
change
and
being
able
to
describe
and
showcase
how
we
think
people
should
do
it.
I
think
will
be
important
rather
than
just
saying
here's
a
cool
feature
go
figure
out
what
to
do
with
it.
I
think.
A
E
Yeah
just
cause
there's
two
John's
on
the
collar.
So
how
did
the
modifier
a
swift
change
of
pace?
The
internship
working
group
has
completed
exited,
whatever
met
its
exit
criteria
and
it's
pushing
up
the
daisies,
so
we
might
want
to
think
about
taking
on
an
intern
it's
sort
of
time
to
correlate
with
the
end
of
the
US
and
European
school
years.
So
it
might
appeal
to
graduates
more.
It's
a
pilot
scheme.
E
There
are
four
places
for
interns
and
all
that's
being
asked
of
teams
that
ask
for
interns
is
that
they
can
provide
one
mentor,
possibly
two
and
there'll,
be
a
kickoff
in
Amsterdam
the
interns
to
be
flown
times
to
them
and
then
there'll
be
a
wrap-up
I
believe
in
San
Francisco.
So
pretty
cool
experience
you
asked
me
or
for
anyone
straight
out
of
college
and
so
yeah
like
basically
there's
a
Google,
Form
and
I.
A
F
F
We've
got
a
number
of
issues
that
have
been
open
or
open
about
this
to
try
and
get
our
heads
around
how
this
is
gonna
work,
but
basically
I
kind
of
get
my
head
around
sort
of
what's
happening
in
next
releases
and
bid,
subject
matter
expert
for
on
project
management
and
somehow
feedback
kind
of
what
we
find
out
in
support
from
customers
about.
What's
going
on
what's
going
badly
and
so
on,
I
think.
A
F
F
Continuous
integration
functionality
and
he's
had
a
lot
of
really
good
feedback
about
them,
proving
the
docs
he's
found
some
bugs
I
found
some
more
bugs
reproducing
his
bugs
and
yeah.
He
pp-put
some
feedback
into
an
issue
that
put
up
management
ways
to
round
making
that
part
the
product
more
lovable.
So
that
would
be
an
example
where
you
know
we
might
be
able
to
identify
customers
that
were
more
than
happy
to
get
involved
in.
A
F
A
Yeah
no
great
well
we'll
see
you
in
future
meetings,
I,
guess
and
welcome.
Yep
I
think
that's
everything
from
the
agenda.
Unless
someone
added
some
after
I
switch
tabs
away
nope,
that's
it
okay,
great
well!
Having
fun
testing
week,
everybody
and
I'll
speak
to
you
all
soon.
I
like
this
once
I've
got
the
recording
thanks
clay
right.