►
From YouTube: UX Showcase: Access, Compliance, and Analytics
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
B
A
It's
been
quite
exciting
and
I'm
excited
to
see
Austin
take
over
and
see
where
it
goes
from
there.
So
the
first
one
that
we
were
doing
was
a
feature
where
we
needed
to
make
sure
the
project
when
it
was
officially
deleted,
was
actually
deleted
and
not
just
sitting
in
limbo.
There's
been
a
large
request
for
this
feature
to
whenever
you
currently
delete
something
in
the
system.
It'll
sit
there
for
a
time
before
it
decays
and
that
causes
problems,
compliance
because
the
acts
the
data
is
still
accessible,
and
you
can
still
view
the
project
and
contents.
A
So
having
this
feature,
deleting
something
instantaneously
was
a
feature
that
we
needed.
The
next
item
here
is
to
personal
it
approvals
for
settings
and
changes.
So
if
you
were
to
make
a
change
in
the
setting
that
a
project
currently
there's
no
way
to
track
that,
so
what
we
wanted
to
do
is
have
a
way
to
inventory
at
that
data,
especially
again
in
regards
to
compliance.
A
We
have
another
issue
where
SSH
and
p80
expirations,
two
main
tokens
have
expressions
the
problem
before
we
didn't
have
a
way
to
track
this
data
and
if
we're
looking
to
see
when
a
user
or
a
token
or
an
SSH
key,
has
validity
or
access
to
a
project
or
a
group,
there
needs
to
be
a
way
to
track
that
and
to
see
when
that
times
time
frame
is
going
to
lapse.
That
will
allow
us
to
renew
the
license
to
renew
the
key,
if
needed,
or
understand
why
it
was
removed.
A
So
in
this
case,
sometimes
tokens
are
revoked.
If
there's
a
security
concern
or
just
expired,
because
somebody
forgot
about
it.
So
we
want
to
be
able
to
track
that
inventory
and
see
the
things
aren't
going
stale
in
our
projects
and
making
sure
that
there's
no
sketchy
access
being
had
so
another
one
is
allowing
mr
s
to
pull
an
external
service.
A
So
this
is
something
where
we
want
to
allow
a
organization
to
export
or
send
a
mr
check
out
to
an
auditing
body
of
an
auditing
source
within
their
own
organization
or
through
api's
that
they
have
in
in-house,
which
would
allow
a
organization
to
do
a
check
or
audit
on
the
mr
that's
being
passed
to
them.
This
would
allow
them
to
basically
validate
or
have
another
check
off
in
their
compliance
organization.
A
Next,
there's
the
approval
status
of
pipelines
warning,
and
this
is
taking
pieces
from
the
merge
request
window
and
bringing
it
into
the
compliance
dashboard
that
we're
building.
So
currently,
it's
easier
to
see
things
in
this
particular
view,
because
auditors,
this
is
a
new
profile
or
the
new,
a
persona
we're
making
others
don't
necessarily
need
to
see
all
the
data
associated
to
the
entire
merge
request
list
as
well.
That
doesn't
necessarily
provide
anything
specific
to
compliance.
A
So
another
issue
here
we
have
is
to
allow
admins
to
scope
how
the
mr
approvals
are
done,
and
this
is
part
of
the
feature
that
we're
expanding
on.
In
regards
to
compliance
frameworks,
we
have
a
number
of
frameworks
that
we're
trying
to
work
with
and
to
allow
certain
problems
to
be
enforced
on
the
compliance
depending
on
which
framework
is
needed
is
quite
helpful.
So
this
would
allow
us
to
only
focus
specific,
merge
requests
to
say.
A
I
only
want
Hitman's
for
this
particular
project,
as
well
as
I
only
want
to
allow
the
author,
or
only
allow
commissioners
to
make
the
approval.
So
a
number
of
changes
to
flexibility
which
didn't
exist
before
this
feature
and
again
all
these
features
are
coming
through
previous
research
and
interviews,
we've
done
with
clients.
A
lot
of
this
stuff
has
been
tested
and
is
gettin
quite
positive
reviews.
So
that's
always
good
to
hear
now
in
Access.
There
is
for
me
a
bit
of
a
learning
curve,
so
I'm
trying
to
come
into
the
project
as
it
just
started.
A
The
primary
concern
that
they're
having
right
now
is
regarding
permissions
inheritance,
and
this
is
related
to
some
work
that
Gabe
has
been
doing
in
regards
to
organizational
constructs.
So
why
things
don't
necessarily
work
between
groups
or
projects?
Why
is
there
segmentation
between
these,
how
things
receive
inheritance
for
your
security
or
your
access
whenever
you've
attached
yourself
to
a
group
where
you've
been
added
to
a
group
and
when
you
get
put
into
a
project
how
that
security
is
then
passed
on
to
anything
underneath
that
organization?
A
There's
a
case
study,
that's
been
done
with
organizations,
we've
been
doing
business
with
it's
an
internal
issue,
so
you
won't
be
able
to
see
it
if
you're,
not
as
I've
employee,
so
in
the
future,
we're
looking
to
try
and
make
this
a
little
bit
easier.
But
that
is
quite
a
monumental
task.
It
does
involve
again
reorganizing
some
of
the
structure
and
information
architecture.
B
A
So
in
the
next
steps,
again
working
with
Austin
to
try
and
get
him
on
board
for
the
compliance
and
work
that
we're
doing
so,
I
don't
basically
see
what
we've
done
so
far
and
how
to
pick
up
the
torch
and
move
forward
and
then
compliance.
This
focuses
in
a
shift
towards
continuing
the
dashboard,
but
expanding
the
scope
of
it
and
refining
some
of
the
functions
and
features.
There's
a
lot
more
features
that
we
need
to
put
into
the
dashboard
to
make
it
a
total
package
so
to
speak.
A
B
Swap
over
seamlessly
how
we
do
it
and
manage
okay,
so
my
name's
Nick
post
I
work
in
managed,
analytics
and
I
just
wanted
to
do
a
little
Whistlestop
tour
of
some
of
the
stuff
that
I've
been
working
on
I've
been
asked
a
number
of
times
like
what
is
analytics
and
and
why
is
it
different
from
from
monitor
all
this
sort
of
stuff?
So
I
wanted
to
do
like
a
little
low
differentiation?
How
I?
B
How
I
think
about
what
analytics
does
our
purpose
is
a
stage
group
number
one
is
we're
focusing
on
value
stream
management,
which
is
a
big
thing
where
we're
effectively
mapping
the
entirety
of
the
software
developer,
lifecycle
from
the
start
of
creating
an
issue
all
the
way
through
to
implementation
and
having
some
sort
of
value
in
front
of
the
customer.
So
that
requires
a
level
of
visualization
and
understanding
to
see
whether
you
can
unblock
stuff,
which
is
going
through
your
value
stream
and
get
insights
into
whether
you're,
improving
all
that
sort
of
stuff.
B
So
one
element
to
that
is
that
as
I
just
mentioned
visualizing
this,
but
another
element
of
this
is
actually
taking
the
insights
that
we
get
from
these
value
stream
calculations
and
bringing
them
into
everyday
workflows.
So,
for
example,
what
is
the
average
time
that
it
takes
for
an
issue?
To
close,
can
we
embed
that
within
the
issue
workflow
so
as
you're
working
actually
within
an
issue?
You
know
that
this
is
25%
taking
longer
than
the
normal
issue
within
this
group.
B
So
one
is
visualizing
the
stuff
and
then
another
side
is
actually
taking
those
and
embedding
those
insights
within
the
workflows
to
make
them
a
little
bit
more
actionable
as
well.
So
that
is
the
category
of
value
stream
management.
Now
Madeline
manager
analytics
were
also
helping
to
create
general
general
capability
of
data
visualization
and
analytics
across
the
product
that
all
stage
teams
and
users
eventually
can
use.
B
And
all
this
lovely
stuff
themselves,
for
particular
data
sets
that
they
are
specifically
interested
in
meaning
that
that
it
becomes
much
more
relevant.
The
data
that
they're
getting
yeah
so
value
stream
management
and
general
data
visualization
good
stuff.
So
a
few
things
I'm
working
on
within
value
stream
management,
one
is
undoing
solution,
validations,
I've,
spoken
with
a
few
users
around
to-do
lists
and
know
patience
and
the
rationale
behind
working
on
the
solution.
B
My
ideas
for
how
we
can
improve
to-do
lists
notifications
and
some
analytics
and
metrics
that
go
along
with
that
I'm
also
doing
some
general
feature
work
around
improving
what
we
have
the
value
stream
management
at
the
moment,
which
is
not
much
but
giving
users
the
capability
of
creating
multiple
value
streams
within
a
single
group.
They're
only
allowed
to
do
one
at
a
time
at
the
moment
and
then
also
improving
different
experiences
to
configure
what
they
see
around
this
tasks
by
type
chart
doing
a
label
selection
experience.
B
What
we're
focusing
on
moment
is
the
report
object,
I've
done
a
bunch
of
documentation
around
the
report,
object
to
the
moment
and
what
the
report
object
is
is
effectively
when
you
drill
down
from
a
metric
or
a
chart
into
the
granular
data
set.
A
report
is
basically
the
place
where
you
end
up,
and
that
holds
the
granular
data
set
in
some
way.
So
we
we
have
started
to
build
these
pages
out
in
a
sort
of
generic
way.
B
Starting
with
insights
and
also
group
activity
is
the
first
sort
of
applications
of
the
product
started,
documenting
that
and
then
the
typical
iteration
path,
we're
sort
of
hypothesizing
will
be
create.
The
drill-down
experience
allow
charts
to
be
embedded
within
the
handbook
and
then
allow
charts
within
the
handbook
to
drill
down
into
particular
data
on
pages
and
then
start
to
create
a
library
of
each
poor
pages.
B
So
the
report
object
itself
is
providing
sort
of
some
guidance
and
overview
into
what
the
components
were.
Focusing
our
efforts
on
at
the
moment.
That's
why
you'll
see
I'm
working
alone
on
different
charts
and
improving
the
functionality
of
charts
and
all
this
other
stuff
here.
So
finally,
just
to
summarize
manager
analytics
works
on
value
stream
management,
which
is
the
category
and
then
general
data,
vis
UX,
which
is
what
I'd
call
a
capability.
B
So
let
me
know
if
you
plan
on
using
a
report,
object
or
a
dashboard
anytime
soon,
and
maybe
would
collaborate
on
that
and
let
me
know
if
your
state
can
benefit
from
any
sort
of
value
stream,
metrics
or
calculations
in
the
context
of
your
workflows
as
well.
I'm
super
open
to
collaborating.
Give
me
a
shout
and
I
wanted
to
also
chuck
out
a
special
thank
you
to
Tori,
Jeremy
elder
and
Ayane
for
guiding
me
through
the
process
of
contributing
to
to
pyjamas
on
only
this
chart
stuff.