►
From YouTube: Compliance: Change Management design proposal
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
austin,
I'm
a
product
designer
here
at
git
lab
today,
I'm
going
to
cover
an
issue
around
change
management
that
we've
been
ideating
on
to
start
off
I'll,
introduce
cameron,
our
compliance
manager
so
cameron's
a
persona.
We're
focused
on
in
this
scenario
cameron's
frustrated
because
it's
difficult
to
aggregate
like
the
reports
around
what
he
cares
about
he's,
trying
to
better
understand
their
posture
and
preparing
for
compliance
audits,
and
to
do
that.
It
takes
a
lot
of
manual
effort
today
to
begin
alleviating
this
pain
point.
A
We
introduced
a
compliance
dashboard
several
releases
ago
and
it's
a
simple
view
right
now.
Primarily
it
tells
you.
The
latest
merge
request
for
a
specific
project,
as
it
relates
to
a
group
so
for
gitlab
work.
We
have
a
couple
projects,
gitlab
shell
and
gitlab
test,
and
it
shows
the
most
recent
merge
requests
for
each
of
these.
We
can
see
that
the
approval
status
was
not
adhering
to
one
of
the
rules
for
separation
of
duties
and
that
their
latest
pipeline
failed.
A
A
So
each
of
these
answers
is
a
specific
question
related
to
that
I've
marked
off
the
ones
that
we
kind
of
can
answer
today.
So
an
example
is
if
you're
looking
to
know
who
made
a
specific
change
in
a
merge
request.
You
could
technically
create
this
report
that
gives
you
a
csv
of
all
the
merge
commits.
You
would
be
able
to
find
an
author
in
there.
That
tells
you
who
made
what
changed
so
technically,
you
can
get
the
answer,
but
there's
a
lot
of
there's
some
more
manual
work.
A
You'd
have
to
do
for
something
like
how
did
it
affect
the
code?
Quality
you'd
have
to
come
here
and
you
have
to
go
into
the
dashboard
and
then
like
go
find
this
specific,
merge
request
and
then
look
at
it
and
figure
out
what
changed,
obviously
showing
the
most
recent
one
isn't
super
helpful,
because
as
soon
as
a
new
merch
request
comes
in
this
one
won't
be
seen
anymore,
and
then
you
won't
know
about
it.
It's
now
off
your
radar.
A
A
For
sake
of
this
simple
presentation,
we're
flagging
a
merge
request
if
it's
violated
one
of
our
compliance
rules
that
we've
built
into
the
system.
So
in
this
example
the
fixed
scaling
ruby,
not
starting
on
tests,
it
has
separations
of
duties
where
one
rule
isn't
adhering.
We
have
a
failed
pipeline
and
we've
had
the
code
coverage
decrease.
A
A
A
If
the
same
person
that
approved
it
was
the
same
person
that
merged
it
or
maybe
how
long
someone
was
spending
in
a
review,
we're
trying
to
elevate
the
things
that
cameron
cares
about
in
this
drawer
and
give
them
access
to
it
as
you're
triaging,
the
number
of
merge
requests
that
go
into
production
that
way
they
know
they
won't
get
any
nasty
surprises
when
they
get
around
to
the
audit
phase,
because
they've
already
been
managing
these
things.
A
I'm
interested
to
hear
your
thoughts
on
how
this
view
resonates
with
you.
If
you
think
introducing
a
drawer
as
a
way
to
answer
questions
is
valuable
or,
if
you
think,
there's
another
way
to
do
it.
What
I
was
trying
to
do
is
focus
on
showing
the
most
important
information
on
the
page
and
then
giving
a
quick,
accessible
way
to
find
key
highlights
that
relate
to
that
specific
merge
request.