►
From YouTube: Plan stage weekly - 2021-06-17
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
Yes,
I'm
in
all
right
welcome
plan
stage,
weekly
apac
edition.
What's
the
17th
of
june
charlie
epic
boards.
B
Yay
hooray
for
epic
boards,
so
I
I
think
between
backhand
front
end
and
docks,
I
think
and
and
release
post,
which
I
noticed
that
you
merged
earlier.
I
think
that
epic
boards,
we
are
good
to
go.
C
B
Yeah
yeah,
so
I
think
we've
got
we
sort
of
touch
base
with
each
other,
every
every
so
often,
and
so
we
kept
our
eye
on
the
prize
and
and
we
got
there
and
nobody
burnt
out.
B
I
think
that
we
did
it
in
a
way
that
was
well
paced
and
you
know
we
communicated
well,
and
so
I
think
it
went
really
well.
I
think
we
could
probably
have
a
retro
anyway.
I
figured
that
that
comparing
this
one
with
with
swim
lanes,
I
thought
I
thought
we
were
much
more.
B
I
don't
know
feature
focused
yet
yeah,
also
well
paced
and
I
think
making
sure
that
everyone
was
okay
and-
and
there
wasn't
too
much
on
the
on
the
plate,.
D
I'm
I'm
I'm
really
happy
with
the
way
it
went
and
yeah
like
you
mentioned,
swim
lanes.
We
are
we
we
we've
learned
from
that
and
we
did
better
yeah.
It
was
good
to
not
be
on
a
crunch
for
six
months,
so
that
was
good
and
yeah.
I'm
really
happy
also
with
like
not
crunching,
also
means
that
I
think
we
are
actually
delivering
something
of
higher
quality
compared
to
swim
lanes
as
well.
D
B
D
So
yeah
I'm
looking
forward
to
feedback,
but
I'm
optimistic
like.
D
D
B
Think
having
one
dedicated
for
when
everybody
sees
it,
so
it's
just
yeah
we
can
close
the
other.
It's
a
good
point.
It's
a
good
point.
A
That's
a
good
idea,
yeah.
So
that's
one
part.
I
think
we
should
still
have
the
retro
on
epic
boards.
Retro
can,
of
course,
be
positive
things
too,
because
we
want
to
take
what
we've
learned
from
epic
boards
and
apply
that
for
some
of
the
future.
Things
like
plant
objects
that
you've
listed
out
there,
which
is
great
but
yeah
overall,
great
job
team
with
epic
boards.
It's
super
exciting
to
have.
A
I
was
talking
about
flori
about
this
earlier,
but
just
having
like
normally
there's
that
that
huge
rush
to
get
everything
out
right
before
the
end
of
the
milestone,
and
with
this
one
we
had
like
a
couple
days
to
really
make
sure
the
docks
were
were
were
great
and
the
release
post
was
all
short
up
and
good,
which
is
nice.
It's
a
nice
change
and
then
yeah
overall,
just
the
like
epic
boards
feels
even
though
it's
technically
the
first
innovation
it
feels
solid.
A
You
know,
like
flory
said
we
haven't
gotten
a
whole
lot
of
like.
There
are
a
lot
of
beta
users.
We
haven't
gotten
a
whole
lot
of
bug,
issues
or
critical
feedback
on
on
on
the
feature
which
is
good
to
see.
I'm
excited
to
see
the
feedback
that
we
get
now
that
it's
out
to
more
people.
I
posted
a
science
link
in
the
channel
that
is
tracking
the
pageviews
on
gitlab.com
to
any
epic
board.
A
It
was
interesting
to
see
the
jump
for
when
we
turned
it
on
for
dot
com
that
went
from
like
70
a
day
to
like
500,
and
then
it
dropped
for
the
weekend.
But
then
it
was
up
again
this
week
and
I'm
really
excited
to
see
how
how
high
it
jumps
up
once
we
announce
it
in
the
release
post
because,
like
kristin's
been
saying,
this
is
a
hugely
requested
like
it's
a
number
one
clicked
preview
item
in
the
release
post.
So
I
think
there's
like
that.
B
There
was
some
there
was
talk
about
having
a
like
a
ticker,
so
we
can
get
a
live
sense
of
how
things
are
going.
I
think
that
would
make
it
really
real.
I
don't
know
it's
not
really
needed
and
we
could
always
just
go
click
here
and
look
and
then
you
can
see
it
going.
A
Over
engineer
that
the
yeah,
so
then
I
asked
a
couple
questions
around
like
the
table,
because
we
don't
have
that
information
in.
We
don't
have
that
table
in
sci-sense.
Yet
I
have
a
request
from
the
data
or
to
the
data
team
to
add
that
so
once
that's
added,
hopefully
we
can
do
a
ticker,
maybe
there's
not
a
whole
lot
of
like
you
can't
embed
charts
from
size
sense,
so
we
might
have
to
do
something
else
like
use,
grafana
or
something
else:
okay,
but
yeah.
B
Would
be
cool
to
do
it
in
grafana,
like
I
don't
know
for
anyone
else
like
me,
who's
sort
of
learning
how
to
do
things
in
grafana,
not
just
look,
and
you
know,
and
cite
and
whatever,
but
to
actually
make
stuff.
That
might
be
a
really
interesting
exercise.
B
B
A
Yeah,
I
agree,
and
we
should
do
we've
been
talking
also
about
having
like
we
should
celebrate
big
wins
like
this.
Well,
we
should
celebrate.
We
should
celebrate
more
wins
than
we
do
so,
if
you
all
can
think
of
some
way
to
celebrate
this
by
like
having
another
game
day
or
or
something
like
that,
we
should.
We
should
definitely
do
something
yeah,
let's
have
a
team
day,
yeah.
B
All
right
we'll
organize
a
team
day,
great
cool,
so
so
that's
done
anything
else.
We
want
to
sign
jonatha
for.
B
Okay,
you're
lucky
this
time:
okay,
anyway,
that's
that's
really
it!
It
was,
was
sort
of
getting
getting
that
out
there
and
official
and
and
seeing
if
there's
anything
else
we
need
to
do
after
after
it
goes
out
other
than
the
usual,
the
usual
make
sure
nothing's
on
fire
kind
of
stuff.
F
B
B
F
B
Access
to
indo
stuff
yeah,
definitely,
but
this
this
one
I
think
is
is
is
more
enthusiastic
than
than
normal.
I
think
I
think
the
the
fact
that
it's
been
so
hyped
for
so
long.
I
mean
not
because
we're
like
yeah
yeah,
if
it
wasn't
going,
but
it's
more
like
yeah
we're
working
on
it,
we're
going
we're
going
as
fast
as
we
can
and
people
are
like
come
on,
come
on,
which
I
totally
get
it's
it's
it's
very
exciting
and
it's
a
it's
a
cool
feature.
So
I'm
glad
that's.
B
D
C
B
B
Cool
yeah,
great
cool,
so
yeah,
so
I'm
happy
with
that.
So
I
don't
know:
do
we
have
like
a
post
big
feature
thing
like
processing?
I
don't
like
when
I
say
fast,
I
don't
mean
formal
process
for
when
you
put
out
a
feature.
Do
these
things
it's
more
like,
like
a
team
culture
thing
you
know,
like
you
know
how
to
celebrate
cool
things.
A
Yeah,
no,
I
don't
think
we
have
a
any
kind
of
formal
thing,
but
we
should
like
within,
like
I
said,
like
we
should
be
celebrating
not
just
the
big
things
like
this,
but
we
should
be
celebrating.
B
B
Yeah
exactly
so
who's
going
to
be
the
tri
for
doing
that.
F
B
Okay,
great
with
that
for
celebrating
wins.
I
guess
I
guess
more
reliably
is
the
wrong
word,
but
yeah
like
more
consistently,
I
suppose
yeah
yeah,
okay
cool,
so
now
you're
in
the
agenda,
it's
official!
Thank
you.
Thank
you
for
volunteering
you're
safe
this
time,
john.
A
Simon
to
your
point
about
turning
on
the
feature
flags
as
kind
of
a
way
to
allow
for
beta
access,
I
don't
think
we've
done
it
within
plan
before
I
think
other
teams
may
have
done
it
honestly.
I
hope
we
don't
do
that
again
or
I
hope
we
don't
do
it.
That
way
again,
like
beta
features.
Slowly
releasing
out
to
users
is
fine
using
feature
flags
for
that.
I
don't
think
is
the
best
way
to
do
that.
It's
just
like
with
epic
boards.
A
It
was,
it
came
in
a
request,
one
person
or
a
couple
people
went
in
and
just
added
it
to
chat
ops.
I
was
always
afraid
that
I
was
going
to
mess
something
up
and
remove
every
single
group
from
that
beta
list
and
then
to
add
them.
All
back
would
not
have
been
super
easy
using
chat.
Ups,
so
yeah
I
mean.
Maybe
we
we
think
through
a
different
approach
to
release
betas.
A
D
So
I
had
like
a
really
like
close
loop
of
feedback
right
away
to
see
how
they
were
using
it,
what
they
were
expecting
from
it,
what
issues
they
were
having
with
it.
What
was
important
to
them,
so
maybe
future
flags
are
not
the
best
way
and
we
can
find
another
way
to
do
it.
But
I
just
want
to
point
out
that
it's
extremely
valuable
to
be
able
to
have
instant
feedback
on
a
feature
that
is
currently
in
development.
F
D
Yeah,
maybe
we
went
a
bit
too
far
in
the
number
of
customers
we
gave
it
to,
and
I
understand
this,
the
enthusiasm
and
it's
hard
to
say
no,
but
like
the
like
doing
it
with
someone,
you
work
with
closely
is
hugely.
A
Yeah,
I
definitely
agree
it
is
valuable,
like
we
should
definitely
have
the
beta
process
of
select
users
having
early
access.
It's
just
a
matter
of
the
process
by
which
we
do.
A
That
I'm
trying
to
think
if
yeah,
if
there's
any
other
way
that
we've
been
thinking
through
doing
that,
I
don't
know
if
there
is,
but
it
would
be
nice
to
have
a
different
way
outside
of
feature
flags
to
do
that.
B
B
B
Who
do
we
connect
with
to
make
that
happen,
because
I
know
that
there's
like
there's,
there's
like
ux
research
and
there's
and
stuff
like
that,
where
we're
there
and
design
our
designers
and
stuff
like
that,
so
there's
there's
vectors
for
that,
but
I'm
wondering
how
how
we
make
that
into
a
reality
to
explore
that
space
to
see
what
what
what
we
could
do
in
that
to
make
it
actually
actionable.
A
A
B
B
I
can't
talk
in
time
at
the
same
time.
Nor
should
you
try,
because
I
think
it's
yeah,
but
yeah
thanks
for
that.
I
just
I
wouldn't
want
us
to
be
like.
Oh,
we
should
do
this
again.
It
just
kind
of
falls
off
the
wagon.
I
think
it's
it's
nice
to
follow
these
things
up,
even
if
it
doesn't
go
anywhere
yeah.
Thank
you
for.
B
B
Oh,
this
is
just
sort
of
an
fyi
that
I'm
so
I'm
I'm
currently
working
on
migrating
the
requirements
database
table
so
right.
Now
it's
a
first-class
object.
It's
a
it's
its
own
objects
or
some
kind
of
type
of
object,
and
what
I'm
doing
is
I'm
migrating.
B
Those
requirement
objects
to
an
issue
type
requirement,
so
it
will
be
a
requirement,
but
it
will
actually
be
an
issue
underneath
yeah
underneath
so
I
just
wanted
to
let
people
know
what
I'm
doing
and
what
I'm
doing
right
now
is
kind
of
in
the
background,
and
the
idea
is
to
deprecate
the
requirements
api
in
six
months
or
whatever,
and
then
people
can
use
the
the
issues,
api,
the
graphql
or
rest
api
in
order
to
get
what
they
need
and
they
can
just
specify
the
type
of
requirement
and
this
kind
of
ties
into
the
broader
plan
objects
discussion,
but
it's
more
of
an
fyi
rather
than
any
discussion
really
needed
unless
anyone
wants
to
ask
stuff,
but
I'm
just
I'm,
I'm
keeping
there's
an
issue
and
I've
got
a
road
map
on
the
issue,
for
that
particular
thing
and
jan
and
felipe
are
working.
B
I'm
working
with
those
two
closely
on
that
and
jan
is
doing
sort
of
more
the
logic
change.
So
once
we
once
we
do
the
background
migration,
then
there's
going
to
be
some
logic,
change
to
make
sure
that
all
the
all
those
things
so
the
requirement
objects
themselves
will
become
more
of
a
proxy
to
the
actual
issues.
So
when
you
say
oh
give
me
a
requirement
I'll
be
like.
Oh
here
have
an
issue
that
looks
like
a
requirement
because
they,
basically
a
requirement,
is
an
issue
with
a
lot
fewer
fields.
B
It
has
a
you
know
a
title
and
a
description
and
stuff
like
that,
but
there's
not
heaps
different
and
we
just
have
to
switch
some
stuff
off.
So
that's
really,
that's
all
it
is,
and-
and
I
wanted
to
to-
and
I
might
I
might
be
also
working
on
widgetizing-
the
sort
of
working
on
a
little
bit
of
widgetization.
B
So
it
really
means
that
there
are
certain
facets
that
are
available
only
to
certain
types.
So,
for
example,
assignees
I'm
not
working
on
assignments,
but
assignees
are
only
only
available
on
on
issues
but
not
like,
for
example,
test
cases
and
that's
another
type
of
issue,
so
we're
basically
switching
stuff
off
and
on
and
we're
including
certain
things
for
certain
types
of
issues,
so
that
becomes
kind
of
a
and
so
I'm
sort
of
scratching
away
at
that
surface
area
of
that
problem,
and
I
just
wanted
to
bring
awareness
to
what
I
was
doing.
B
Here's
the
I'll
just
plonk
the
issue
here
and
that
has
actually
what
I'll
do
is
I'll
I'll.
I
put
in
a
sort
of
a
road
map
to
completion.
I
don't
think
that's
the
right
word
to
use,
because
we
already
have
a
roadmap
feature
that
okay,
so
that
has
that
completion,
and
it
just
has
a
list
of
mrs
that
I'm
doing
and
what
each
one
is
doing.
And
so
that's
like
how
I
plan
to
finish
this
and
I
want
to
make
that
more
widely
available.
B
So
everyone
can
be
aware
of
what's
happening
and
if
and
if
anyone
says
no
don't
do
that
because
it's
a
terrible
idea,
then
they
can
tell
me
so
so
I
don't
do
something
weird
or
that's
going
to
make
things
very
difficult
in
the
future,
because
it's
such
a
big,
huge
problem.
F
This
is
great
I'm
I
I
like
one
of
my
kind
of
I
understand
the
irony
of
not
bringing
it
up,
but
it's
like
one
of
my
reservations
about
the
what
are
calling
them
issue
types
general
thing,
just
like
big
vague
problem
is
that
it
can
feel
too
big
and
we're
just
kind
of
you
know
we'll
solve
everything
perfectly.
The
second
time
we
try
it.
A
F
Rather
than
this
is
like
a
more
let's
solve
the
smaller
problem,
that
is
a
part
of
this
and
kind
of
see
what
happens
so.
We
kind
of
yeah,
just
like
you,
said,
chip
away
at
parts
of
it
and
get
to
do
a
lot
of
the
things
we'll
have
to
do
more
completely.
B
Yeah,
so
I
feel
like
felipe,
has
already
done,
work
with
test
cases
and
so
test
cases
are
part
of
issues
and
he's
and
he's
also
implemented.
I
think
we
can
switch
off
certain
things,
and
so
some
of
that
work's
already
been
done.
So
to
me,
the
requirements
table
is
the
next
step
in
that,
so
it's
kind
of
like
baby
steps,
but
I'm
definitely
standing
on
his
shoulders
for
this
one.
So
I
appreciate
the
work
that
he's
put
in
already
and
and
jan
has
been
really
amazing,
as
well
with
his
guidance.
A
B
It's
kind
of
the
direction
we're
going
yeah
cool
and
then
we
can
optimize
the
heck
out
of
it.
I
suppose
yeah
cool,
because
so
many
things
just
acted
like
an
issue.
B
They're
going
to
do
the
same
thing,
they're
going
to
become
an
issuable
as
well
and
and
well
an
issue
underneath
under
the
hood,
and
then
you
know,
they'll
have
all
those
different
things
switched
on
or
not
switched
on,
and
then
we're
gonna
be
able
to
have
things
associated
with
any
other
thing,
and
then
we
can
have
different
widgets.
You
can
switch
on.
Like
I
mean
I
think
there
was
it
was
too
kristin
was
talking
about.
You
know
you
can
switch
on
a
victory.
B
B
I
think
the
idea
is
that
giving
that
flexibility
to
people,
while
still
having
structure
will
mean
that
they
can
plan
things
a
lot
more
effectively
depending
on
how
their
organization
does
things
rather
than
what
we
do
and
what
we
think
other
people
should
do
so
it's
it
gives
them
just
a
lot
more
freedom
to
do
that,
and
hopefully
it's
not
so
much
that
it
becomes
something
like.
I
don't
know
one
of
these
things
where
you
have
to
do
a
lot
of
configuration
before
you
can
actually
start.
B
Yeah
between
this
and
projects
and
groups
becoming
a
single
thing,
or
at
least
projects
becoming
a
facet
of
a
group,
or
something
like
that
that
will
be
huge
to
simplify
when
so
when
I
was
I
was.
I
did
some
teaching
at
a
university
recently
and
I
was
teaching
the
students
how
to
use
gitlab
for
project
planning
and
so
for
for
for
planning
out
and
doing
project
management.
B
I
should
say,
and
one
of
the
things
that
really
tripped
people
up
was
the
difference
in
projects
in
the
group
and,
of
course,
you
know
the
whole.
Oh,
this
is
a
group
level
label
or
this
is
a
project
level
label.
B
So
you
can't
use
in
your
group
level
and
stuff
like
that,
and
I
think
once
those
are
unified,
it's
just
it's
going
to
be
so
much
easier
for
people
to
start
using
it
and
and
just
use
it
how
they
want
to
use
it
without
thinking
about
these
different
levels
and
and
and
where
everything
lives
in
a
project
versus
group,
and
it
also
will
simplify
our
logic
because,
as
you
say,
we
won't
have
to
re-implement
things
at
different
stages.
A
Cool
and
yeah,
as
far
as
planning
objects,
there's
still
a
lot
of
thinking
going
through.
There's
still
a
lot
of
thinking
and
planning
going
on
around
like
how
we're
actually
going
to
implement
how
we're
going
to
get
to
that
end,
result
of
everything
being
a
planning
object
and
initially
getting
epics
to
be
a
planning
object,
I'll
link
to
a
few
of
the
issues.
There's
a
product
one,
there's
a
technical
discussion.
A
A
This
as
an
opportunity
to
get
issues
or
to
get
planning
objects
into
a
completely
view,
app
like
a
single
page
view
app
so
yeah.
So
we
were
talking
about
creating
an
issue
to
talk
through
some
of
that
but,
like
I
said
I'll
link
to
all
of
that
in
our
agenda.
B
B
B
It's
really
nice
seeing
you
know,
knowing
that
I
have
an
awesome
team
that
has
my
back.