►
From YouTube: Plan stage weekly - 2020-05-06
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
Yeah
I
just
want
to
can
bring
bring
this
up.
So
one
of
the
things
we're
starting
to
hear
a
lot
more
from
customers
is
the
need
for
a
program,
little
order
or
an
epic
board,
so
a
board
that
just
has
epic
cards
kind
of
different
from
the
slim
lean
project,
we're
also
working
on
so
one
I
just
wanted
to
bring
it
up
early
to
get
the
team.
B
C
Sure
I
was
gonna,
propose
or
thinking
about
proposing
renaming
the
category
Kanban
boards
to
do
sports,
and
that
way
we
could
use
those
like
work
on
an
underlying
board
construct
that
can
be
used
for
epics.
It
can
have
swim
lanes,
it
can
be
used
for
issues
and
like
toggling
the
modes.
So
that
way,
we're
not
creating
like
a
new
thing,
but
we're
like
iterating
on
what
we
have
to
make
it
extensible
for
both
these
cases.
C
Yeah
cool
okay,
but
that
would
that
way
because,
like
we
already,
we
need
to
refactor
the
boards,
I'm
pretty
sure
we're
working
on
making
in
real
time
it's
what
we
would
do.
We
also
want
to
make
it
so
that
we
could
open
and
like
an
issue
directly
within
the
board
and
interact
with
it,
and
it's
like
that
same
experience
would
work
for
the
epic
level
and
I
think
it
also
makes
sense,
and
some
of
the
explorations
I
was
doing
them
like
the
limbs
goal,
like
just
figuring
Italian,
to
like
one
value
stream.
C
So
you
could
almost
like
zoom
out
from
the
issue
level
into
the
epic
level
and
like
that,
it's
all
connected,
and
so,
if
I'm
working
on
my
stuff
I
can
I
can
go
to
whichever
granularity
I
need
to
to
given
point
in
time
to
see
progress
of
both
things.
I
like
that.
That
would
make
it
so
that
I
would
never
have
to
use
lists
either
like
issue
list
and
epic
lists
and
search
for
things
and
search
for
the
things
for
my
life.
I
could
figure
out
a
one
light
kind
of
place
that
that's
my
hope.
B
Yeah
I
I
think
it
makes
sense
if
we're
gonna
expand
it
to
cover
nun
convent
like
something
like
epics.
That
makes
sense.
I,
don't
know
if
board's
is
teaching
Eric.
If
we
need
to
doll
it
up,
more
I,
don't
know,
but
yeah
I
don't
have
any
problems
with
focusing
on
a
rename.
That
gives
us
a
little
more
coverage
in
an
area.
Alright,
yeah.
A
A
A
Alright,
so
this
one
is-
and
this
is
an
extension
of
the
drag-and-drop
on
epic
tree-
that
we
did
a
bit
ago-
the
plan
was
to
allow
for
interaction
from
epic,
so
from
children
of
an
epoch
to
children
of
another
epic.
We
just
had
not
had
not
prioritized
it
yet
Florrie
took
it
on
this
test
or
in
13.
Oh
so,
I'm
gonna
show
what
we're
doing
here.
So
this
one.
This,
mr,
is
in
canary.
A
It's
not
a
production
yet
so
I'll
show
it
first
in
production,
how
it's
currently
working
and
then
I'll
flip
around
and
show
how
it's
going
to
work
once
that
makes
it
to
production.
Okay.
So
here
we
have
a
sub
epic
or
I'm.
Sorry,
an
issue
within
an
epoch
say
I
wanted
to
move
it
to
this
second
epoch:
it's
just
not
possible.
A
A
I'll,
do
it
again,
let's
see
if
I
can
get
it
right
there
we
go
mm-hmm
and
it's
actually
pretty
like
the
dragging-and-dropping
is
pretty
intuitive
I'm,
pretty
impressed
with
how
easy
it
is
to
sometimes
one
year
and
now
as
I
say
that,
of
course,
I
can't
get
it
in
there,
but
sometimes
with
like
what
would
be
like
a
bullet
point
is
a
bit
tough.
Oh,
you
know
what
this
may
be
an
issue.
If
there's
not
a
oh
there,
it
is
okay
yeah.
E
F
C
C
The
cool
thing
about
this
is
like
we
were
we're
working
on
swim
lanes
and
one
of
the
things
like
you
can't
do
enjoy
your
next
Jim
is
drag
an
issue
between
like
parents,
epics,
right
and
I.
Think
this
word.
If
we
figured
it
out
here,
we
should
also
be
able
to
extend
it
to
like
boards
and
some
lanes
and
all
that
cool
stuff
and
then
eventually,
hopefully,
the
road
map
to
yeah
yeah,
because
I
would
be
awesome.
Do.
B
Yes,
it's
desired.
It's
it's
I've
been
reactive
in
real-time
interaction
with
the
road
maps
which
is
a
sub
epic
under
road
map.
Category
maturity,
complete
I
think
we
had
some
time
till
we
run
into
that
one.
But
yes,
that
is
so
here's
the
thing,
regardless
of
how
good
we
make
the
road
map
in
its
current
state.
B
The
next
immediate
expectation
that
we
already
get
now,
but
we
were
going
at
or
we'll
have
to
tackle,
even
when
we
get
to
a
better
functioning
road
map,
is
the
ability
to
like
interact
after
with
the
road
map
and
change
it
in
real
time.
Click
to
add
another
epic
click
milestone
clicking
epic
and
drag
it
to
change
the
dates
and
then
dragging
them
for
probably
different
organizational
constructs
like
the
epic
treatise
or
to
move
it
around
on
the
rememb
you.
But
that
is
a
very
real
use
case
that
we'll
need
to
approach.
A
C
So
just
yeah
FY,
because
there's
a
lots
of
people
that
are
contributing
to
the
dear
importer
and
it's
thank
you
by
the
way
it's
going
great
I.
Think
yarko
is
investigating
these.
Your
mapping
thing
yesterday
and
realized
that,
like
the
original
idea
was
odd,
match
users
from
JIRA
with
users
and
get
lab-based
an
email
address.
Jira
has
changed
her
policies.
I
guess
it's
happened.
C
Maybe
a
year
ago
now,
but
they're
just
getting
around
to
updating
you
guys
that
you
can't
request
you
basically
don't
have
visibility
into
the
email
address
unless
you
are
an
app
a
registered
app
with
JIRA
and
you
have
been
whitelisted
and
you
use
it
first
for
some
spaces,
our
use
case
is
technically
like
would
be
approved,
but
we
aren't.
We
don't
have
an
app
that
we're
registering
with
in
JIRA
that
we
can
get
Wyatt
listed
since
we're
just
using
an
API
so
again
from
your
user.
C
So
because
of
that,
we
have
to
shift
and
change
our
approach
to
how
we're
going
to
do
use.
Your
mapping
and
I
proposed
a
couple
different
options:
hyper
perches,
either
using
a
UI,
JSON
file
or
a
combination
of
both
and
I.
Think
we're
gonna
have
to
do
that.
Just
because
the
enabling
asking
everybody
in
your
organization
to
make
your
email
address
public
is
a
pain,
and
then
it
only
work
if
you're
a
site
admin
and
not
just
like
a
project
admin.
C
So
it's
it's
overly
restrictive
and
cumbersome
and
I
think
we
can
make
it
a
little
bit
easier
with
approach
that
at
least
some
of
the
approaches
to
that
line.
So
that's
gonna
touch
design,
Holly,
that's
gonna,
touch
front-end!
Now
more
and
I'll
sit
back
int,
so
I
don't
really
care
what
the
solution
is.
I,
don't
have
a
strong
opinion,
other
than
I
would
say
like.
C
Let's
take
whatever
is
reasonable
from
a
cost
and
time
perspective
and
also
make
it
a
good
user
experience
so
that
you
don't
have
to
like
go
and
reference
names
and
to
systems
and
try
to
like
pull
everything
together.
It
takes
like
hours,
I
think
we
can
make
it
easier
for
the
user.
So
read
that
thread
if
you're
interested
and
we
can
follow
a
sink,
just
an
FYI,
any
questions.
All
that
concerns
thoughts.
A
The
only
question
I
have
on
that
is
around
JSON
and
CSV.
In
the
research
we
did
on
Durham
Porter
the
users
that
are
going
to
be
importing
it.
How
technical
are
they
like?
Are
they
going
to
be
able
to?
Are
they
familiar
with
JSON
and
writing
JSON
in
order
to
get
that
or
should
we
should?
We
prefer
CSV
for
the
first
iteration
if
we
decide
not
to
figure
out
a
way
to
auto
match
or
form
a
table
image.
C
I
I,
don't
have
a
strong
preference.
I
did
propose
if
we
do
the
JSON
approach
to
more
or
less
populating
a
template
for
them
to
download.
That
has
like
everything
set
up.
So
it's
basically
like
you
have
your
key
and
value
for
every
tier
user,
and
then
you
have
a
key
for
it
like
Guzzi,
underneath
that
and
like
an
array
of
objects,
and
then
you
have
all
of
your
get
lab.
Users
are
in
that
project
like
populated
the
top
and
like
a
comma,
or
something
like
that.
So
this
is
just
a
copy
and
paste.
C
You
know
down
that's
one
option
if
CSV
is
somehow
easier
that
could
be
another
I
basically
wanted
to
propose
that,
because
it
would
make
it
so
that
somebody
didn't
have
to
reference
users
in
both
systems
and
we
we
can
provide
the
display
names
of
both
systems
in
one
file
already.
We
just
can't
necessarily
match
them
together
perfectly.
D
Lean
toward
what
is
going
to
be
the
easiest
approach
for
the
user,
just
because
I
don't
feel
that
we
have
strong
insight
and
gauge.
You
can
tell
me
if
I'm
wrong
on
that
as
to
what
the
level
of
technical
skills
would
be,
and
then
we
can
learn
as
we
go,
but
we
can
talk
about
it
more
in
the
issue.
If
that
makes
sense,.
A
Alrighty
I'll
move
on
to
the
last
topic.
Just
for
the
portfolio
management
certify
board,
I
was
looking
at
that
earlier.
There
were
only
three
items
and
ready
for
dev,
which
is
great
because
it
shows
that
things
are
flowing
through
the
workflow.
I
did
move
two
things
over
that
were
planning
priority
issues
that
we
had
in
planning
breakdown.
A
B
Review
single
mark
I.
F
Took
a
quick
review
over
it,
I
think
the
one
thing
that
was
missing
I
just
had
it
over
there
was
the
tracing
for
requirements.
I
don't
have
things
in
that
list
as
well.
So
you
know
I
could
take
a
look
at
that
make
sure
we're
in
order.
So
you
start
pulling
for
the
top
and
shouldn't
take
us
more
than
a
little
bit
I
think
after
this
meeting,
at
least
for
me,
I
can't
speak
for
Keenan
yeah.