►
From YouTube: Plan stage weekly 2020-04-08
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
And
cushaw
I
was
actually
sorry.
I
was
actually
going
to
ask
mark
to
give
an
intro
on
requirements,
management,
but
I
think
Cormac
actually
just
did
a
and
we
didn't
record
it
of
course,
but
you
did
a
pretty
good
intro
on
the
the
business
value
of
requirements
management.
You
want
to
just
kind
of
repeat
what
you
what
yeah
it
said
before
we
started
recording
I'm
sure.
C
I,
so
you
know
from
a
marketing
perspective
we
and
to
the
public.
We
talked
a
lot
about
the
value
of
the
single
application,
having
everything
in
one
place
and
having
all
the
stages
of
your
life
cycle
in
the
same
place
and
I
think
that
this
to
me
is
a
really
good
example
of
what
you
could
do
when
all
of
that
information
is
together.
A
Yeah
so
I'm
in
our
good
luck,
shell
project
I
in
debates-
so
let
me
know
if
you
still
find
it
not
clear
or
visible.
So
in
the
gate
lab
shell
project,
we
have
37
requirements.
We
already
have
made
the
changes
regarding
the
counts,
so
we
show
exact
counts
of
available
requirements
for
the
project
in
the
tabs
as
well
as
in
the
navbar.
These
counts
update
dynamically.
So
you
don't
have
to
reload
the
page
in
over
order
to
see
the
updated
counts
based
on
the
interactions
you
do
so
on
single
page
will
be
showing
20
requirements.
A
To
begin
with,
this
is
the
same
count
that
we
are
using
for
issues
and
Amar's,
and
one
difference
that
you
would
notice
that
if
there
are
more
than
20
requirements,
the
pagination
controls
that
are
available
at
the
bottom
of
the
page
do
not
show
page
numbers.
So
there
is
an
there
is
an
own
graph
queue
limitation
like
we
cannot
have
a
random
access
to
individual
pages.
We
have
to
traverse
through
all
the
pages
in
order
to
reach
end
of
the
list
or
beginning
of
the
list.
A
A
So
if
I
click
on
previous,
we
have
20
items
on
the
page,
so
you
would
notice
that
we
saw
20
skeleton
loading
animations
on
the
page
and
then
the
items
showed
up
so
that
way
it
feels
like
a
refined
UX
on
the
listing
power
of
things
now
going
to
the
archived
page.
So
switching
between
the
tabs
is
something
that
will
require
page
reload,
because
that's
how
we
are
doing
it
for
other
places
as
well,
be
it
epics
issues
or
more
requests
and
all
the
requirements
are
that
an
archive
currently
will
be
shown
here.
A
One
difference
that
you
would
notice
is
that
if
we
go
to
the
open
tab,
there
are
two
exit
buttons
and
of
them
are
represented
by
icons.
So
we
have
an
edit
action
and
the
archived
action.
As
far
as
archive
tab
is
concerned,
we
have
a
button
with
a
label
reopen
so
I'm
working
with
Nick,
regarding
which
I
can
to
use
here.
For
now,
we
don't
have
appropriate
icon
to
show.
A
So
we
are
at
least
starting
in
the
first
iteration
will
be
using
reopen
as
the
label
and
not
any
item
so
that
we
are
not
blocked
by
any
design
decisions.
So
now
I'll
go
ahead
and
create
a
new
requirement
and
we'll
go
through
individual
flows
like
updating
your
created
requirement,
they're
not
having
it
and
then
reopening
it
back
again.
So
this
new
requirement
button
shows
up
on
the
open
tab.
So
if
we
go
to
the
archive
tab,
you
would
notice
that
the
button
hides.
A
So
we
do
not
want
basically
to
show
new
requirement
form
in
places
where
newly
created
requirement
won't
show
up.
So,
for
example,
if
I
am
on
the
archive
tab
and
if
I
still
allow
user
to
create
a
new
requirement
from
the
archive
technically,
that
requirement
goes
into
the
open
tab.
It
doesn't
show
up
in
the
archive
tab,
so
we
don't
want
to
create
any
confusion
like
if
user
creates
a
requirement
and
then
expects
that
requirement
to
show
up
within
the
same
list
without
reloading
the
page.
A
So
in
order
to
simplify
it,
we
are
simply
hiding
the
new
requirement
button
on
places
where
it
is
not
supposed
to
be
so
now
when
I
click
on
new
requirement,
I'll
just
call
it
fubar
and
I'll
click
on
create.
There
will
be
an
animation
on
the
bottom
button.
Obviously,
since
we
are
demonstrating
it
on
local
genie
case,
everything
happens
fast,
so
the
requirement
was
created
and
we
refresh
the
list
of
the
items
and
the
new
requirement
is
just
created
here.
It
will
reflect
the
creation,
timestamp
and
updated
timestamp
in
case
it
is
newly
created.
A
Both
of
them
are
same
now
if
I
want
to
edit
it
I
can
click
on
edit,
and
this
is
how
the
Edit
form
looks
like
so
fubar,
hello,
I'll,
just
change
its
title.
Click
on
save
and
there
you
go
changes
of
hello-
show
up
now
notice
these
counters
as
I
start
interacting
with
individual
requirements.
So
right
now
we
have
27
open
requirements
and
total
of
38
requirements.
Now,
if
I
archive
this
requirement,
you
would
notice
that
the
count
reduced
by
1,
so
we
do
not
have
to
reload
the
page.
A
The
counter
gets
updated
based
on
whether
create
a
new
requirement
or
update
an
existing
and
the
moment
our
IR
caved
that
requirement.
It
went
away
from
this
list
and
is
now
available
in
the
archive
page,
and
here
you
can
see
that
it
is
on
top
of
this
list.
Now,
if
I
click
on
reopen
same
thing
happens,
it
will
go
back
to
the
open
tab
and
goes
away
from
there
and
going
back
to
open
tab
shows
up
right.
So
these
are
the
three
workflows
that
we
are
aiming
for.
A
The
three
items
that
I
mentioned
in
the
agenda,
which
aren't
available
here,
is
that
one
design
proposal
is
that
when
new
requirement
is
created,
we
want
to
highlight
that
requirement
on
the
list,
because
we
are
aware
that
newly
created
requirements
show
up
at
the
top
of
the
page,
but
it
might
not
be
obvious
for
new
users,
so
we
want
to
highlight
it
using
some
colors.
So
those
designs
are
already
in
place:
I'll
implement
those
changes
by
next
week.
A
So
before
12.10
is
frozen
on
17th
of
April,
we
have
all
those
changes
in
massive
rooms,
so
that
is
one
thing.
Another
one
is
that
the
additional
actions
that
you
do
like
updating,
the
title
or
archiving
or
looping
the
requirement
you
want
to
show
to
us
the
message
at
the
bottom
of
the
page
to
reflect
what
exactly
happened.
So
that
is
also
something
that
we
will
be
covering
in
the
upcoming
Amar's
and
same
thing
goes
for
empty
states
like
if
I
visit
a
project.
Well,
there
aren't
any
requirements
available
at
all.
A
A
Ideally
we
are
supposed
to
show
new
requirement
action
right
on
the
NP
State
page
itself
like
this
page
here
it
will
be
explaining
what
requirements
are
as
per
the
proposed
design
so
like.
If
there
are
no
requirements
on
the
base,
then
you
would
see
this
like.
There
are
no
open
requirements,
but
in
case
there
are
no
requirements
created
at
all
for
this
project.
A
We
want
this
message
to
explain
what
requirements
as
a
feature
is,
and
instead
of
showing
this
new
requirement
button
here,
we'll
be
showing
it
somewhere
here
and
you
click
on
that
button
and
create
a
requirement
for
the
project
and
same
thing
goes
for
other
places
like
if
I
click
on
this
all
tab.
It
will
show
all
the
requirements
with
archived
and
open
requirements
and
the
actions
that
are
available
are
in
on
the
individual
basis
like
once
we
have
the
listing
loaded
here.
A
You
would
notice
that
ok
yeah,
so
obviously
it's
a
demo
and
no
demo
is
completed
without
anything
broken,
so
I'll
obviously
check
what's
going
on
with
this
all
tab,
igneel
a
is
supposed
to
load
in
all
the
requirements,
instead
of
not
rendering
anything.
So
that's
one
thing,
but
obviously
this
is
the
basic
demo
like
what
features
are
expected
to
work
on
the
requirements,
management
so
yeah.
That
is
it
for
the
demo.
Any
questions
so
far.
D
A
E
A
Yeah,
so
so
what
happens
in
this
case
is
that
so
right
now
we
are
having
own
day
26
requirements
and
with
27
requirements
to
be
exact,
and
we
are
only
having
two
pages
I'll
quickly
demonstrate
why
that
page
number
is
still
important,
although
it
is
not
used
directly
on
pagination
component
itself,
but
we
are
still
utilizing
it
to
determine
when
to
disable
next
or
previous
buttons.
So
let
me
change
our
default
page
size
to
5,
so
that.
A
So
you
have
one
more
thing
that
I
forgot
to
mention
was
that
all
the
pages
are
permalink.
So
if
you
have
more
than
one
page
of
items
and
if
you
are
traversing
through
pages,
you
can
copy
the
URL
share
it
with
someone
and
they
are
guaranteed
to
land
on
the
exact
same
page
that
you
are
viewing.
So
that
way
we
are
preserving
the
functionality
of
maintaining
the
page
position.
E
A
A
Idea
of
having
the
appearance
of
what
is
that
like
yeah
so
like?
If
there
are
five
pages
in
the
list
and
if
user
has
already
traverse
through
third
page,
then
the
URL
will
include
page
three
in
the
banner.
So
if
someone
copies
that
URL
and
opens
that
page
I
mean
they
will
notice
that
both
next
and
previous
buttons
are
enabled,
because
user
is
in
the
middle
of
the
page
position.
So
if
user
is
not
on
the
first
or
last
page,
then
we
need
to
be
sure
that
both
the
buttons
are
available
for
access.
A
So,
like
notice,
we
are
on
the
third
page
and
if
I
click
on
next
once
more,
it
will
take
me
all
the
way
to
the
last
page,
and
now
next
button
is
disabled.
So,
if
like,
if
I'm
on
the
fourth
page
and
if
I
copy
this
URL,
it
will
land
me
directly
on
the
fourth
page
and
we'll
make
sure
that
the
next
button
gets
disabled
at
appropriate
position.
So
if
I
click
on
next
again
on
six-phase,
it
gets
disabled.
A
So
that
way
we
are
preserving
the
page
position
and
in
last
plan
v3
I
also
mentioned
like
how
to
handle
browser
back
and
forward
buttons.
So
that
is
preserved
like
if
I
click
on
back
it
will
reload
the
page,
and
it
will
drop
me
on
page
five
page,
one
directly
in
case
I
am
on
a
different
page
position.
So
that
way
user
is
not
affected
by
how
bad
was
the
back
button
works,
even
if
they
are
traversing.
A
F
Yeah
I
think
it's
me
next,
thanks,
coach,
like
we
saw
live,
demos,
were
a
great
addition
to
this,
but
the
live
coding
part
was
especially
a
hedge
of
seat
stuff,
like
so
Thanks
yeah,
look
I,
don't
know
who
in
the
team
is
aware
of
this
yet
Bob
we
are
working
on
the
first
real-time
feature
for
get
lab.
That
is
real-time
assignees
in
sidebar
yeah.
So
we
have
a
working
group
for
this.
A
lot
of
the
application
work
is
already
done
by
Heinrich,
but
there's
an
opportunity.
F
F
So
if
this
is
something
you
speaking
especially
to
the
engineers,
if
this
is
something
you're
particularly
interested
in
and
please
get
in
touch
with
me,
because
we'll
obviously
need
more
of
the
team
to
get
involved
than
just
one
person,
and
also
it's
a
really
good
opportunity
to
have
a
real-world
example
of
a
feature
deployed
right
to
the
end
of
the
the
chain.
You
know
from
application
level,
true
docker
ization
all
the
way
through
to
deployment
kubernetes
and
not
just
to
learn
academically,
but
to
actually
deploy
something
useful
with
it.
F
F
I
have
the
next
item
as
well.
So
he
like
there
have
been
a
couple:
we've
kind
of
talked
about
these
kind
of
things
at
length,
but
again
I
just
wanted
to
vocalize
in
front
of
everyone,
who's
involved
in
the
planned
stage,
where
we've
kind
of
been
doing
things
that,
like
don't
scale
right
so
with
regards
to
some
features.
The
JIRA
importer
is
the
obvious
one.
So
we've
kind
of
created
a
slack
channel
I
do
bi-weekly
or
dates,
and
the
PM's
do
bi-weekly
updates
on
the
progress
or
seal
interest.
F
We
have
epics
that
we
constantly
groom
and
reprioritize.
We
also
built
a
proof
of
concept
first
and
then
broke
the
featured
ein
from
that
proof
of
concept,
and
we
delivered
the
JIRA
importer
have
to
say
like
Alexandra
and
Yakov
diversity
reporter
in
a
very
short
space
of
time.
But
there
are
other
examples
of
this
as
well
and
requirements.
F
Management
is
another
good
example
where
Marcus
on
office
hours
every
week
and
provided
training
materials
and
we're
starting
to
do
something
similar
with
burn
up
charts
and
so
I'm
kind
of
wondering
like
what
are
people's
opinions
on
this
approach.
It's
not
sustainable
and
it
doesn't
scale
for
every
feature
that
we
want
to
release.
F
But
you
know,
as
as
Paul
Graham
says,
you
know,
do
things
that
don't
scale
to
start
with
and
then
hopefully
we
won't
need
these
in
three
milestones
for
milestones
and
so
yeah
I
just
want
to
put
it
like
that
first
or
open
discussion.
What
do
people
think
of
these
things?
They
are
they
only
helpful
for
me
or
are
they
helpful
for
other
people
as
well
to
follow
the
work
I.
E
Think
it's
it's
helpful
for
me
to
be
able
to
focus
on
something
like
as
a
deliverable
I
had
this
feeling
before
that
I'm,
not
exactly
sure
what
some
of
the
deliverables
are
for
a
specific
release
like
the
high
high
level
kind
of
view,
so
to
say,
yeah
like
being
able
to
you
have
this
focus
groups
so
to
say
specific
deliverables.
I
feel
like
it's
helpful,
maybe
later
on
once
we
kind
of
polish,
the
workflow
and
so
on.
E
D
Object,
we
mention
the
concept
behind
the
office
hours.
The
reason
that
I
kind
of
chose
that
approach
relieve
requirements
management
was
the
idea
that,
once
the
development
work
is
primarily
completed
on,
I
was
hoping
the
office
hours
within
transition
to
marketing
and
sales
team
so
that
they
could
come
and
ask
questions
from
their
particular
groups
that
they
interface
with
and
if
necessary.
We
could
then
pull
an
engineering
if
required,
but
not
necessarily
as
an
everyday
thing.
So
I
was
hoping
that
would
theoretically
scale
slightly
better.
D
It
was
more
or
less
morph
into
something
slightly
different.
What's
the
idea
behind
it
we'll
see
how
that
plays
out
I'm
I'm
game
to
keep
that
as
sort
of
an
experiment
and
see
you
know
where
it
leads
us,
and
if
it's
something
we
want
to
keep
doing
in
the
future,
and
if
it
isn't
useful,
then
that's
fine.
We
can
always
cancel
on.
C
F
E
Yeah
I
think
that's
more
a
question
for
you
yard.
During
this
specific
instance,
bad,
like
I,
think
it
does
help
because
again,
especially
that
out
for
myself,
if
I
would
be
joining
a
feature
in
development
already.
It
would
be
helpful
to
know
like
where
to
ask
this
specific
question.
If,
like
we
do
have
the
development
channels-
and
you
can
ask
all
sorts
of
questions
when
it
is
very
focused
on
a
specific
deliverable
or
tasks
you
reach
to
the
people,
with
the
expertise
much
much
faster.
If
you
feel
like.
E
On
the
same
theme
of
the
collaboration,
we
did
talk
about
stuff
here
and
we
kind
of
want
to
get
feedback
it
to
me
personally.
It
doesn't
feel
like
very
collaborative
to
have
the
agenda
and
to
have
people
that
do
not
attend
the
call
coming
to
agenda
and
try
to
get
feedback.
So
I
was
wondering
if
we
should
actually
pull
this
into
a
issue
of
some
sort.
Maybe
a
separate
project
for
the
plan
meetings
or
something
like
that.
So
I
don't
know
if
you
so
just
encourage
collaboration,
easier
collaboration
on
these.
B
E
B
Yeah
so
I'm
wondering
because
the
agenda
is
nice
for
like
no
or
that
Google
Doc
is
nice
for,
like
real-time
note-taking
and
using
it
as
an
agenda
that
way,
but
I
agree
that
can
I
encourage
collaboration
on
some
of
the
things
that
we
talked
about.
It's
probably
best
to
at
some
point,
ideally
right
after
the
meeting
we
go
and
create
issues
for
them,
and
then
we
further
instead
of
continuing
communication
in
the
in
the
Google
Doc.
Let's
continue
those
conversations
within
within
issue,
maybe.
E
F
Me
yeah
I'm
glad
I
specified
the
H
because
there's
more
than
one
john
on
the
call
right
so
yeah
anyway
cool
so
yeah,
that's
just
a
reminder
for
eligible
engineers
to
please
sign
up
for
the
on
call
slots
for
me:
I'm
the
facilitator
for
me
and
I.
Think
chang-jung
is
the
backhoe
facilitator,
so
yeah
anyway,
we're
still
down
a
few
slots.
So
if
you
haven't
done
yet,
please
look
at
the
dock
and
pick
some
slots.