►
From YouTube: Commit Virtual 2020: Accelerating Speed to Mission through Low to High Cross Domain Collaboration
Description
Speaker: Marc Kriz
Government development teams need the ability to work seamlessly across disparate network enclaves, with all artifacts, issues, and code intact as if they were working on the same DevSecOps project. How can they accelerate their speed to mission without compromising security?
Discover how two Intelligence Community organizations empowered their teams with seamless collaboration across enclaves to dramatically increase their delivery on the mission.
Get in touch with Sales: http://bit.ly/2IygR7z
A
Government
development
teams
need
the
ability
to
collaborate
across
domains
across
enclaves
across
classifications,
but
how
do
they
do
that
and
still
keep
all
of
their
materials
repositories?
Artifacts
code
still
intact,
mark
chris
with
gitlab,
is
going
to
talk
to
us
about
accelerating
speed
to
mission
through
low
to
high
cross-domain
collaboration
and
he'll
show
us
a
few
stories
about
how
the
intelligence
community
is
doing
that
right.
B
B
But
what
I'm
really
here
to
do
is
to
tell
a
story,
a
story
of
a
group
of
summer
interns
that,
when
they
were
equipped
with
get
lab,
seamless,
end-to-end
devsecops
solution,
they
were
able
to
work
seamlessly
on
the
low
side
and
make
an
immediate
mission
impact
on
the
high
side.
For
this
particular
agency
mission
group.
B
Now
the
goal
of
this
presentation
is
pretty
simple.
Your
time
is
valuable,
and
I
want
to
thank
you
for
taking
this
time
to
spend
it
with
me.
So
my
commitment
to
you
is
to
deliver
a
conversation
in
a
story
that
has
real
lessons,
learned
real
tips
and
tricks
that
you
can
take
away
and
remember
this
isn't
a
how-to
guide,
but
it's
a
story,
it's
a
journey
and
it
has
outcomes
that
exceeded
expectations.
B
They
had
another
goal
for
this
program,
however,
which
was
the
government
leadership
of
the
agency,
wanted
a
way
to
make
their
summer
intern
programs
more
effective.
So
they
could
get
this
young
talented
group
of
individuals
excited
about
a
future
career
path
with
the
agency
so
picture.
If
you
will
17
summer
interns
from
colleges
and
universities
all
over
the
area,
they
bring
them
all
together,
and
they
explained
that
and
again
this
was
pre-coveted,
so
they
had
an
option.
B
They
brought
them
together
and
said
you
can
work
over
the
summer
from
an
unclassified
facility
with
one
of
our
agency
partners
here
or
you
can
work
remotely,
because
that
that
situation
of
that
office
didn't
geographically
serve
all
of
those
college
interns.
Some
of
them
were
living
at
home
with
their
parents
over
the
summer.
Some
of
them
were
living
in
dormitories.
Some
of
them
were
limit
living
on
campus
for
the
summer,
so
they
had
to
work
from
all
different
places.
What
was
interesting
about
this
group
was
that
they
had
a
diverse
background.
B
They
were
majoring
in
a
lot
of
different
disciplines,
everything
from
political
science
to
sociology
to
data
science.
In
fact,
out
of
the
17,
only
one
of
them
had
a
background
in
computer
science,
and
none
of
them
had
a
background
in
git
lab
now.
What
was
interesting
was
the
program
was
only
going
to
run
for
90
days
over
the
summer,
so
it
had
to
start
quickly.
B
The
agency
program
had
some
requirements
for
their
program.
One
is
that
they
needed
it
to
have
a
quick
start,
because
it
was
only
90
days
in
duration.
Also,
the
branch
chief
from
the
government
program
office
wanted
to
have
visibility
into
what
his
interns
were
doing,
what
kind
of
work
they
were
doing.
He
wanted
to
have
this
daily
visibility
into
their
work,
their
priorities
and,
most
importantly,
their
results.
B
So
imagine
a
group
of
interns
they
have
to
work
on
the
low
side.
They
want
to
be
able
to
collaborate
together
easily
and
they
want
to
be
able
to
change
course
if
their
research
was
taking
a
direction
that
they
wanted
to
iterate
on.
They
needed
to
have
a
way
to
be
able
to
do
that
quickly.
B
So
now
the
story.
So
here
we
are
it's
it's
a
first
day
of
the
summer,
the
17
interims
are
brought
together
in
a
big
conference
room
in
that
unclassified
partner
facility,
and
all
of
them
are
sitting
around
this
large
conference
table,
none
of
them
with
any
get
lab
experience.
So
what
we
had
done
ahead
of
time
is.
We
had
worked
with
the
agency
to
set
up
an
instance
of
get
lab
on
the
low
side.
B
We
gave
them
all
accounts
so
that
on
day
one
when
we
brought
them
all
together,
we
were
able
to
do
a
four
hour.
Quick
start
get
lab
training
for
them,
which
allowed
them
to
understand
very
quickly
how
to
use
git
lab
what
the
interface
looked
like.
Now,
here's
the
good
news
about
the
get
lab
solution.
B
B
They
began
to
tag
each
other
and
at
mention
each
other
in
those
issues
and
what
was
exciting
was
they
also
took
the
topics
for
their
research
project
that
were
given
to
them
by
the
branch
chief
and
they
created
an
epic
and
get
lab
for
each
one
of
those,
so
they
created
an
epic
and
organized
themselves
very,
very
quickly.
So
then,
at
the
end
of
the
day
picture
this,
they
all
leave
the
conference
room
and
they
all
go
back
to
their
individual
workspaces
on
the
low
side.
B
Now
the
work
begins,
so
they
began
to
collaborate
and
what
they
found
using
git
lab
on
the
low
side
is
that
they
would
start
their
day
with
their
to-do
list
in
git
lab.
So
they
would
bring
up
their
account.
They
would
click
on
the
to
do
drop
down
and
they
would
look
at
all
of
the
things
that
they
had
been
tagged
in.
So
maybe
there's
issues
that
they
have
been
assigned.
Maybe
there's
issues
within
gitlab.
B
You
can
easily
create
a
task
list,
so
these
interns
would
create
these
lists
of
tasks
and
assign
each
other
to
those
tasks,
and
then
they
began
to
use
the
project
repository
to
drop
their
research
artifacts
into
so
this
gave
them
a
way
to
quickly
collaborate,
and
the
other
thing
that
they
discovered
in
this
workflow
was
that
even
though
they
were
all
dispersed
geographically
and
and
different
locations,
they
actually
began
to
communicate
asynchronous
asynchronously
together
and
that
gave
them
the
ability
to
work
at
different
hours,
but
yet
not
lose
any
of
that
rapid,
workflow
and
iteration
and
bouncing
ideas
off
each
other.
B
Now
the
impact
so
imagine
that
the
branch
chief
is
wanting
to
see
how
this
work
is
going,
but,
most
importantly,
he
wants
to
start
applying
the
results
of
their
research
to
his
current
way
of
doing
business.
So
what
they
would
do
is
using
the
get
lab
interface,
they
would
actually
use
a
capability
called
the
get
lab
project
import
export
archive
capability.
B
This
is
our
unique
differentiator
that
allows
for
that
seamless
low
to
high
collaboration.
So
what
they
would
do,
the
interns
would
click
on
the
the
get
lab
drop
down
at
the
project
level
and
they
would
archive
their
project
now
what
our
our
technology
does
is.
It
takes
not
only
the
repo
and
all
the
the
files
in
that
repo,
but
it
takes
all
the
artifacts
and
bundles
all
those
together
so
think
about
this.
B
B
So
what
are
some
of
the
outcomes
and
lessons
learned
well,
first
of
all,
by
being
equipped
with
get
lab
ultimate
and
instance
on
the
low
side,
those
interns
got
off
to
a
really
fast
start.
Remember
I
mentioned
the
whole
project
was
90
days
start
to
finish
well,
these
interns
began
working
quickly
together
by
using
get
lab
to-do
list
and
get
lab
issues.
They
were
able
to
collaborate
easily
and
dan.
The
branch
chief
was
able
to
get
visibility
into
what
he
needed
to
see
his
interns
doing
so.
B
B
Now,
what
that,
in
turn
translated
to
was
all
all
of
those
interns
felt
like
they
were
making
an
impact
like
it
wasn't
just
a
summer
intern
program
that
they
were
used
to,
where
a
lot
of
it
might
be
just
busy
work.
They
were
actually
making
a
real
mission
impact
and
that
led
to
a
really
happy
group.
It
was
a
high
morale
within
the
team
and
several
of
them
indicated
interest
in
continuing
to
do
work
for
the
agency.
B
So
what
are
some
lessons
learned?
Well,
the
technology
doesn't
by
itself
change
culture
to
be
agile
and
collaborative,
but
it
is
an
enabler
so
get
lab
ultimate,
and
our
capability
for
seamless
low
to
high
development
really
enabled
this
summer
intern
program
to
be
as
successful
as
it
was.
B
It
also
gave
the
ability
for
those
interns
to
start
quickly
and
it
gave
leadership
the
ability
to
actually
assign
an
account
a
user
account
for
their
program
manager,
who's
working
on
the
high
side.
They
gave
those
program.
Managers
accounts
on
the
low
side
instance
so
that
they
could
interact
in
those
issues
and
those
to-do
lists,
etc
on
the
low
side
as
well,
and
that
really
created
this
nice
liaison
between
the
low
and
the
high
side.
B
The
other
thing
is
by
using
git
lab.
It
helped
influence
a
cultural
change
in
minimal,
viable
change,
so
the
interns
be
became
used
to
getting
an
idea
quickly
out
there
amongst
their
peers
to
to
collaborate
on
test
their
hypothesis
get
feedback
on
it
and
then
change.
If
change
was
needed
quickly
and
by
getting
everybody
involved,
it
got
everyone
on
to
the
same
page
or
the
same
version
of
the
truth.
B
So
git
lab
is
an
end-to-end,
complete,
devsecops
solution
and
because
they
didn't
have
to
leave
the
gitlab
interface
to
go
to
other
siloed
products,
they
were
all
on
the
same
page
all
day
long
and
that
really
accelerated
their
success.
So
the
summer
ended.
The
program
was
a
huge
success
and,
most
importantly
to
the
government
leadership.
B
So
if
you're
a
government
leader,
if
you're
a
system,
integrator
a
thought
leader,
I
would
challenge
you
to
take
a
look
at
how
you
can,
especially
in
the
midst
of
this
pandemic.
B
How
can
you
take
get
lab's,
seamless,
high-to-low
capability
and
employ
that
in
your
program,
because
again,
the
technology
doesn't
change
the
culture,
but
the
right
technology
can
enable
that
cultural
shift.
Ladies
and
gentlemen,
thank
you
very
much
for
the
time
and
I
look
forward
to
joining
you
in
the
live.