►
From YouTube: Requirements management proposal by Sid, GitLab CEO
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).
A
Hey
I'm,
Sid
CEO
at
gate,
lab
and
I
want
to
talk
about
requirements.
Management
requirements.
Management
is
something
that
is
very,
very
important
to
our
customers.
Many
of
our
customers
are
in
regulated
industries
and
they
have
to
show
that
their
software
addresses
all
the
requirements
they
defined
up
front
and
I
think
there
is
a
much
simpler
way
to
do
that
than
what
they
have
to
do
today.
Today
they
have
to
use
an
external
product
like
IBM
doors
or
something
like
that
to
prove
this
chain
and
I
think
get
lab
already.
A
Has
all
the
elements
necessary
to
do
requirements
management,
except
that
we
need
to
tie
them
together?
We
have
issues
in
which
you
can
define
the
requirements.
We
have
great
CI
and
running
tests
which
make
your
able
to
test
the
code
to
make
sure
they're
addressed,
and
we
have
release
engineering
which
releases
and
things
like
that
to
make
sure
that
you
can
see
what
software
got
released
and
we
got
to
tie
that
together.
So
I
think
the
idea
is
you
define
your
requirements
in
an
issue?
A
Is
you
have
a
number
when
you
implement
that
requirement
in
this?
In
the
testing
code,
you
leave
a
comment
in
the
testing
code
that
has
the
issue
number
in
it.
Then
what
get
lab
should
be
able
to
do
is
that
when
you
release
a
version
of
your
software,
get
lab
knows
what
version
you
release.
It
knows
what
tests
it
ran
on
that
version
it
can
scan
in
like
the
build
logs
it
can
scan
for
those
issue
numbers.
A
A
Now,
building
that
that
we
need
to
kind
of
parse
the
build
logs.
That
might
be
the
hard
part
about
this,
but
other
than
that
I
think
we
have
a
lot
of
things
in
place
for
our
customers
to
show
hey.
This
release
addresses
all
the
quirements
me
set.
Another
thing
that
might
be
needed
for
this
is
that
we
have
to
label
issues
as
a
requirement.
A
Just
add
a
label
requirement
so
that
we
know
kind
of
hey.
If
this
issue
number
is
not
present
in
the
build
logs,
then
something
went
wrong.
You
should
be
able
to
kind
of
download
that
build
law
that
the
log
is
a
CSV
file
or
so
something
like
that
Scott,
it's
not
your
area.
It's
not
my
area
about
any
initial
reaction.
B
A
I
think
they
should
go
to
releases
and
in
releases
show
that
an
alternative
would
be
to
go
to
the
environment.
But
environments
is
more
for
software
as
a
service
and
I
see
in
a
lot
of
regulated
industries.
The
software
runs
at
an
and
an
appliance,
whether
that's
an
aircraft
or
an
Internet
of
Things
device,
or
something
like
that.
So
the
software
is
not
run
as
one
software
as
a
service,
but
it's
frequently
shipped
to
all
kinds
of
devices.
A
A
B
A
It's
I
think
it's
mostly
the
title
tends
to
be
something
like
compliance,
compliance
engineer
or
something
like
that,
and
there
are
the
people
that
are
making
sure
that
it
addresses
all
use
case
and
it's
very
common
in
automotive,
aerospace,
medical
industry
anywhere,
where
you
have
like
big
machinery
that
can
cause
a
lot
of
damage.
Okay,
you
tend
to
have
these
things
great
cool.