►
From YouTube: Requirements Management Office Hours - May 29, 2020
Description
Requirements Management Office Hours from May 29th. Discussion around prioritization of Requirements Management and Quality Management, discussion about moving requirements traceability forward.
A
Hello,
everyone
and
welcome
to
the
requirements
management
office
hours
on
may
29th.
Let's
see,
I
think
I've
got
the
first
agenda
item
here,
so
I
just
want
to
bring
up
the
requirements.
Traceability
is
moving
forward.
Well,
there's
a
nice
issue
written
up,
I
believe,
by
nick
our
designer
about
how
we
can
have
a
satisfied
or
unsatisfied
indicator
on
the
requirements.
A
Sort
of
list-
and
this,
coupled
with
all
the
hard
work
john's
been
doing-
gives
us
encouragement
that
we'll
have
some
form
of
very
basic
traceability,
completed
in
either
13
1
or
early
132,
which
is
really
great
news.
So
we're
very
excited
about
that.
I
don't
know
if
there's
any
comments
on
that,
but
I
guess
I
just
wanted
to
let
everybody
know
that's
a
huge,
huge
step
forward
for
us.
A
Originally,
there
was
an
okr
for
shipping,
the
home
page,
which
was
basically
getting
all
stages
to
a
minimal
situation
that
would
have
included
quality
management.
For
us,
the
okr
has
been
removed.
That
did
not
make
it
into
the
official
okrs,
so
we
do
have
a
little
bit
more
flexibility,
there's
still
a
desire
to
get
quality
management
launched
soon-ish,
but
if
we
can't
get
it
into
q2,
it's
not
going
to
be
detrimental
to
the
okr.
A
So
I
guess
just
wanted
to
give
everybody
that
sort
of
update
that
we're
no
longer
sort
of
under
a
time
crunch
for
that,
so
we're
going
to
try
to
insert
it
where
it
makes
sense.
When
we
have
a
lull
in
requirements
management
or
when
we're
at
a
good
breaking
point,
we
will
do
some
work
to
ensure
we
truly
understand
the
scope
of
the
quality
management
mvc
and
then
figure
out
where
it
fits
best
in
our
whole
plan.
So.
A
I
don't
know
if
we
want
to
have
a
team
go
out
and
or
to
my
team
I
mean
a
person
go
out
and
look
at
the
feasibility
or
just
make
sure
we
really
understand
that
it's
well
scoped.
I
guess
the
best
thing
we
can
do
is
prep
and
make
sure
yeah.
We
know
exactly
how
we
do
that
and
we
don't
expect
any
surprises.
A
We
can't
predict
everything,
but
I
think
getting
at
least
a
set
of
eyes
on
that
to
really
sort
of
walk
through
it
from
the
engineering
side
to
make
sure
that
it's
well
understood,
and
it
makes
sense-
it's
probably
the
first
step
after
that.
I
think
it's
just
a
matter
of
figuring
out
when
we
want
to
fit
it
in.
If
it's
not
going
to
be
that
bad
from
a
scope
perspective,
we
can
start
working
it
as
a
background
task
over
a
couple
releases
and
just
not
plan
on
having
it
done
moving
forward.
A
A
B
Yeah,
I
remember
in
I
think,
october
november
time
we
actually
started
on
requirements
management
by
doing
some
training
first
with
people
just
to
kind
of
introduce
some
of
the
competitors
in
the
field
and
introduce
some
of
the
kind
of
standards
around
requirements
management.
So
we
could
even
do
that.
You
know
even
as
a
just
to
kind
of
set
some
context
first
and
that
equips
us
better
to
answer
questions
about
how
we
should
implement
it
later.
A
No,
I
think
that
makes
sense.
I
maybe
I'll
try
to
set
up
a
kickoff
call
next
week,
where
we
just
sort
of
go
over
the
mvc
idea
right
now
and
talk
about
how
it
relates
to
sort
of
other
products
out
there.
Quality
management
is
a
very
broad
topic
and
I
think
that's
why
it's
if
I
ask
20
different
people
and
I
have
what
quality
management
means
to
their
organization,
I
get
20
different
answers,
so
we're
really
trying
to
kind
of
figure
out
with
the
mvc.
A
We
want
to
get
something
out
there
for
people
to
use
and
then
provide
feedback.
So
we
can
really
better
understand
the
most
important
factors
for
every
organization,
so
yeah.
I
can
I'd,
be
happy
to
set
something
up
next
week,
I'll
try
to
schedule
it.
I
think
early
in
the
day
works
better
for
the
engineering
team
for
certify
you
can
invite.
Whoever
is
interested
yeah,
there's
not
a
great
time,
maybe
I'll
run
to
one
in
the
morning,
one
late
at
night.