►
From YouTube: TT210: Create and Plan
Description
YouTube description:
This is a Tanuki Tech session on 9/22/2020.
For more on Tanuki Tech, see here: https://about.gitlab.com/handbook/marketing/revenue-marketing/sdr/tanuki-tech/
For more on the speaker, see here: https://www.linkedin.com/in/christopher-wang-0835b226/
B
Today,
one
thing
I'd
like
to
say
is:
I
think
that
some
of
the
things
here
are
going
to
be
review
for
people
who've
been
here
longer,
so
feel
free
to
you
know,
just
let's
sort
of
say
like
hey.
I
already
know
this
or
you
know
we
can
take
this
conversation.
However,
you
want,
I
want
to
see
how
I
can
add
to
your
day,
but
today's
what
we're
going
to
talk
about
is
creatine
plan.
B
So
what's
creating
plan
and
what's
our
goal
for
today,
so
our
goal
is
always
the
same:
have
better
sales
conversations?
How
are
we
going
to
do
that
so
create
and
plan
is
our
sem
and
our
agile,
ticketing
solutions
and
the
whole
idea
is
understand
these
better
understand.
Customer
questions
better
understand
why
they're
asking
certain
things
and
how
we
can
use
these
questions
to
show
gitlab
value
right.
B
So
I
do
think
that
some
of
this
will
be
recap
from
next
from
last
quarter.
Just
let
me
know
if
this
is
stuff
that
you've
heard
before,
but
yeah,
so
how
we're
gonna
do
this?
We're
gonna
understand
what
this
is
from
a
technology
perspective,
but
the
most
important
thing
is
asking
the
question
of
like:
why
are
customers
actually
asking
some
of
these
things
right?
So,
if
they're
asking
for
clustering
or
if
they're
asking
for
h
a
then,
why
do
they
care?
B
B
I
think
that
that's
one
of
the
challenges
with
understanding
our
product,
there's
literally
10
different
product
categories,
and
what
we're
specifically
talking
about
today
is
these
two
product
categories,
and
just
to
translate
them
create,
is
all
of
our
sem
technology
and
features
and
plan
is
all
of
our
agile
stuff.
So
epics
issues,
you
know
time
tracking
and
things
like
that,
and
once
again
the
goal
today
is
to
figure
out.
Why
is
this
important
for
people
when
someone
asks
you
a
question?
What
are
they
actually
looking
for,
and
how
can
we
articulate
how
we
can
help?
B
So
one
of
the
things
I
always
like
to
just
like
start
off
with
is
like
well,
I
actually
first
have
a
question
for
you
all.
So,
like
you
all
get
a
ton
of
customer
questions,
I
think
everyone
in
this
call
is
in
from
emilia
except
for
me.
I
know
that
you
all
have
a
lot
of
inbound.
So
what
percentage
of
your
customer
questions
in
your
region
are
actually
about
our
sem
and
issue
ticketing?
Is
it
like
half?
Is
it
about
a
third
like
you
know,
in
terms
of
your
conversations
right
now?
C
I
think
it's
quite
high.
To
be
honest,
I
mean
because
especially
in
smb,
because
we
are
mostly
talking
about
the
startup
runs
and
the
civil
plan
and
ticket
management
and
issues,
and
everything
regarding
this
is
always
something
they
are
trying
to
figure
out
how
to
make
it
better
and
sometimes
involving
project
manager
if
the
teams
are
bigger,
but
it's
always
a
conversation.
It's
always
very
interesting
to
see
how
they're
doing
it
right
now
with
different
tools
or
multiple
tools
and
how
they
want
to
implement
it
with
gitlab.
So
it's
it's
very
high.
C
I
think
in
in
smb.
B
Gotcha
in
terms
of
these
conversations,
a
lot
of
times
like
a
customer
will
say
like
hey:
do
you
have
this
functionality
and
the
conversation
will
depend
on
it
because
they
need
it
out
of
scm
in
our
ticketing
solutions?
How
often
does
that
happen
where
it's
just
sort
of
like
the
next
conversation
depends
on
whether
or
not
we
can
do
something
out
of
our
sem
our
ticketing.
B
Yeah
gotcha
all
right
thanks
for
that.
I
think
that
that's
really
interesting
there's
a
difference
in
perspective
between
europe
and
america.
So
that's
good
for
me
to
know.
Let
me
talk
to
you
about
just
sort
of
like
the
industry
behind
these
right.
So
obviously
this
is
the
reason
why
I
started
out
with
these
two
feature
sets.
Is
this
fundamental
part
of
our
value
proposition?
B
What
makes
gitlab
gitlab
is
the
fact
that
we
have
sem
and
issue
tracking
all
built
into
the
same
tool
right
and
that's
really
important
for
people
just
like
from
taking
a
more
general
industry
perspective.
One
thing
to
know
is
that
we
do
operate
in
crowded
markets
for
both
of
these,
and
so,
if
you
just
take
a
look
at
this
image
on
the
bottom
right,
there's
a
lot
of
different
like
people
who
do
very
similar
things.
I'll
just
give
you
an
example.
B
So
over
here,
I
just
typed
into
google
best
project
management
software
and
you
get
a
list
of
40
best
project
management
tools
and
the
big
problem
with
this
is
that
you
know
you
don't
want
to
be
competing
against
40
different
other
people,
especially
some
of
these
people.
They're
really
hungry.
Some
of
these
companies
they're
really
hungry.
They
put
all
their
development
into
their
project
management
tool
and
that's
where
they
get
all
their
revenue
from
right.
So
what
we
don't
want
to
do
is
to
go
up
against
all
of
these
different
tools.
B
What
we
do
want
to
do
is
to
deliver
the
message
that
we're
different
from
all
of
these
tools,
because
we're
one
tool
for
the
entire
devops
life
cycle,
and
we
have
everything
integrated
together,
because
that's
how
we
stand
out
from
all
those
different
companies,
so
yeah,
there's
tons
of
different
project
management
tools.
There's
a
lot
of
scm
tools.
B
The
markets
are
mature,
a
lot
of
different
mature
solutions
exist,
so
jira
came
way
before
get
lab
and
that's
part
of
the
reason
why
they
have
so
much
incumbency
and
our
real,
unique
differentiator
from
all
these
people
is
the
fact
that
we
are
one
integrated
solution.
So
do
we
have
differentiators
totally?
I
use
ton
of
my
messaging
and
the
fact
that
it's
one
integrated
solution.
If
I,
if
people
ask
about
the
individual
differentiators,
I
do
speak
about
them,
but
it's
not
how
I
lead
a
sale
all
right.
B
B
All
right
great,
so
I
got
a
lot
of
like
I
only
had
like
50
of
reaction,
so
just
go
over
real
quickly.
Fundamentally,
all
of
software
is,
is
it's
a
bunch
of
different
text
files
and
it's
really
kind
of
interesting
to
think
that
someone
could
be
getting
paid
like
80
to
100
euros
thousand
euros
a
year,
just
fundamentally
editing
text
files
right
and
so
what
I?
What
do
I
mean
by
that?
Well,
this
is
get
lab
itself
and
get
lab
fundamentally
is
around
several
thousand
text
files.
B
That's
all
gitlab
is,
and
so
over
here
is
the
text
files
that
actually
make
up
gitlab.
If
I
go
into
this,
this
is
one
of
these.
Like
several
thousand
text
files
and
fundamentally
all
these
text
files
are
doing
is
telling
machines
to
do
stuff,
so
it
could
be
turn
a
light
on
could
be
turn
a
button
on
could
be
create
a
folder
but
any
sort
of
software
application.
A
fundamental
level
literally
all
it
is-
is
a
combined
set
of
text
files.
B
So
this
is
get
lab
text
files,
as
you
can
see,
literally
what
developers
do
all
day.
Is
they
edit
these
text
files
and
that's
how
they
get
paid
their
value
to
a
company
is
creating
and
editing
text
files,
and
when
I
was
a
developer,
this
is
what
I
did
all
day
and
so
yeah
this
one
developer
is
literally
getting
paid
to
add
in
this
text.
Take
some
different
text
out.
So
the
big
problem
with
that
is
that
for
something
like
git
lab,
there's
a
bunch
of
different
problems
right
so
one.
B
If
you
just
think
about
like
a
lot
of
times,
we
have
these
amas
right
and
then
so
it
might
be.
100
people
in
marketing,
editing
the
same
text
file
and
what
happens?
It
gets
really
disorganized
right,
and
so
it
becomes
way
more
complicated
because
gitlab,
instead
of
just
one
text
file,
it's
actually
about
several
thousand
text
files
and
then
problem
number
two
is
as
opposed
to
having
a
hundred
people
editing
it.
We
have
around
3000
people,
editing
the
same
set
every
release
and
every
single
time
zone.
B
So
scm
is
a
tool
for
storing
these
text
files.
When
I
was
a
developer
for
half
a
decade
and
I'd
say
that
I
probably
spent
five
to
ten
percent
of
all
of
my
days
using
things
like
git
and
my
scm
tools,
I
actually
use
github
and
I
think
it's
important
to
understand
just
sort
of
like
where
this
fits
into
the
hierarchy
of
developer
tools.
B
So,
for
instance
like
sometimes
when
you're
an
engineer
or
like
a
welder
or
plumber,
you
have
tools
that
are
nice
to
have
and
then
sometimes
there's
tools
that
are
completely
necessary
for
your
job.
So
you
can't
be
like
a
painter
if
you
don't
have
brushes
right.
So
if
you're,
a
developer
sem,
is
completely
100
necessary.
There's
no
way
to
do
modern
software
development
without
sem,
and
it's
extremely
important
for
everyone's
developer
flow.
You
literally
spend
like
maybe
30
minutes
on
scm.
B
Every
single
day,
yeah
so
sem
is
a
tool
for
storing
these
text
files
over
here
in
the
bottom
right,
you
can
see
a
chart
on
the
market
share
for
the
different
tools
and,
as
you
can
see,
the
market
is
consolidated.
B
Consolidating
on
git,
I
used
to
use
git
all
the
time,
and
one
thing
I
say
about
it
is
that
it's
by
far
the
easiest
solution
and
I
believe
that
what
we're
going
to
see
in
the
next
couple
of
years
is
even
though
it
has
90
percent
the
market
share
right
now.
I
think
it's
going
to
have
95
percent
of
the
market
share,
because
it's
a
better
piece
of
technology,
all
right
so
gets
the
most
popular
piece
of
you
know
scm
tool.
We
already
know
that
get
labs
built
on
git.
B
One
thing
to
keep
in
mind,
though,
is
like
git,
is
open
source,
which
means
that
other
people
can
just
take
it
and
use
it
and
then
build
better
versions
of
it
and
then
sell
that
open
source
tool.
So
that's
what
gitlab
and
github
do
does
so.
Let's
talk
about
some
of
the
things
that
this
does.
This
should
be
a
review
for
a
lot
of
people
here
so
feel
free
to
try
and
just
let
me
skip
ahead
if
you
want,
but
one
problem.
B
B
Then
you
finally
added
in
citations
right,
so
that's
version
16,
and
then
you
have
your
final
draft,
but
then
you
need
to
change
something
and
then
there's
the
actual
final
draft
right,
and
so
the
big
problem
with
this
is
one.
I
have
20
files
which
I
don't
want
to
have
right
and
number
two.
This
is
really
unwieldy
right
and,
as
you
can
imagine,
for
a
gigantic
software
project
like
gitlab,
you
don't
have
one
essay
that
you're
trying
to
version
control.
You
have
maybe
5
000
different
files
that
you
need
to
keep
a
track
of.
B
So
there's
a
lot
of
complexity.
Here,
there's
no
way
the
solution.
Scales
problem
number
two
is
just
sort
of
like
imagine.
We
have
five
people
in
this
room
right
now,
but
imagine
we
had
to
all
write
some
big
essay
for
school,
so
we
divided
up
into
five
chunks
and
the
whole
idea
is
to
copy
and
paste
it
together.
It
should
be
easy
right,
but
what
ends
up
always
happening
is
that
people
make
changes
that
are
universal
to
the
entire
file
right.
So
three
people
might
change
the
font.
Two
people
might
change
like
the
styling.
B
One
person
might
make
it
double
spaced
and
then
so
it's
never
as
simple
as
just
copying
and
pasting.
Everything
in
someone
has
to
copy
and
paste
it
in
and
then
choose
like.
You
know
there
has
to
be
sort
of
like
rules
so
that
this
process
of
like
splicing
all
the
code
together,
is
actually
done
in
an
organized
manner.
So
it's
like.
We
have
five
people
right
now
in
this
group.
B
If
we
were
just
trying
to
copy
and
paste
some
essay
together,
we'd
have
to
like
come
to
a
meeting
and
figure
out
what
sort
of
spacing
we
wanted.
What
sort
of
font
we
wanted,
because,
ultimately,
a
bunch
of
people
would
be
editing
the
same
thing
right,
but
now
imagine
if
there's
around
3000
people
editing
get
lab
code,
as
you
can
see
over
here,
like
here's
all
the
merge
requests
that
come
in
right,
and
so
there
could
be
five
different
people
trying
to
edit
the
same
file.
B
There
needs
to
be
some
sort
of
tool
that,
like
organizes
all
of
that,
and
so
this
is
what
a
merge
request
is,
and
so
what
the
merge
request
is
actually
is
the
issue
I'm
looking
at
the
wrong
thing.
So
this
is.
This
is
a
merge
request
right
and
in
the
merge
request.
The
developers
are
are
basically
handing
in
their
code,
and
one
thing
I
like
to
say
about
this
is
that
this
is
especially
important
because
we
are
an
open
source
project.
B
People
try
to
hijack
open
source
projects
all
the
time
and
if
you
can
imagine
like,
let's
just
say
that
we
are
an
open
source
project,
it
is
theoretically
possible
for
our
competitors
and
for
other
businesses
to
try
to
hijack
our
roadmap
by
adding
in
code
that
either,
like
you
know,
tries
to
steer
us
into
a
bad
direction
or,
like
you
know,
is
gonna
like
so
they
have
like.
Our
competitors
literally,
can
submit
merge,
requests
in
the
gitlab
and
influence
like
how
the
product
works.
B
They
could
do
it
from
an
account
that
is
not
tied
to
like
microsoft
or
something
like
that,
and
so
people
actually
try
to
do
this.
So
another
thing
that
like
scm,
does
and
especially
for
an
open
source
project,
is
you
need
to
create
some
sort
of
gate
for
getting
coded?
Not
everyone
can
just
like
edit
our
files
right
and
so
what
the
merge
request
view
does.
Is
it
creates
a
mechanism
that
serves
as
a
gate?
So
if
we
just
go
back
to
this
merge
request
here,
not
everyone
can
just
edit
our
files.
B
These
are
all
git
lab
people,
so
this
prevents
people
from
you
know
some
from
either
a
competitor
or
someone
who
just
like,
doesn't
understand
the
road
map
of
our
product
from
you
know
doing
something
that's
going
to
be
detrimental
to
our
technology
right,
and
so
this
is
the
gate
that
sem
has
created
through
the
merge
request
view
yeah
in
real
software
development,
you
can
have
hundreds
of
people
working
on
the
same
project,
spread
out
across
10
different
time
zones
without
sem.
You
could
not
do
this.
B
There's
the
idea
of
like
a
master
branch
and
in
your
master
branch.
Is
your
current
and
best
running
version.
This
is
like
the
source
of
truth
right,
and
so
if
your
master
branch
gets
messed
up,
then
your
website
could
theoretically
stop
working.
So
you
need
to
protect
it,
and
so
people
don't
directly
edit
the
master
branch.
B
What
they
do
is
they
do
this
thing
called
branching
and
so
the
master
branch
lives
like
so
all
the
code,
which
is
the
master
branch,
lives
on
some
sort
of
centralized
server,
and
then
you
actually
only
edit
the
so
like
step.
One
is
you
do
this
thing
called
branching?
What
branching
is
is
a
copy
and
paste
all
of
these
text
files
from
the
master
branch
to
now.
B
Basically,
I
now
have
them
all
downloaded
to
my
macbook
right.
So
in
this,
after
I've
branched,
I
have
an
identical
set
of
text
files
between
the
master
branch
and
my
macbook,
and
I
actually
edit
my
the
text
files
that
are
my
macbook
and
not
the
ones
on
my
master
branch.
So
at
this
point
they
started
to
diverge
right.
So
I'm
a
developer,
I'm
working
on
my
stuff,
I'm
making
some
chart
every
time
I
hit
save
basically
hitting
save,
is
making
a
commit.
B
So
you
can
think
about
committing
and
saving
as
the
exact
same
thing,
and
so
I'm
making
my
chart,
I
make
some
progress,
hit,
save
or
commit
make
another
commit
after
I
fix
something,
and
then
I
made
a
final
commit
when
I'm
really
proud
of
my
work
right,
and
so
my
button's
done
my
chart's
done.
B
I
want
to
hand
my
work
in
which
is
ultimately
how
I
get
credit
as
a
developer,
so
I
have
to
go
through
now
this
gating
mechanism
right
and
that's
when
I
create
a
merge
request
and
and
then
so
merging
this
code
is
getting
these
three
commits
into
the
master
branch.
All
of
these
pull
requests
here,
it's
just
people
trying
to
get
whatever
changes
that
they
made
into
the
master
branch,
and
that
is
fundamentally
what
a
merge
request
does.
So
after
this
code
were
merged,
all
of
this
green
text
would
be
added
in
this.
B
So
yeah,
let's
just
talk,
let's
just
demo,
some
of
the
functionality
that
we
had.
So
I
remember
you
all
remember
this
from
when
we
did
I'm
looking
at
the
wrong
thing.
When
we
did.
You
know
the
demos
from
last
quarter,
but
here's
git
lab
right.
So
it's
several
thousand
text
files.
B
If
I
go
in
the
history
view,
then
I
can
see
the
history
for
my
entire
project
and
I
can
see
that
within
the
last
hour
there
was
literally
about
15
changes
that
were
made,
and
you
know
just
going
back
to
our
earlier
example
where
it's
like.
If
we
did
the
whole
version,
one
version
two
version
three
of
all
these
files,
then
this
would
be
like
it
would
get
super
complicated
right.
B
The
second
thing-
that's
really
really
important
is
that
when
you're
a
developer
a
lot
of
times,
you
are
fixing
some
sort
of
thing.
That
was
implemented
two
years
ago
and
the
person
who
implemented
this
thing
may
not
no
longer
be
with
the
company
right
and
then
so
it's
just
sort
of
like
imagine.
I
made
some
sort
of
website
now,
all
of
a
sudden
we're
running
into
problems
with
it.
B
I
have
to
go
figure
out
what
part
of
the
code
has
to
do
with
this
problem
and
the
person
who
implemented
it
originally
is
no
longer
here.
So
I
can't
ask
this
person
right.
So
one
thing
that
sem
does
is
it
provides
history,
and
so,
let's
just
say
that
I've
identified
where
the
problem
comes
from,
it
comes
from.
You
know
like
this
file,
for
instance,
and
now
what
I
have
to
do
is
I
can
go
in
the
history
view
and
I
can
go
now
look
into
all
right
here,
the
two
versions
of
it.
B
It
changed
this
and
this
and
this
so
there's
only
been.
Let's
just
say
that
there
are
five
changes
here.
This
isn't
the
best
example,
but
I
know
it
worked
in
this
change.
I
know
it
worked
in
this
change.
This
change
happened
and
then
stuff
stopped
working
like
you
know,
shortly
after
that,
so
now
I've
identified
the
problem
probably
comes
from
this
change.
Let
me
look
at
it
and
so
all
right.
This
is
the
change
that
this
engineer
implemented,
and
so
theoretically,
I
can
just
undo
the
changes.
B
Maybe
that'll
fix
it,
but
the
more
important
thing
is
that
scm
gives
you
the
history
log
about
why
this
change
was
made.
So
when
this
developer
was
here,
we
have
documentation
on
why
he
or
she
changed
his
file
and
then,
even
though
he
or
she
is
not
with
the
company
anymore.
I
understand
their
reasoning,
and
this
is
super
super
valuable
for
debugging
software
projects.
B
You
need
this
history
because
otherwise,
there's
absolutely
it'd
just
be
impossible
to
like
maintain
them
at
a
quick
rate,
and
so
this
is
another
thing
that
sem
does
so
yeah,
so
we
looked
at
version
control
for
a
project.
We
looked
at
version
control
for
a
file.
We
looked
at
how
software
developers
debug
projects
using
the
history
for
each
change.
This
is
incredibly
important.
B
There's
basically,
no
way
to
be
a
software
developer
without
this
functionality,
and
this
is
something
that
git
does
and
then
the
other
thing
that
we
talked
about
is
merge
request.
We
are
an
open
source
project.
There
needs
to
be
some
sort
of
gate
for
people
submitting
things,
otherwise
your
competitors
hijack
our
product.
So
what
merge
requests
do?
B
Is
they
provide
an
approval
mechanism
that
protects
our
code
from
getting
hijacked
and
make
sure
that
we're
staying
still
on
track
and
so
get
lab's
merge,
request
process
and
our
approvals
are
the
best
I
used
to
use
github
for
about
like
half
a
decade
that
we
can
with
gitlab.
We
can
say
like
all
right
to
get
this
code
in.
You
need
to
have
two
people
from
the
test
team,
one
person
from
security.
B
B
Gitlab
all
right
can
I
clarify
anything
about
all
this
branching
stuff,
because
I
know
that
this
is
like
a
lot
of
jargon
and
stuff.
Real,
quick.
C
C
So
I
think
we
all
did
it
a
little
bit
and
but
it's
very
interesting
to
see
where
you
see
the
changes
and
everything
my
question
would
be
because
you
just
mentioned
that
the
benefit
of
gitlab
is
that
you
have
this.
C
These
rules
that
certain
parts
of
the
team
have
to
approve
a
code
in
comparison
to
github.
Does
this
have
to
do
with
the
permission
levels
that
we
have?
What
does
this
simply
have
to
do
with
search
code
management?
That
is
just
a
rule.
You
need
to
have
a
tester.
You
need
to
have
a
security.
You
need
to
have
those
people,
otherwise
the
merge
request
is
not
allowed,
or
can
you
personally
say?
Okay,
I
want
one
of
this
team,
one
of
that
team
or
one
overseeing
basic.
C
You
do
your
own
approval
rules,
yeah
and
it's
the
difference
between
github.
You
don't
have
these
approval
rules
per
segment
or
per?
What
are
you
working
in.
B
Yeah,
that's
a
really
great
question,
so
thanks
for
mentioning
it,
the
way
to
think
about
it
is
that
we
have
really
really
really
complicated.
It's
complicated
is
not
the
right
word,
but
we
give
organizations
the
ability
to
customize
permissions.
However
they
want
and
how
we
do.
It
gives
customers
a
lot
more
control
than
any
other
tool
that
I've
ever
seen.
I
use
github
for
about
half
a
decade.
The
amount
of
customization
that
you
can
do
in
gitlab
is
way
higher
than
you
can
do
in
github,
and
so
there's
different
ways
of
doing
this.
B
That
get
lab
supports
one.
Is
that
there's
the
different
permissions
right,
so
there
are
about
seven
different
types
of
users
in
gitlab,
so
you
can
have
like.
Like
an
auditor,
you
can
have
like
a
developer
and
then
you
can
have
like.
B
Yeah
exactly
so
over
here,
guest
reporter
developer,
maintainer
owner
these
people
can
do
different
stuff.
Not
some
of
these
people
can
only
create
issues.
Some
of
them
can
only
see
everything
the
developers
can
are
that
now
you
can
start
submitting,
merge
requests.
Maintainers
are
like
the
maintainer
of
the
environment.
They
can
now
do
like
sysadmin.
They
can
admin
the
server
itself
and
owners
can
do
everything.
They're,
like
your
super
users
right
so
like
your
vp,
is
like
your
owner.
B
So
that's
one
level
of
permissions
that
we
have,
which
is
baked
into
each
user,
that
we
have
at
gitlab
other
things
that
we
do.
So
it's
like
we're.
Taking
a
look
at
the
approvals
that
we
had.
This
is
actually
something
that's
different
and
it's
something
that's
complementary
to
what
we
just
looked
at,
and
so
what
approvers
list
is
you?
B
We
can
customize
it
even
further,
and
so
it's
just
sort
of
like
you
actually
create
some
sort
of
file
that
determines
which
users
are
eligible
for
approving
your
merge
requests,
and
so
you
can
customize
this
file.
However,
you
want,
if
you
wanted
to
have
like
hey
there's,
you
need
four
security
people.
Two
test
people,
three
developers
and
one
director,
because
this
is
really
top
secret,
important
stuff
and
you
can
customize
it
that
way.
If
it's
a
smaller,
faster
moving
project,
then
you
can
customize
it
so
that
you
just
need
two
developer
approvals
right.
B
B
Great
can
can
so
like
one
more
thing
that
I
want
to
talk
about
is
like
a
merge
conflict.
I
know
that
this
is
something
that
we
hear
from
time
to
time.
What
a
merge
conflict
is
is
it's
when
two
people
write
a
merge
request
that
edits
the
same
file
and
now
the
big
problem
is
well.
Like
you
know.
If
I
accept
persons
changes,
then
I
can't
accept
the
other
person's
changes
and
then
so
it's
just
sort
of
like
we
there
just
needs
to
be
some
sort
of
way
of
like
resolving
that
right.
B
So
it's
just
sort
of
like
imagine
I'll.
Just
give
you
a
visual
example.
So
here's
get
lab
code
a
danger
file,
it's
going
to
danger
file
so
like,
let's
just
say
that
I
edit
this
line
and
turn
it
into.
You
know
like
some
text,
whatever
right
and
then
you
know
christina
edits
this
exact
same
line
and
then
edit
changes
it
to
some
other
text.
So
I
say,
like
I
change
this
into
the
literal
like
text,
purple
right
and
then
christina
edits
it,
and
then
she
writes
blue
right.
B
They
both
create
merge
requests
and
both
of
them
are
now
going
to
show
up
in
the
merge
request
view,
and
if
I
merge
my
code
then
now
the
master
branch
is
going
to
reflect.
The
fact
that
I
put
this
in
as
like
blue
and
christina's
merge
request
no
longer
makes
sense
because
it
doesn't
reflect
the
current
version
of
the
code
anymore.
Her
merge
request
is
still
going
to
say
like
this.
Is
this
text
is
the
older
version?
B
I
want
to
change
it
to
green,
but
this
code
actually
changed
since
the
last
time
she
made
her
merge,
request
bottom
line.
I
don't
think
that
it's
super
important
to
understand
like
all
of
the
syntax
about
this,
but
if
people
are
editing
the
same
file,
it
creates
merge,
requests
and
that's
a
that's.
A
problem,
so
get
lab
is
really
good
at
resolving
merge
requests
it's
better
than
github.
B
I'm
gonna
skip
the
exercise
for
now.
Let's
talk
about
differentiators,
we
have
a
huge
differentiator
and
let's
talk
about
it,
so
advanced
self-hosted
functionality
with
high
availability.
That's
a
lot
of
different
terms.
Let's
unpack
what
this
means,
but
I'm
just
going
to
start
with
a
story
right.
Git
live
has
two
deployment
methods
one's
to
sas.
If
you
use
their
sas
offering,
then
it's
google
cloud
fundamentally
right
option.
Number
two:
is
you
can
get
your
own
server
and
install
gitlab
on
it?
So
that's
self-hosted
right.
B
So,
let's
just
say
that
we're
some
sort
of
super
super
super
top
secret,
like
government
branch
and
what
we
work
with
is
you
know
like
social
security
numbers
for
the
united
states
and
we
gotta
go
store
this
data
somewhere
and
it's.
We
know
that
other
countries
are
trying
to
like
hack
all
this
data
and
our
security
team
literally
has
like
tons
and
tons
and
tons
of
security
rules.
Google
cloud
is
not
up
to
us
enough
with
our
security
rules.
They
are
not
secure
enough.
B
So
what
we
do
is
we
have
a
couple
of
data
centers
that
are
underground.
They
are
literally
underground
and
they
are
completely
disconnected
from
the
internet
and
so
like
to
get
into
this
data
center
surrounded
by
barbed
wire
fence.
And
then
you
have
to
get
like
top
secret
security
clearance,
three
different
levels.
Then
you
take
some
elevator
downstairs
and
then
you
have
a
bunch
of
servers
and
then
this
is
like
where
bank
financial
information
is
are
like,
where
social
security
information
is
kept
right,
so
extremely
highly
highly
secure.
B
So
for
a
business
like
that
or
a
government
branch
there,
they
don't
trust
they.
They
would
never
trust
our
sas
and
the
reason
why
is
because
our
sas
fundamentally
is
running
on
google
cloud.
So
if
google
cloud
messes
up,
then
all
their
data
is
lost.
If
git
lab
makes
some
sort
of
vulnerability,
then,
like
all
of
a
sudden,
their
data
is
lost,
so
they
have
to
have
itself
hosted
so
certain.
B
So
just
a
recap:
some
customers
require
self-hosted
as
opposed
to
the
sas
just
because
their
security
rules
are
so
high
and
a
lot
of
times
these
customers
require
this
thing
called
high
availability.
So
it's
high
availability,
so
don't
get
confused
by
this
diagram.
The
whole
idea
with
high
availability
is
I'm
not
going
to
show
this
diagram.
The
whole
idea
with
high
availability
is
like,
let's
just
say
that,
like
on
amazon.com
or
on
netflix
are
on
facebook.
B
I
get
all
of
my
revenue
from
having
my
website
up.
If
my
website's
down,
I
literally
lose
millions
of
dollars
like
a
minute,
there's
no
way
that
my
website
can
go
down.
So
I
have
all
these
data
centers.
I
need
to
go
design
my
environment,
where,
if
some
data
center
sets
on
fire
gets
hit
by
an
earthquake,
literally
no
one's
affected
and
people
can
still
go
to
amazon.com
might
be
a
little
bit
slower,
but
like
what
we've
done
is
we've
made
our
web
service
highly
available?
Well,
how
do
you
do
this?
B
You
do
this
by
making
really
really
big
clusters
of
servers.
So
let
me
show
you
how
this
works.
This
is
a
simplified
diagram,
but
this
is
an
example
of
a
server
cluster
right
and
the
whole
idea
is
that,
because
I
have
two
machines
that
are
running
my
web
service,
if
one
of
them
dies-
or
you
know-
I
have
to
reboot
it
or
like
you
know-
sets
on
fire
or
whatever,
then
all
of
the
work
just
goes
to
the
server
number
two
and
my
website
still
runs
right,
and
so
this
is
how
I
implement
high
availability.
B
The
whole
idea
is
that,
like
I
build
in
a
bunch
of
redundancy
into
my
environment,
if
one
data
center
gets
hit
by
an
earthquake,
I
have
many
other
data
centers.
I
have
now
implemented
a
highly
available
web
service,
and
so
it's
going
to
continue
running
so
all
of
these,
like
top
secret,
like
whatever
bank
financial
institutions
that
require
all
the
security
stuff,
they
require
high
availability,
because
if
some
of
their
server
gets
servers
get
compromised,
then
people
still
need
they
like
be
able
to
pull
money
out
of
their
financial
account.
B
Right
like
if,
like
your
bank,
stopped
like
giving
money
because
of
some
problem,
then
like
people
would
panic
right.
It's
something
that
could
never
happen
all
right,
so
bring
everything
back
together.
Some
customers
are
security,
conscious
they
require
self-hosted
functionality
and
they
require
high
availability.
So
that's
the
ability
to
have
clustered
servers
which
is
going
to
create
like
web
services
that
are
going
to
be
like
really
really
really
reliable.
B
The
whole
idea
is
that,
like,
if
I
experience
some
problem,
it
doesn't
matter
it's
not
going
to
affect
my
business,
and
what
I
want
to
say
about
this
is
that
git
lab
is
by
far
the
best
in
this.
In
this
type
of
customer
scenario,
we
have
80
percent.
The
market.
Github
has
20
percent
the
market.
B
We
are
way
better
than
everyone
else
in
this,
because
we
thought
about
these
things
when
we
designed
the
product
yeah,
so
literally
we're
better
github's
trying
to
catch
up
with
our
roadmap
right
now
on
this
but
like
we
are
substantially
better
and
we
win
the
vast
majority
of
the
deals
that
fall
into
this
category.
So
it's
a
huge
differentiator
that
we
have
what
other
differentiators
do
we
have
honestly
like
a
lot
of
it,
just
has
to
do
with
permissions
right,
so
we
talked
about
how
there's
different
types
of
users
with
gitlab.
B
When
I
was
using
github.
They
didn't
really
have
this
concept
that
may
have
changed.
I
you
know,
because
they're
copying
a
roadmap,
but
like
the
amount
of
like
permission
levels
and
like
you
know
who
can
edit
what
and
stuff
like
that
is
way
better
with
gitlab
than
any
other
product
that
I've
used
and
especially
github.
So
this
is
something
that,
like
it
makes
a
difference,
is
a
huge
differentiator
or
not.
Really
all
right
can
I
clarify
anything
that
I
just
talked
about
right
now.
C
That's
very
interesting
because,
I'm
sorry
it's
the
highest
availability.
I
honestly,
I
never
talk
with
a
customer
about
this.
Maybe
it's
because
in
smb
it's
not
that
big
of
a
deal
but
the
user
permission
levels.
We
talked
about
a
lot.
The
merge
approvals,
the
different
approvals
that
this
customization
is
there.
We
talk
a
lot,
but
it's
very
interesting
to
hear
about
the
high
availability.
C
B
Yeah,
I
think
that
I
really
appreciate
your
smb
perspective,
thanks
for
mentioning
that.
I
think
that
it
matters
way
more
for
enterprise
and
for
federal,
so
I
know
a
bunch
of
like
federal
organizations.
B
You
cannot
have
this
deal
unless
this
functionality
is
in
place
because
our
security
team
is
going
to
reject
your
tool
like
it
is
not
secure
enough
unless,
like
you,
deploy
it
in
this
way,
I
think
that
for
smb,
if
you
have
like
10
20
30
developers,
then
like
you
only
need
really
one
gitlab
server
right
and
then
so
you
don't
care
about
having
a
cluster
your
environment's,
not
large
enough
to
warrant
having
like
five
servers.
B
That
does
this
just
because
and
a
lot
of
times
like
so
I
worked
for
a
startup
about
like
six
years
ago.
We
eventually
got
acquired
and
then
the
whole
idea
is
like.
We
got
an
a
round
of
funding,
it
was
2
million
or
something
so
it's
like
they
want
to
use
the
sas
in
that
instance,
because
it
gives
them
way
more
flexibility
right.
So
it's
like
if
they
deployed
their
own
server
and
then
their
development
team
got
bigger.
B
Then
they
need
to
buy
another
server,
they
need
to
install
gitlab
on
it
and
that
just
takes
a
lot
of
time.
You
don't
want
to
have
hardware,
because
in
a
startup
like
a
lot
of
times,
you
don't
even
know
if
you're
gonna
exist
in
three
years
right,
so
I'd
much
rather
not
sync,
all
my
money
into
capital
transactions
and
spend
like
five
thousand
dollars
in
servers.
I'd
rather
have
it
in
the
cloud
and
just
pay
like
cloud
server
cost
like
in
the
united
states
costs
like
12
cents
per
hour,
14
cents
per
hour.
B
D
I
had
a
question
regarding
high
availability
and
to
my
understanding,
if
they're
using
a
self-hosted
instance
and
they're
managing
their
own
servers,
aren't
they
able
to
do
this
themselves,
meaning
doing
multiple
clusters
on
their
servers
and
if
so,
what
other
value
gitlab
adds
in
this
in
this
scheme,.
B
Yeah,
that's
that's
a
really
great
question,
I'm
happy
to
chime
in
here
for
that,
so
there's
no
additional
cost
for
deploying
git
lab
with
in
a
clustered
fashion
versus
so
we're
talking
about
sophosted
now
you're
paying
for
the
subscription
and
the
subscription
does
not
care
how
many
servers
you
deploy
it
on.
B
So
so
I
think
I'm
answering,
I'm
sorry
was
the
second
part
of
your
question
again.
I
just
want
to
make
sure
I'm
actually
answering
it.
D
B
Yeah,
so
the
value
of
having
high
availability
for
gitlab
is
that
it's
just
safer
for
your
environment.
If
this
server
stops
working,
then
this
server
like
continues
to
work
and
just
to
put
this
into
perspective
when
I
was
a
developer
for
a
startup
every
once
in
a
while.
Your
tools
that
are
imagine
if,
like
salesforce,
went
down
right.
How
much
would
that
affect
your
productivity?
B
It's
the
same
idea
with
gitlab,
so
it's
just
sort
of
like
every
single
tool.
I've
ever
used,
github
gitlab
salesforce.
They
go
down
from
time
to
time,
and
if
that
affects
the
productivity
of
your
team,
then
what's
the
value?
What's
the
loss
in
terms
of
value
to
your
business
right,
so
you're,
paying
all
these
people
like
30
euros
like
an
hour
or
something
like
that
and
then
if
their
productivity
is
affected,
that
affects
your
business.
B
So
the
reason
why
people
want
to
have
clusters
of
gitlab
servers
is
so
that
they
can
just
have
gitlab
up
and
running
in
a
more
resilient
manner
and
the
whole
idea
is
that,
like
if
part
of
my
environment
is
affected,
I
get
hit
by
earthquake
or
something
well.
You
know,
like
obviously,
people
need
to
take
care
of
their
families
and
it's
still
going
to
be
affected,
but,
like
you
know
like
we're,
not
going
to
have
problem
with
our
tools,
gitlab's
going
to
be
up
and
running
because
we
deployed
it
in
a
clustered
fashion.
D
So
what
you?
What
you're
saying,
is
that
the
functionality
of
gitlab
of
high
availability
is
just
giving
them
the
ability
to
have
a
second
server.
They
can
run
gitlab
onto
which
they
wouldn't
have
if
they
had,
for
example,
bronze,
starter
plan
or
because
high
availability
is
in
the
premium.
One
right.
B
If
against
our
competitors,
they
they're
the
level
of
so
github
now
has
clustering,
but
their
clustering
is
not
nearly
as
good
as
ours,
and
if
you
want
true
clustering
right
now,
you
pretty
much
need
gitlab
for
sem.
B
So
it's
literally
almost
like
a
checkbox
thing.
I
am
a
customer
that
requires
this.
Can
your
product
do
x,
y
z,
said
gitlab,
says,
check,
check,
check,
github
says
check
check.
Well,
I
I
require
set
too.
So
it's
like
we're
going
to
go
with
git
lab
a
lot
of
the
deals,
especially
in
enterprise
and
federal
space.
They
work
like
that.
D
B
All
right,
so,
let's
talk
about
project
management,
so
we
just
talked
about
all
the
crate
functionality.
Let's
talk
about
the
plan
functionality.
That's
part
two.
So,
let's
start
with
the
story
right,
so
we
got
five
people
in
this
meeting.
We
are
now
wedding
planners
and
we
got
300
people.
That's
coming
this
wedding
right,
so
we
got
to
divide
up
all
this
work.
We
need
to
come
up
with
lists
of
things
to
do.
B
B
We
gotta
somehow
get
progress
on
each
item
and
communicate
them
to
everyone
else,
because,
ultimately
we
have
stakeholders
right
so
with
you
know
so,
bride
and
groom.
They
hired
us
to
make
stuff
work
for
them.
They
need
to
know
progress
on
how
this
stuff's
coming
along
right
and
the
last
thing
that
they
need
to
know
is
which
items
need
to
be
done
in
a
certain
order.
If
we
just
came
up
with
a
simple
like
to-do
list-
and
we
just
started
like
all
right-
let's
do
the
first
one.
First,
let's
do
task
number
two.
B
B
The
invitations
need
to
be
sent
out
first
right,
so
you
need
to
figure
out
like
what
sort
of
sequencing
all
this
stuff
works,
and
so
project
management
tools
take
care
of
all
this
they're
very
popular
jira
has
over
50
the
project
management
market,
so,
like
literally
in
software
development
jira
has
over
50
percent
of
the
market.
They're
really
really
big
and
project
management
tools
are
pervasive
in
software
development.
You
basically
can't
just
like
you
can't
do
your
job
without
sem.
You
really
can't
do
your
job
without
project
management
tool
too.
B
So
this
is
something
I
like
to
say.
Is
that
like
there's
not
to
get
too
abstract,
but
there's
better
goals
that
you
can
have
right?
So
it's
just
sort
of
like
this
has
to
do
with
organizational
leadership
theory,
but
not
to
get
too
abstract.
But
it's
like
if
you're
leading
a
team,
then
a
bad
thing
to
say
to
one
of
your
team
members
is
you
need
to
get
better
and
they're
going
to
look
at
you
and
they're
going
to
be
like?
Well
thanks.
B
You
know
like
all
right
who
like
how
do
I
do
that
right,
but
a
much
better
goal
is
say
like
hey.
I've
noticed
that
the
amount
of
you
know
like
that,
like
you're,
doing
everything
that
your
results
are
a
little
bit
lower,
you're
doing
everything
by
email.
Would
you,
but
you
know
some
of
our
other
team
members
are
using
a
lot
of
linkedin
and
having
a
lot
of
success
with
it.
B
So
my
goal
for
you
for
this
week
is
to
go,
send
out,
is
to
go
talk
to
mike
lebeau
and
goal
number
two
and
talk
to
him
about
like
how
to
use
like
you
know,
better
outreach,
stuff
and
goal
number
two
is
I
want
you
to
send
out,
like
you
know,
activate
like
three
of
these
sequences
for
the
week
or
something
like
that
right.
So
that's
a
better
goal.
Why?
B
Because
it
actually
tells
me
something
that
I
can
do
as
opposed
to
something
nebulous
like
get
better,
that's
just
sort
of
like
I
don't
even
know
what
to
do
with
that
right.
So,
what's
a
what's
a
good
goal,
good
goals
are
specific,
so,
as
opposed
to
like
get
better,
it's
like
go
activate
x,
number
of
outreach
sequences.
B
They
are
measurable
right.
So,
as
opposed
to
like
I
want
to
get
better
in
shape.
You
say
like
I
want
to
go
decrease
my
resting
heart
rate
by
10
by
the
next
two
months
through
working
out
right.
They
have
to
be
attainable.
If
you
tell
someone
a
goal
which
is
like
hey,
I
want
to
like
go
run
a
marathon
in
like
a
two
weeks,
then
that's
not
that's
not
achievable
right.
It's
got
to
be
like
incremental
progress.
It's
the
whole
idea
of
iteration
that
we
have
here
and
then
relevant.
Obviously
that
makes
sense
time
bound.
B
You
have
to
have
time
limits
to
all
of
your
goals,
otherwise
nothing
gets
done.
So
we
can
part
of
the
reason
why
get
lab
project
management
stuff
is
really
good
and
project.
Any
sort
of
good
project
management
tool
in
general
is
going
to
be
good
if
they
help
you
to
implement
these
smart
goals.
That's
the
secret
to
project
management
tools.
If
they
do
all
of
them,
that's
great.
If
they
do
some
of
them,
then
they're
not
going
to
be
as
good
and
ultimately
what
do
you
get
out
of
this
and
a
good
project
management
tool?
B
You
get
better
collaboration
across
your
organization
that
may
help
out
your
organization.
20
30
right
in
terms
of
let's
just
say
that
a
business
is
pouring
like
20
million
dollars
into
their
engineering.
Well,
if
you
can
get
20
to
30
more
out
of
them,
then
what's
the
cash
value
for
that
right.
Other
things
about
project
management.
They
provide
history,
I'm
going
to
show
you
how
that
works.
They
provide
accountability.
It's
also
really
important
for
organizations.
B
They
give
management
a
sense
of
progress.
I
want
to
talk
about
a
story
about
that
and
they
helped
optimally
sequence
work.
So
when
we're
talking
about
project
management
in
gitlab,
we're
talking
about
issues,
issues
are
grouped
together
in
milestones.
Epics.
We
had
to
do
that
for
last
quarter,
but
let's
actually
take
a
look
at
what
this.
What
these
things
are
right,
so
I'm
going
to
talk
about
what
gitlab
does
in
terms
of
all
these
things
and
why
we're
better
than
other
people.
So
here's
an
issue.
B
Actually
this
is
the
issues
tab,
let's
go
into
here
right.
So
here
here's
an
issue-
and
this
is
a
unit
of
work
right,
so
it
could
be
create
some
new
chart
create
some
new
shopping,
cart
function
and
my
product.
My
website
update
my
website,
something
it's
a
it's
a
unit
of
work
right
as
a
developer.
I
get
paid
for
solving
issues
if
I
get
solve
30
issues
and
everyone
else
is
solving
10.
I
get
promotion
right.
So
that's
fundamentally
like
what
I
do
just
like.
We
get
iqm's,
they
solve
issues.
B
So
this
is
I'm
gonna
talk
about
how
we
provide
collaboration.
When
I
was
using
github,
then
this
is
the
idea
of
silos
right
so
with
github.
B
Generally
speaking,
only
the
developers
use
it
and
because
of
that,
after
someone
creates
an
issue,
then
people
start
collaborating
on
the
best
way
to
do
it.
So
someone
could
say,
like
hey,
I
did
this
a
year
ago.
I
did
it
this
way.
It
worked
out
pretty
well
for
me
boom
by
him,
saying
that
it
saved
me
50
of
my
time.
What's
the
value
of
that
to
my
organization,
so
the
collaboration
aspect
for
issues
is
very
important.
B
Other
things
is
that,
like
they
could
say
like
hey,
if
you
you
know,
someone
could
say
like
don't
do
it
this
way,
because
if
you
do
it
this
way,
then
it's
gonna
have
this
problem
with
their
product.
I
found
this
out
the
hard
way
you
know
like
a
month
ago.
I
didn't
know
that,
but
now
that
he
chimed
that
in
he
saved
me
like
two
weeks
of
going
down
the
wrong
path
right,
so
the
collaboration's
really
important.
B
So
if
you
are
using
some
sort
of
tool
that
only
the
developers
are
using
are
only
the
test
teams
using
or
all
the
security
people
are
using
you're
going
to
have
the
benefit
of
the
collaboration
of
that
team.
The
value
of
gitlab
is
that
all
the
teams
use
it,
which
means
that
your
collaboration
is
better
I'll.
Give
you
an
example.
B
So
when
I
was
a
test
engineer
for
about
half
a
decade
and
the
big
problem
with,
I
wouldn't
say
a
big
problem,
but
like
people
changed
things
that
would
negatively
impact
our
test
stuff
all
the
time.
So
someone
would
solve
this
issue
in
some
way.
That
would
give
me
two
additional
weeks
worth
of
work
happened
all
the
time
and
a
lot
of
times.
I
did.
B
I
couldn't
see
these
changes
coming
in
because,
like
I
didn't,
have
visibility
because
we
were
using
different
tools,
but
if
we
had
git
lab,
then
the
person
could
say
like
hey,
I'm
thinking
about
doing
it.
This
way
and
then
me
as
a
test
person
and
say
just
letting
you
know,
if
you
do
it
this
way,
then
it's
going
to
break
our
test
infrastructure,
because
our
test
infrastructure
is
not
designed
to
go
like
you
know,
test
things.
If
you
set
up
our
api
this
way
right
and
then
a
manager
can
say
hey
all
right.
B
We
don't
have
enough
time
to
like
push
our
road
back
out
two
weeks.
Let's
just
go
with
another
way
right
and
then
all
of
a
sudden.
Our
organization
has
now
saved
two
weeks
of
time
because
we
have
better
cross-team
collaboration.
Cross-Team
collaboration
is
very,
very
key
for
engineering
organization
success.
If
an
engineering
organization
has
crossteam
collaboration,
they
will
be
maybe
like
40
better
than
their
someone
who
has,
like
average,
crossteam
collaboration
so
yeah.
We
provide
public
collaboration.
B
Another
thing,
that's
really
important
is
just
like
how
we
saw
all
the
changes
come
in
for
the
code,
and
so
it's
that
story
of,
like
hey,
I'm
fixing
this
problem,
the
person
who
last
wrote
who
wrote
this
wrote
it
two
years
ago
and
he's
no
longer
with
the
company.
B
So
I
can't
ask
him
about
their
code
right,
but
if
I
were
to
look
at
all
of
the
these
issues
and
the
collaboration
here,
I
can
find
out
the
issue
that
corresponds
with
what
that
person
was
doing,
and
then
I
could
read
this
person's
reasoning
right
and
then
so
now,
as
the
person
who's
trying
to
fix
this
thing,
that
was
introduced.
Two
years
later,
I
have
more
of
an
understanding
on
how
to
fix
it.
This
is
really
really
really
important.
B
Yeah,
I'm
trying
to
think
about
like
a
good
analogy
for
this,
but
yeah.
So
all
of
this,
like
history,
someone
can
take
a
look.
Go
in
all
this
issues.
Log
right
all
these
issues
over
here
were
in
literally
like
you
know.
B
All
right
provide
accountability
and
gift
management
track
of
progress.
How
we
do
this
with
issues
is
that
we
give
people
we
give
metrics
right,
and
so
the
way
to
think
about
this
is
that
engineers
try
to
protect
themselves
a
lot
by
sandbagging,
and
so
the
whole
idea
is,
if
I'm
a
developer.
I
think
that
it's
going
to
take
me
two
weeks.
My
manager
asked
me
how
long
it's
going
to
take.
I
say
three
weeks
and
the
problem
with
that
is
that
the
manager
then
sends
bags
right.
So
the
director
asks
him.
B
How
long
is
all
this
stuff
going
to
take?
He
thinks
it
can
be
two
months
and
then
he
says
three
months
and
the
big
problem
is
your
developer.
Sandbag,
your
manager
sans
bags,
your
director
sends
bags
your
senior
director
sands
bags.
Your
vp
stands
back,
everyone
sandbags
40,
then,
all
of
a
sudden,
your
schedule
is
now
inflated
150.
B
So
what's
the
cash
value
loss
of
that
your
organization?
What's
large
right
and
that's
the
problem
with
relying
on
word
of
mouth,
if
you
have
no
metrics
driven
way
of
figuring
out
how
much
time
is
left
in
your
project,
you
have
to
rely
on
word
of
mouth
and
then
all
of
a
sudden,
your
schedule
inflates
because
everyone
tries
to
sandbag
and
the
problem
with
that
is
that
there's
a
universal
rule
and
work
that
work
expands
to
the
amount
of
time
that
you
give
it
right.
B
So,
if
I
give
someone
two
months
to
do
something,
they're
gonna
find
some
way
to
spend
all
that
time
and
a
lot
of
times.
People
aren't
gonna,
be
honest
and
say
they're
bored
right.
So
how
do
we
do
this?
One?
We
have
burn
down
charts
this
burn
down.
Chart
shows
from
a
metric
driven
perspective,
the
velocity
in
which
all
of
our
issues
are
getting
closed.
So,
let's
just
say
my
big
project.
This
big
project
has
683
issues
right
director
can
come
in
and
say
hey
at
the
rate
that
you're
going.
B
I
think
that
you're
going
to
be
done
in
around
august,
so
I'm
going
to
give
you
two
additional
weeks.
Does
that
sound
good
to
you,
so
manager,
then
says
you
know,
could
could
push
back,
could
explain
some
additional
context.
Hey.
I
have
some
people
going
on
vacation
whatever,
but
they
no
longer
have
the
ability
to
say.
Oh,
I
need
50
extra
time
in
sandbag
right.
They
somewhat
do,
but
it's
a
lot
harder
if
there's
metrics,
so
the
burn
down
charts
are
really
important.
B
The
other
thing
that's
really
important
is
built
into
the
issues
we
have
time
tracking.
So
it's
like
I'm
working
on
this
issue.
I
spent
my
entire
day
on
it.
I'm
going
to
submit
eight
hours
because
that's
a
u.s
workday
into
this
issue,
and
then
this
issue
is
going
to
keep
track
of
how
much
time
I've
spent
into
it,
and
so
this
is
really
important
from
a
manager.
Pers
excuse
me
perspective
because,
like
if
I
find
out
hey,
there's
this
one
issue,
it's
really
really
important.
B
If
this
slips,
then
we're
going
to
be
late
for
a
project
we
need
to
have.
We
need
to
get
progress
on
this
and
if
the
developer
is
not
spending
any
time
on
this
because
they
want
to
go,
do
other
stuff,
which
happens
all
the
time,
then
you
now
have
an
accountability
mechanism
or
in
your
next
one
of
one
you
can
say
hey.
I
looked
in
gitlab
and
I
looked
at
this
issue.
That's
really
important.
I
really
communicated
you
that
is
really
important.
B
Have
you
spent
any
time
on
it,
because
the
issue
doesn't
say
that
you
put
any
time
into
it
right
so
now
you
have
a
metric
different
way
of
finding
out
who's
been
working
on
what
the
other
thing
that
you
can
find
out
with
time
tracking
is
like,
let's
say,
developers
put
a
hundred
percent
of
their
time
into
it
and
they're
that
usually
means
that
they're
stuck
in
some
way.
They
don't
know
how
to
do
it
and
your
manager
can
now
come
in
and
provide
organizational
leadership
and
say:
hey.
Are
you
stuck
on
this?
B
That's
totally
cool!
If
you
are
I'm
understanding,
I've
been
there
before
too,
but
you
know
we
have
organizational
challenges
here.
We
do
have
a
timeline.
So
what
do
you
think?
If
I
paired,
you
with,
you,
know,
developer
rachel
with
this
one
and
that's
how
he
can
provide
assistance
for
developers
who
can't
figure
out
how
to
implement
something
so
time
tracking
is
really
important.
Due
dates
are
also
really
important.
B
It's
just
sort
of
like
discrete
ways
of
making
things
time
specific
and
smart
goals.
Your
goals
have
to
be
time,
specific
right,
all
right,
so
optimally
sequence
work,
that's
roadmaps
over
here
you
can
see
our
gitlab
roadmap,
and
so
what's
this
actually
show
this
shows
all
the
individual
projects
that
you
have.
So
your
vp
can
look
into
here,
see
all
the
projects
that
their
managers
are
working
on.
This
manager
project
starts.
The
project
starts
here
ends
here.
B
This
project
starts
here,
ends
here
right
and
now
the
problem
is
that,
like,
if
you're
a
vp,
you
know
that
all
not
all
projects
are
created
equally
right,
so
there's
some
projects
that
are
extremely
extremely
important.
If
this
project's
not
done-
and
it's
not
done
well-
and
it's
not
done
the
beginning-
then
there's
all
these
other
projects
that
can't
be
done
because
they
depend
on
the
output
of
the
first
project
right.
So
in
a
situation
like
that,
I
got
to
put
this
project
first.
B
Another
thing:
that's
really
important
is
like,
let's
just
say
that
there's
only
two
people
in
the
organization
that
know
kubernetes
right,
and
so
I
know
that
they
already
said
they're
going
to
be
on
vacation
in
this
month.
Therefore,
I
got
to
go
plan
that
they
start
this
stuff
here
before
they
go
on
vacation
or
something
like
that
right,
and
so
your
roadmap
can
help
you
to
sequence
work
in
a
way
that
makes
the
most
sense
for
your
organization,
your
project
managers-
all
they
do.
B
Is
they
log
in
the
road
map,
see
how
stuff's
going
along
and
see
if,
like
these
like
lines,
are
like
make
the
most
sense?
Another
thing,
that's
really
important
is,
as
you
can
see,
with
our
specific
deadlines
like
we
got
a
lot
of
stuff,
that's
running
right
now,
right
and
so
now
you
got
to
think
about.
Like
all
right.
I
only
got
a
finite
number
of
developer
heads.
Does
it
make
sense
that
all
of
our
projects
are
running
in
the
beginning?
Maybe
we
should
spread
things
out.
B
More
good
engineering
team
is
gonna,
have
their
work
front
loaded
so
that
you
can
build
yourself
cushion
at
the
end
because
usually
stuff's
late
right,
but
you
can't
put
all
of
your
work
in
the
beginning,
because
otherwise
your
developers
are
going
to
be
really
stressed
out
right.
B
Your
roadmaps
tell
you
that
so
teach
you
how
to
optimally
sequence
work
the
difference
between
doing
this
and
not
doing
it
is
basically,
if
you
don't
do
this
well,
your
organization
is
not
going
to
run
project
manager.
All
they
do
is
come
in.
Look
at
the
road
maps
see
how
stuff's
coming
along
see
if
things
are
being
done
in
the
right
order,
and
that's
basically
just
completely
necessary
for
like
for
engineering
teams
to
like
you
know,
do
their
jobs.
B
So
we
talked
about
the
developer
workflow
great.
We
got
to
talk
about
kanban
charts.
Do
any
of
you
all
use
kanban
for
your
own
stuff.
B
B
I
use
trello
for
ken
bam
too
yeah,
so
you
know
what
I
don't
want
you
to
dive
into
your
personal
life.
B
I'll
just
show
you,
the
one
that
I
have
set
up,
but
what's
a
kambam
chart
cam
bam
chart
is
the
idea
that
it's
just
one
way
of
doing
project
management
there's
other
ways
in
which
you
can
do
it,
but
the
whole
idea
is
think
about
like
a
conveyor
belt,
so
kanban
actually
comes
from
japan
and
it
was
actually
how
they
did
stuff
in
factories
and
the
whole
idea
is
there's
this
big
conveyor
belt.
In
the
first
section
they
do
something
second
section
they
build
off
of
what
was
done.
B
B
What
they
do
for
the
kanban
chart
is
you
have
a
bunch
of
different
columns
right
and
then
so
for
our
wedding
analogy,
let's
just
say
that
we
got
to
make
we're
using
trello
for
campbell
charts.
So,
like
we
figure
out
all
the
work,
that's
involved,
we
create
issues
for
all
this
work.
Now
we
have
300
different
different
issues
and
if
we
were
to
set
this
up
with
a
can
damn
chart
how
it
works
is
that
there's
different
columns
right
and
so
the
columns
correspond
to
the
different
stages
in
your
conveyor
belt.
B
The
first
stage
is
nothing
started.
Yet.
Second
stage
is
like
we're.
Planning
third
stage
is
that
we're
actively
building
a
thing,
four
stages
that
we
think
it's
done
in
each
checking
and
then
fifth
stage
is
we're
very
confident
that
it's
done
and
so
like
how?
If
we
were
to
implement
our
wedding
project
with
a
kanban
chart,
then
how
it
would
be
like
is
like
all
right,
someone's
I'm
responsible
for
picking
out
the
flowers.
I
go
talk
to
the
bride
and
groom,
see
I've.
Looked
up
these
research,
I
researched
these
vendors.
B
I
found
out
their
budget.
I
found
out
what
they
wanted.
I
think
that
these
are
good
fits
in
progress.
You
know,
like
you
know,
I'm
not
talking
to
the
vendor,
I'm
trying
to
negotiate
rate
and
then
you
know
needs
check.
B
When
everything's
in
a
done
column,
then
we're
done
with
our
project
and
that's
how
kanban
works
trello
you
can
do
kanbam
too
trello
is
owned
by
atlassian.
Now
they
bought
them.
But
the
whole
idea
is
that
if
you
go
to
an
issue
board,
you
can
create
the
same
thing
right.
So
open
issues
is
like
all
of
the
stuff
that
you,
this
isn't
actually
like
a
kanban
chart.
But
if
you
want
to
set
this
up,
open
issues
is
not
started.
C
I'm
just
a
question
about
the
issue
boards.
Is
there
still
a
debate
about
if
we
could
create
our
own
issue
boards
for
personal
needs
as
just
scheduling
what
we
want
to
do,
because
we
tried
this.
I
think
when
I
started
in
october
and
then
it
was
said,
we
cannot
do
this
because
of
reason,
a
and
reason
b.
That's
why
I
think
many
of
us
don't
use
issue
boards
in
gitlab.
B
Yeah
you
can,
if
you're
going
to
try
to
create
like
an
issue
board
under
like
the
gitlab
project,
then
there's
going
to
be
like
rules
that
are
associated
with
that.
But
if
you
want
to
create
your
own
like
project
and
then
create
its
own
issue
board,
you
can
do
that
so
over.
Here
I
have
like
this
sandbox
environment
for
and
then
I've
had
like
sdr's
in
our
organization
like
add
stuff
to
it,
so
that
they
can
work
with
git
lab
and
you
can
create
like
your
own
issue
boards
over
here
right.
So
it's
like.
B
I
have
all
these
fake
issues
that
don't
actually
mean
anything,
but
you
can
do
that
with
your
own
public
project.
Now
I
didn't
need
to
ask
anyone
to
do
this
cool
thanks
for
sure,
thanks
for
asking
all
right,
so
I'm
also
under
fort
maps.
It
sounds
good
competitors
got
to
talk
about
competitors,
so
first
chart
that
I
showed
best
40
project
management
tools.
Don't
want
to
be
one
of
40.
B
B
Jira
is
very
heavy.
So
what
that
means
is
that
it
takes
a
lot
of
time
to
install
it.
Updating
it
takes
a
long
time.
It
is
good
at
what
it
does,
but
it's
a
very,
very,
very
heavy
solution.
So
like
it's
not
like,
I
just
give
you
like
a
meal
analogy
right.
So
there's
some
restaurants,
you
come
in.
You
pay
your
money,
you
have
your
food
in
two
minutes
and
then
you
can
eat
and
then
you're
out
in
like
30
minutes,
jira
is
like
you
come
you
wait
for
a
table.
B
You
for
20
minutes.
You
finally
get
a
waiter.
You
get
your
table,
you
it's
like
fine,
dining
right!
So
it's
like
your
appetizers
come
then
your
wine
comes,
then
your
entrees
come
and
then
it's
just
like
it's
a
two-hour
event.
So
it's
like,
but
jiro
is
good.
It's
just
that
it
takes
a
really
long
time
and
companies
have
to
pay
money
to
have
juror
administrators
because
it's
so
complicated.
So
a
little
bit
about
history.
We
try
to
compete
with
jira
first,
you
know
the
whole
idea
of
like
hey.
B
We
can
replace
your
entire
tool
chain
and
then
people
realize,
like
oh
wait.
People
don't
want
to
like
get
off
of
their
jira.
Why
is
that?
Well?
The
problem
is
that,
like
we
saw
the
value
of
having
all
of
this
log
of
issues
in
your
organization
right.
So
if
I'm
trying
to
fix
something
that
happened
two
years
ago,
I
can
go.
Look
at
the
issue.
I
can
go
see
what
the
developers
were
thinking
and
the
collaboration
that
happened.
This
ultimately
saves
me
time
and
organization
makes
an
organization
more
efficient.
B
So
it's
something
that's
very
powerful
for
an
organization.
The
problem
is
that
if
I've
been
using
jira
for
the
last
four
years,
all
of
my
data
and
history
is
on
jira.
So
it's
really
difficult
to
convince
me
to
go
migrate
from
jira
to
all
of
a
sudden
in
gitlab
to
do
project
management,
considering
the
fact
that
they
have
over
50
percent
of
market
share.
All
of
these
c
levels
they're
talking
their
colleagues,
all
their
other
companies
are
using
jira.
So
it's
like
it's
it's
hard
right.
B
I
I've
used
jira
before
I
both
use
github
before
I've
also
used
gitlab
before
I.
I
think
that
our
stuff
is
the
best
I'm
gonna.
You
know
not
skirt
around
that,
because
I
think
that
jira
is
too
heavy
and
I
think
the
developers
they
appreciate
something
that
is
quicker
and
more
intuitive
to
use.
I
think
that
jiro
is
really
complicated,
but
that
being
said,
they
are
the
incumbent
and
when
your
business
and
all
of
your
all
of
these
c-levels
friends
that
are
presidents
of
other
companies,
they
use
jira.
B
It's
a
hard
sell
to
get
them
to
migrate
from
one
project
management
tool
to
another,
especially
considering
they
have
five
years
of
data
on
jira
right.
So
that's
just
a
hard
thing
to
migrate.
Off
of
so
we
move
from
a
replace
motion
to
an
integration
motion
where
gitlab
can
work
great
with
your.
It
has
first
class
integrations
if
you
want
silver,
you
get
this.
If
you
want
you
know
premium,
then
you
get
this
so
on
and
so
forth,
so
yeah
all
right,
just
bringing
everything
home.
B
I
know
that
we
talked
about
a
lot
of
stuff
and
I
just
want
to
go
back
to
this
slide.
Real
quick,
so
just
imagine
like
this
vendor
over
here
right.
So
all
of
these
different
project
management
tools
over
here
you
have
lists
of
40
best
project
management
tools
and
we
do
have
good
differentiators
in
them.
I
personally,
if
I
were
a
c
level,
I
were
looking
at
a
project
management
tool.
B
I
would
highly
consider
git
lab
for
it,
but
the
ultimate
reason
why
I
would
buy
gitlab
is
not
because
it
has
x,
y
and
z
feature
over
our
competitors.
The
reason
why
I
would
buy
gitlab
is
because
it's
one
tool
for
the
entire
software
development
process,
which
saves
me
time:
money,
integration,
maintenance,
license
costs
and
it's
seamless,
so
integrated
scm,
ci
security,
all
this
other
stuff
and
the
value
that
that
brings
my
organization.
So
that's
what
I
try
to
talk
about
a
lot
and
so
yeah
gitlab
is
one
shared
table.
B
B
Our
developers
use
github
our
test.
People
use
something
else
and
when
you
have
everyone
in
the
same
platform,
you
have
one
shared
table,
which
means
that
you
have
better
cross-organizational
collaboration,
which
makes
us
more
efficient
in
the
long
run
so
yeah
great.
Can
I
help
clean
it?
Can
I
help
clarify
anything
or,
if
not,
then,
let's
just
talk
about
homework
and
I'll.
Give
you
10
minutes
your
time
back.
C
I
just
have
one
question
about
the
jira
integration,
because
you
mentioned
this
data
that
you
might
have
for
five
years
and
it's
very
hard
to
convince
people
to
change
this
if
you
integrate
jira
within
gitlab,
and
it
works
now
simultaneously
with
your
new
issues
and
everything.
How
long
is
like?
Would
it
take
to
migrate
everything
that
the
old
data
to
gitlab
on
average,
depending
on
your
volume
and
everything.
B
Yeah,
that's
a
great
question,
so
there's
different
approaches
that
you
can
take.
One
approach
that
you
can
take
is
here's
git
lab.
You
want
to
use
gitlab
for
sem
and
ci
and
all
this
other
stuff,
and
you
want
to
keep
your
jira
well.
One
thing
that
you
can
do
is
as
opposed
to
creating
git
lab
issues.
B
B
I
want
to
go
pull
all
of
this
jira
stuff
into
git
lab.
The
data
is
now
living
in
git
lab.
All
of
that
history
that
we
talked
about
is
in
gitlab
and
I'm
going
to
turn
my
jira
off,
because
now
the
data
lives
in
two
different
places.
It
lives
in
jira
and
get
lab
right.
So
if
I
take
that
approach,
then
I
only
need
one
tool.
I
don't
know
how
long
that
migration
process
takes
I
as
homework.
I'm
gonna
go.
Look
up
the
answer
to
that
and
I'll
get
back
to
you
on
that.
A
B
Okay,
so
I
think
that
everyone
here
has
had
a
class
so
far.
We
know
how
this
goes.
I
have
like
a
quick
homework
for
y'all.
It's
please
only
spend
20-30
minutes
on
it,
but
it
basically
just
has
to
do
with,
like
you
know,
the
stuff
that
we
talked
about
today.
So
what
do
y'all
think
about
getting
this
in
by
this
friday.
C
B
Yeah,
that
sounds
great
thanks
in
general.
My
philosophy
with
it
is
hey.
If
you're
on
pto,
like
I
totally
understand
that
it
doesn't
matter
it's
just
that.
I
found
that
if
people
don't
do
it,
they
forget
about
it,
so
need
some
sort
of
date
in
mind.
It's
time
specific
goal
right:
okay,
cool,
well,
yeah,
thanks
for
attending
this
session
today,
and
if
I
can
help
out
in
any
way,
let
me
know.