►
From YouTube: Requirements Management Office Hours - February 7, 2020
Description
Requirements Management office hours are setup to allow anyone to ask questions, and give space for a cross-functional discussion.
A
Okay,
we've
got
recording
going
so
yeah.
Let
me
just
repeat
that
quick
heart,
a
little
bit
here,
just
gonna
say
that
you
know
this
meeting
is
really
for
those
people
getting
involved.
I
don't
have
a
particular
agenda.
The
agenda
is
shared
in
the
notes
and
of
the
meeting
and
is
now
editable
by
everybody,
which
is
great,
so
I've
kind
of
invited,
a
diverse
group
of
people.
Anybody
who
wants
to
ask
questions,
you
know
we're
gonna
try
to
do
this
weekly
as
much
as
possible.
I
know
next
week.
A
B
You
with
a
hard
one
to
begin
with
so
as
far
as
I
understand
like
the
first
iteration,
we're,
keeping
it
really
really
simple
and
we're
going
to
basically
be
able
to
create
and
list
requirements
and
I
think
that
we've
sort
of
settled
on
the
idea
that
we'll
use
like
a
database
based
solution
for
that.
It's
like,
as
opposed
to
bated
get
for
awhile
and
I.
We
settled
on
at
least
like
storing
metadata
in
the
database,
so
I'm
kind
of
wondering.
B
A
I
think
the
intent
I
have
after
talking
to
Eric
and
Scott,
and
so
the
product
alignment
stuff
we've
been
doing.
Is
they'd
really
want
to
focus
on
this
because
there's
a
large
potential
for
iacv
here
and
there's
a
there's
really
an
untapped
market
that
we
would
like
to
be
able
to
address
and
I
think
we're
gonna
see
iterations
on
requirements,
management
before
it
becomes.
You
know,
mature,
there's,
gonna,
be
a
lot
of
iteration,
so
I
foresee
a
lot
of
the
service
desk
work,
kind
of
being
trailed
off
a
bit
and
focusing
more
than
requirements.
A
Management
aspect.
My
point
with
the
first
iteration
is
mainly:
we
need
to
get
a
platform
forward
to
the
developers
to
begin
building
out
additional
features
and
for
the
designers
to
begin
designing
additional
features,
I'm,
not
sure
if
customers
are
going
to
switch
over
to
get
lab
or
heavily
utilize
requirements
management
with
the
first
iteration
I.
You
know
there
are
a
bunch
of
customers
who
are
interested
in
seeing
we
were
going
with
it
and
want
to
just
get
involved
and
start
playing
with
it
and
I
think
that's
incredibly
valuable.
A
That
will
allow
us
the
opportunity
to
get
their
feedback,
which
will
help
us
shape
the
product
even
more
so
is
there
enough
for
them
to
use
it
and
actually
use
it
in
their
production
environments.
First
iteration,
probably
not,
but
I-
think
it's
definitely
enough
for
them
to
get
involved.
We
have
a
bunch
of
you,
know:
customers,
as
I
said,
who
just
want
to
see
some
progress
on
it,
they're
just
looking
to
see
that
we're
we're
making
progress
in
meeting
our
commitments,
which
is
I,
think
part
of
the
important
thing
here.
B
Thanks
and
so
I'm
kind
of
wonder
and
then
what's
what
do
you
think
is
kind
of
the
the
simplest
thing
we
can
do
to
actually
like
provide
real
body?
I
mean
it's
possible
like
we
won't
immediately
land,
an
aerospace
company
off
the
first
iteration,
but
providing
value
for
customers
that
acquire
less
stringent,
I
guess
requirements
management?
What's
your
view
on
that
I
looked.
A
At
it
from
where
can
we
use
it
and
dog
food
at
the
most
internally,
as
well
as
where
can
we
expect
to
see
our
customers
be
able
to
provide
the
most
feedback
and
I
think
to
me
if
we
can
provide
an
opportunity
for
them
to
create
a
requirement
and
then
link
test
cases
to
it
or
test
results
to
it
or
something
along
those
lines?
In
a
very
simple
level,
we're
going
to
appeal
to
a
large
market
and
that's
gonna,
be
what
we're
gonna
sort
of
foundationally
basis
on
you
know.
I
know
gay.
A
We
ever
talked
to
a
lot
of
the
people
he's
been
on
site
with
he's
been,
you
know,
going
around
talking
a
project
management
in
portfolio
management
and
a
lot
of
them
said
what
would
be
a
killer
feature
for
us
is
simply
to
have
the
jobs
to
be
done,
requirements
user
stories,
whatever
you
want
to
call
them,
depending
on
your
your
organizational
structure
and
be
able
to
link
your
test
results
and
tests
to
those.
Even
if
at
the
beginning,
it's
just
you
can
click
on
it.
It
shows
you
the
results,
you
can
click
on.
A
It
shows
you
the
CSU
job
or
something
very
basic.
Obviously
the
ideal
long-term
would
be
able
to
be
able
to
see
hey
look.
This
test
ran
it
past
and
therefore
we
have
four
out
of
five
test.
Passing
that
trace
to
this
job
can
be
done.
That
would
be
a
nominal
features.
I
think
that
alone
would
draw
people
into
using
a
harmless
banishment,
and
so
we
get
more
toward
regulated
industries.
A
They're
gonna
require
a
larger
feature
set
to
adopt,
simply
because
they
have
to
do
certain
things,
so
if
they
can't
do
those
within
our
tool,
it's
going
to
slow
their
adoption.
However,
even
within
regulated
industries,
there
are
a
awful
lot
of
iron
D
groups
or
sort
of
side
groups
that
could
totally
use
that
as
their
full-featured
requirements
management
solution
to
develop
these
component
level
pieces
that
then
get
pulled
into
the
broader
organization
and
into
other
tools
and
I.
A
Think
that's
really
where
the
power
lies
is
we're
looking
for
something,
that's
quick,
that's
agile,
and
that
will
allow
them
the
basic
level
of
requirements
management.
They
need
to
be
able
to
pass
those
things
off
to
other.
You
know
parts
of
the
organization,
so
I
think
that's
really
where
we
need
to
be
able
to
get
sort
of
before
we're.
At
that
point,
we're
minimal
or
even
viable.
We
can
say,
hey
look,
this
is
usable
and
from
there
we'll
be
bulking
up
features
and
getting
a
lot
of
that
feedback.
Where
do
they
want
to
go?
A
The
other
aspect
to
think
about
is
Quality.
Management
is
still
in
certify,
and
quality
management
is
shaping
out.
The
more
I
talk
to
people
to
be
more
of
a
sort
of
status,
dashboard
of
the
quality
of
your
code,
so
you
can
go
to
one
place
and
say:
okay,
we
have
400
tests
for
this
section
of
code.
320
of
them
are
passing,
80
of
them
are
failing.
These
are
failing
with
major
issues.
These
are
failing
with
minor
issues
and
that's
sort
of
like
their
quality,
their
overall
metrics
requirements.
A
Management
is
slightly
different,
but
it
will
play
off
of
that
very
well.
Those
two
tools
combined
should
give
people
a
lot
of
insight
into
their
product.
Oh
we
made
these
changes.
We
added
this
story.
We
updated
these
tests
and
hey
if
we
can
link
in
bugs
if
we
can
link
in
latency
or
performance
issues
or
other
warnings
that
come
out
of
our
CI
CD
they'll,
be
able
to
then
track
their
change
from
reception
or
idea
all
the
way
down
through
and
say,
hey
this
caused
us
problems
or
hey.
This
is
benefited
us
greatly.
A
Even
better
would
be
able
to
track
adoption
if
we
can
figure
out
a
way
to
somehow
get
that
involved
with
requirements
for
people,
even
if
it's
just
internally
dog
food.
That
would
be
an
amazing
tool
for
us
as
project
managers
and
product
managers
and
basically
engineering
I,
mean
you
say,
hey
look.
We
made
this
change.
We
added
this
job
to
be
done
to
this
story.
We
implemented
it,
we
rolled
it
out
and
look.
C
A
So
we're
designing
it
with
the
database
solution,
primarily
because
we
know
it's
scalable
and
we
know
we
can
move
it
up.
The
org
chart,
as
we
move
and
add
features
to
those
other
like
to
groups
and
we're
talking
about
teams
and
there's
other
there's
other
discussions
ongoing
here.
So
yeah
I
mean
that
was
sort
of
the
goal
here.
I
think
I'm
not
sure
if
we're
gonna
end
up
at
the
project
or
the
group
level,
originally
I
think
it's
pretty
much
the
same
thing.
A
Once
we
go
over
the
database,
I,
don't
think
it's
a
huge
impact
either
way
we
want
to
get
to
the
group
level
as
soon
as
possible.
So
if
that's,
if
there's
no
extra
work
to
get
it
at
the
group
level,
that's
where
we
should
go
if
there
is
extra
work
to
get
there,
I'm
fine
with
releasing
in
the
project
level
and
then
iterate
on
that
and
next
go-around
move
it
up
a
level
and
that's
five
gotcha
makes
sense.
Thanks.
A
Excellent,
so
I
know
the
got
that
MVC
out
there.
I
know
the
next
step
in
that
is
to
promote
that
to
an
epic
and
start
breaking
this
down
into
actionable
issues
to
get
the
engineering
teams
engaged.
I.
Think
I'm,
gonna,
probably
schedule
a
meeting
early
next
week
to
assure
that
happens,
just
walk
through
it
with
engineering
management
engineers
who
they
want
to
bring
along
for
the
ride,
and
we
can
start
trying
to
really.
You
know
decide
on
how
we're
gonna
implement
these
over
the
next
couple.
A
Release
cycles:
what's
gonna
go
where
and
how
we're
gonna
actually
they're
off
the
door
cuz.
That's
that's
the
next
major
point.
I'm
I've
heard
a
lot
of
feedback
from
everyone
that
this
is
something
they
want
to
see,
come
out
and
I.
Think
J.
Jewell
is
also
on
the
call
for
people
who
don't
know
him.
He
works
on
an
inside
sales
group
and
he's
talked
to
a
lot
of
customers
interested
in
requital
mismanagement
as
well.
A
So
again,
if
we
have
questions
about,
you
know
what
market
this
is
for
or
what
you
know
potential
customers
can
we
talk
to.
You
know
he's
been
great
about
setting
up
some
interviews
with
me.
It's
been
a
huge
help
to
get
and
talk
to
these
customers
and
really
get
a
a
good
feel
for
what
they're
looking
for.
A
Of
q1
I'm
hoping
to
be
able
to
be
at
the
point-
that's
basically
three
months.
So
that's
this
really
cycle,
plus
two
more
I
am
very
much
hoping
to
have
the
ability
to
create
requirements
and
the
ability
to
tackle
and
solve
the
problem
of
tracing
those.
Two
tests.
I
think
that's
something
we
need
to
figure
out.
I
think
we
need
to
get
a
research
spike
together
to
sort
of
span.
A
12
eight
12,
nine
sort
of
a
three-week
chunk
in
there,
where
we
figure
out
how
exactly
we're
linking
things-
and
it's
not
just
us,
there's
other
other
parts
of
the
organization
that
are
trying
to
start
to
get
ties
together.
I
know,
release
governance
and
those
types
of
things
are
being
asked
a
lot
and
that
has
ties
in
the
same
method,
so
I
would
love
to
from
requirements.
Perspective
have
crimes
created
the
ability
to
trace
tiers
of
requirements
down
to
pests,
and/or
code
files.
A
D
A
project
within
this
space
that
I
cover
our
customers
are
asking
for
it,
and
this
is
this-
is
a
major
game
changer
for
them
to
be
able
to
use
a
requirements
tool
within
gitlab
and
to
increase
their
visibility
within
the
lifecycle
and
again
using
one
pane
of
glass,
as
I
like
to
say
from
start
to
finish,
and
adding
requirements
and
quality
management
on
is
gonna,
be
a
game
changer.
So
it's
it's
very,
very
important.
I
want
to
thank
you
for
doing
that.
A
Jay
so
yeah.
If
there's
no
more
questions,
I
mean
we
don't
have
to
take
all
the
time,
and
now
the
agenda
is
read
right.
Hopefully,
okay,
actually
I
questions
ahead
of
time
and
I'll.
Try
to
you
know
coming
in
beforehand
and
add
a
few
comments.
You
know
I'm
happy
to
discuss
whatever
we
need
and
just
yeah
I
want
to
keep
this
going
and
as
we
get
this
rolled
out,
I'd
love
to
be
able
to
do
this
from
instructional
chunks
of
this
too.
So
maybe
the
first
five
minutes
will
tackle.
A
You
know
all
the
questions
we've
got
and
you
know
we
get
a
lot
of
questions
on
a
specific
feature.
Maybe
I'll
put
together
a
couple
slides
and
sort
of
present
that
as
a
you
know
to
that,
whoever
wants
to
join
from
the
company
just
that
we
can
make
sure
we're
getting
this
rolled
out
efficiently
and
sure
that
we're
all
talking
the
same
language,
because
I
think
that's
pretty
important
as
we
go
to
market
with
this.
A
B
A
A
Gonna
try
to
schedule
on
more
midweek,
ideally
because
I
think
Friday's
for
a
lot
of
people
are
hard
or
they
want
to
just
spend
Friday
trying
to
get
everything
done
before
the
weekend
since
were
worried
about
it.
So
I
was
going
to
try
to
move
on
so
that
maybe
we
do
like
Tuesdays
or
Wednesdays,
which
can
be
kind
of
busy,
but
do
like
in
the
morning
ish
one
week,
my
time
so
it'll
be
like
8
a.m.
A
A
Awesome
well,
hey
thanks
a
lot
I'll
stop
the
recording
and
I
will
go
ahead
and
post
this
to
unfiltered.
I
think
this
can
go
public
I,
don't
see
any
issue
with
that.
If
we
start
talking
about
customers
ever
just,
let
me
know
if
there's
concerns
and
we
will
we'll
post
it
internally.
Only
thanks
a
lot
thanks.