►
From YouTube: Requirements Management Office Hours - February 11, 2020
Description
Requirements Management office hours are setup to allow anyone to ask questions, and give space for a cross-functional discussion.
A
Excellent,
so
welcome
to
the
second
requirements
office
hours
here
now,
a
time
where
we
can
just
ask
questions,
talk
about
you,
know,
thoughts
and
going
forward
and
see
where
we're
at
and
especially
problems
or
questions
we
can
hopefully
get
them
resolved.
Timely
fashion
keep
people
moving
forward,
so
yeah
is
there
anything
people
want
to
talk
about
today.
B
B
A
B
Yeah
just
looking
again
at
the
issue,
and
one
idea
is
whether
we
should
make
sure
we
keep
the
description
up-to-date
according
to
discussion
under
this
issue,
because
there
are
many
great
comments
from
customers
or
users
and
we
are
keep
updating
the
ideas
how
the
MDC
should
be
implemented.
So
perhaps
we
could
because
I'm
data
through
the
description
according
to
the
extra
plans.
Oh
absolutely.
A
I
intend
to
go
through
that
today
actually
and
try
to
kind
of
catch.
The
description
make
sure
the
description
is
up-to-date,
I'm,
Nick
and
I
had
a
great
discussion.
Sort
of
last
was
the
end
of
the
last
year.
Was
it
yesterday?
It
was
yesterday
about
you,
know,
design
going
forward,
so
I'm
pretty
sure
he's
working
to
make
sure
the
wireframes
work
to
date
in
that
as
well
and
that'll
be
coming
out
soon.
It
has
been
moved
to
planning
breakdown,
so
we
can
start
kind
of
breaking
off
incremental
work.
A
A
A
There
was
a
great
comment
post
thereby
gave
Weaver
about
how
you
know.
If
we
can
make
this
visually
like
a
visual
editor,
it
would
be
a
very
you
know,
great
selling,
point
and
I.
Don't
think
anybody
disagrees
with
that,
but
that
is
an
awful
large
update
and
I
know.
Nick
was
gonna
try
to
touch
base
with
Donald
I'm
out
the
rest
of
this
week
after
today,
so
he
was
gonna,
try
to
touch
base
with
Donald
in
the
front,
end
team
and
just
sort
of
talk
to
them.
A
A
little
bit
about
you
know
is
that
a
Eva,
Boleyn
and
I
think
what
we
were
leaning
toward
was
not
necessarily
going
fully
visual
for
the
MVC
sticking
with
lists
and
in
textual
base,
but
then
adding
this
visual
component
to
it.
So
you
can
click
to
view
the
visual
component
and
then
over
time.
If
we
want
to
go
ahead
and
add
more
functionality
into
the
visual
component
and
if
we
want
to
eventually,
depending
on
customer
desires,
we
could
migrate
over
to
that
in
the
future.
The
underlying
architecture
should
be
the
same.
B
A
If
that's
getting
used
a
lot
that
maybe
we
allow
them
to
edit
but
it'll
be
incremental.
That
way
and
it'll
be
a
much
more
smaller
iteration
step
and,
as
you
said,
yeah
the
back
end
is
gonna.
Have
the
same
back
end.
So
it's
just
how
you're,
interacting
with
that?
It's
really
what
we
want
to
determine
from
usage.
A
Okay,
well,
if
there's
not
a
lot
of
other
discussion,
you
know
I
can
give
people
back
their
time.
I
don't
want
to
take
extra
time
from
people.
I
know
we're
all
busy.
If
there's
any
questions
any
point
you
know
feel
free
to
reach
out
to
me
there,
on
slack
or
in
the
next
requirements.
Office
hours
I'd
be
happy
to
answer
questions
and,
as
we
move
forward
I'm
sure
there
will
be
lots
more
discussion
as
we
start
breaking
this
down
and
actually
doing
the
work
so
I'm
good
to
end
this
everybody
else's
thanks
mark
appreciate.