►
From YouTube: Plan Stage Weekly 2021-05-26
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).
B
Yes,
so
I've
linked
to
a
planning,
epic
as
well
in
this
we're
going
to
have
a
big
refactor,
that's
happening,
starting
in
14-1,
I'm
sure
everyone's
aware
we're
converting
epics
onto
issue
types
as
well
as
figuring
out
the
core
model
for
issue
types,
apis
tracking.
All
of
that
good
stuff.
B
This
one
is
sort
of
the
hot,
the
top
level
tldr
for
what
we're
working
on-
and
this
is
our
planning
epic,
where,
where
the
goal
of
this
is
to
align
on
timelines
goals
and
what
we're
going
to
deliver
in
each
phase,
so
you
can
see
we
both
have
our
goals
and
our
risks
at
the
top,
and
then
we've
started
phasing
out.
What
would
the
next
six
months
look
like
if
we
start
building
a
roadmap
essentially
to
deliver
issue
types
for
that
will
support
epics.
B
This
is
up
for
discussion,
but
for
wednesday
june
the
2nd
I'm
going
to
do
a
kick
off
for
the
engineering
side,
where
we
we
can
set
a
rhythm
and
a
pace
and
figure
out
when
we
should
have
sync
meetings
when
we
should
have
deliverables
and
the
biggest
questions.
We
still
need
to
answer
from
the
engineering
team.
A
C
D
A
D
B
D
I
think
there
was
some
confusion
around
like
the
objects
themselves
and
whether
it
was
like
what
we
were
really
doing
and
calling
them
issues
was
hard
to
visualize
in
parenting
of
issues,
and
so
we
just
called
it
something
very
generic
that
it's
not
real,
even
though
the
api
will
probably
still
be
like
the
core
object
will
still
be
called
an
issue
under
the
hood.
D
That
might
not
be
what
we
call
ui.
Eventually
I
don't
know,
but
it's
a
code.
B
A
D
B
Have
any
of
the
phases
in
this
started?
Yet?
No!
This
is
just
the
draft
of
what
the
phases
are
so
well.
Sorry,
design
phase
has
been
ongoing,
so
it's
been
about
three
weeks
where
they've
been
iterating
on
what
would
a
simplified
issue?
Look
like
what
would
be
the
best
ux
for
this
new
issue
type.
That
would
be
the
shared
design
for
the
the
rest
of
the
objects,
and
so
we're
going
to
figure
out
some
design
deliverables,
so
they
can
start
presenting
those
back
to
the
team.
B
C
So
this
is
still
like
what
we
did
discuss
as
introducing
issue
types
widgets
relationship,
but
in
a
more
formalized
way
kind
of
thing.
Is
that
yeah
exactly
pretty
much?
Not,
I
don't
want
to
say
nothing
new,
because
it's
always
new
yeah,
but
it's
like
not
not.
What
is
there
something
significantly
different.
D
C
What
we
already
kind
of
yeah
wanted
to
introduce
and
to
do.
B
Not
from
an
engineering
standpoint,
what's
new
is
that
I
formally
pushed
back
all
of
my
category
maturity
in
product
planning
by
six
months
so,
like
I
took
that
we
have
skin
in
the
game.
So
now
we've
got
six
months
of
time
to
get
this
right
and
figure
it
out.
So
we
need
to
document,
kick
off,
get
all
of
our
ducks
in
a
row
and
get
a
plan
for
14
one.
So
we
aren't
spinning
our
wheels
once
we
start
into
the
next
release.
D
Yep
I'll
follow
up
with
that
and
just
say
it's
nothing
new!
Really
it's
and
I'm
gonna
push
off
my
stuff
as
well
like
pretty
much
working
anything
other
than
getting
figuring
out
this
foundation
so
that
migrate,
epics
can
migrate.
D
The
issue
type
hierarchy,
the
I
guess
the
key
thing
that
we
want
to
do
with
engineering
before
we
start
is
think
about
that,
like
putting
together
an
architecture
blueprint
so
that
everyone
can
work
efficiently,
asynchronously
in
a
distributed
manner,
all
like
understanding
where
we're
headed,
because
it
is
like
a
lot
of
moving
parts,
and
so
I
think
it
is
just
taking
the
informal
conversations
that
we've
had
and
formalizing
it
into
like
an
architecture,
blueprint
and
roadmap
to
implement
over
the
next
several
months.
A
C
I
just
want
at
the
current
time
do
we
have
any
action
items
that
we
need
to
act
on,
or
is
it
still
kind
of
being
planned
out
and
we're
in
the
process
of
deciding
how
we
want
to
proceed?
It's
like
it's,
not
it's
fairly
bad
to
me
like
what
me
as
an
engineer,
I'm
supposed
to
do
as
of
today
on
or
tomorrow
and
so
on.
B
In
general,
yeah
yeah,
the
next
step
would
be
show
up
to
the
kickoff
meeting
and
then
we're
going
to
work
on
breaking
down.
Essentially
what
needs
to
be
done
in
that
meeting
and
we'll
start
it
async
in
that
epic
that
I
linked
as
well.
B
A
Yeah
and
then
we'll
we'll,
take
this
time
now
during
14-0
to
kind
of
determine
how
we're
going
to,
because
there's
going
to
be
a
lot
of
collaboration
between
the
two
groups.
I
think
the
good
thing
about
having
this
defined
on
the
epic
or
on
the
product
planning
side
of
things
is
that
we're
kind
of.
A
I
don't
know
combine
both
of
the
groups
so
that
we're
all
kind
of
working
on
clabject
we'll
try
to
figure
out
if
that
means
like
product
planning,
will
really
work
on
just
the
epic
related
stuff
or
if
people
from
product
engineers
from
product
planning
are
going
to
be
working
on,
the
core
collab
checked,
object
but
yeah.
That's
that
we're
hoping
to
determine
all
of
that
and
how
that
splits
going
to
work
in.
A
A
Yeah
so
for
now,
there's
a
bunch
of
and
in
planned
weekly
from
two
weeks
ago,
gabe
linked
a
bunch
of
his
kind
of
vision
or
our
vision
and
direction
that
we
want
to
go
as
far
as
collaborate
or
co-object.
So
as
an
engineer,
I
would
start
reviewing
some
of
that
stuff
just
so.
A
You
have
a
a
core
understanding
on
on
what
we
want
to
do
and
where
we
want
to
eventually
be
at
and
then
any
questions
or
comments,
kristen
just
linked
to
the
epic
that
could
be
thrown
in
there
or
any
of
the
issues
or
epics
that
gave
created.
B
B
A
Cool
well,
if
no
one
has
anything
else.
I
just
put
a
note
in
there
created
the
social
channel
that
we
had
talked
about.
A
I
think
manage,
had
used
geekbot
to
feed
starter
questions,
but
charlie
brought
up
a
good
point
that
it
I
don't
know
it
feels
kind
of
not
too
different
than
our
stands.
If
we
use
geekbox
direct
messages,
so
maybe
we
just
someone
will
go
in
and
kind
of
feed
questions.
If
we
want,
I
don't
know
we
had
to
figure
out
a
way
to
to
handle
starter
questions,
but
are
in
that
join
the
channel.
Join
the
conversation,
we'll
social,
socially
talk
in
that.
In
that.