►
Description
Speaker: Melissa Ushakov
In this session, we'll walk through recent product release highlights and the themes for the next year of innovation at GitLab. We'll then do a deep dive on GitLab Plan roadmap and how planning with the DevOps Platform will lead to more collaboration and a better experience!
Get in touch with Sales: http://bit.ly/2IygR7z
A
Our
first
stock
of
the
day
for
get
lab
commit
at
kubecon
comes
from
melissa.
Ushikov
melissa
is
a
group
manager
of
product
management
for
gitlab's
plan
and
ecosystem
groups
prior
to
gitlab.
She
served
as
a
senior
product
manager
at
agile
craft,
which
was
acquired
by
atlassian
and
led
teams,
building
software
to
help
organizations
plan
and
execute
work.
B
B
B
B
B
I
want
to
start
by
highlighting
our
amazing
community
over
the
first
eight
months
of
this
year.
You've
contributed
two
thousand
two
200
improvements:
that's
464
more
than
the
same
amount
of
time
last
year
and
actually
april
of
this
year
shattered
the
record
for
most
contributions
in
a
single
month
so
great
job.
B
Each
month
we
announced
an
mvp
that
has
contributed
in
an
outstanding
way
to
help
make
it
lot
better
for
everyone,
and
I'm
going
to
highlight
the
last
six
mvps
five
still
made
numerous
improvements
to
gitlab
pages
over
the
last
four
months:
cornelius
added
the
original
gitpod
integration
and
expanded
it
by
adding
an
option
to
open
code
changes
in
gitpod
from
a
merge
request.
If
you
haven't
tried
out
gitpod,
I
encourage
you
to
do
it.
It's
great
andrew
helped,
improve
the
usability
of
epic
and
issue
boards
by
adding
more
data
to
them
and
even
sorting
options.
B
B
B
B
B
This
feature
is
a
part
of
our
effort
to
natively
support
thoroughform
metrics
in
git
lab
now.
Remember
how
I
said
I
work
on
the
plan
stage.
I'm
biased,
but
I
think
epic
boards
are
game,
changers
for
visualizing
and
tracking
higher
level
planning
and
we're
going
to
talk
a
lot
more
about
that
later
on.
B
This
next
one,
I'm
really
excited
about
as
well.
I'm
not
a
markdown
expert
so
for
me
being
able
to
see
a
live
preview
of
my
markdown
while
I'm
editing
is
huge
project
level.
Das
and
secret
detection
execution
policies
allow
security
teams
to
be
able
to
manage
scan
requirements
and
not
developers,
so
they
can't
change
them,
and
this
has
been
something
that's
been
long
requested
from
our
security-minded
organizations.
B
B
B
B
The
plan
stage
aspires
to
build
robust
planning
capabilities
that
tie
directly
into
the
devops
lifecycle.
Our
goal
is
to
empower
teams
to
continuously
deliver
customer
and
business
value
with
the
shortest
possible
cycle
times
in
our
roadmap.
We
are
leaning
into
the
adoption
through
usability
theme
and
we're
making
really
significant
improvements
to
our
existing
functionality.
B
B
This
space
is
really
exciting
for
me
and
I'm
going
to
take
a
small
walk
down
memory.
Lane
y'all
can
come
with
me
to
explain
why
I'm
so
passionate
about
this
before
I
was
a
product
manager.
I
was
a
program
manager
in
a
really
large
organization
and
a
big
part
of
my
job
was
making
sure
that
our
leaders
had
status
information
about
our
key
projects.
B
This
resulted
in
me
spending
a
lot
of
time,
parsing
through
different
planning
tools
and
tapping
people
on
the
shoulders.
Just
to
get
the
details
that
I
needed
to
make
status
reports,
I
personally
really
hated
interrupting
people's
work,
just
to
get
a
status
update
and
the
worst
part
was
that
the
minute
the
inca
dried
on
those
reports.
They
were
out
of
date,
and
this
is
because,
when
you're
coordinating
activities
across
the
company
with
hundreds
of
people,
things
happen
every
day.
B
B
Building
and
maintaining
software
at
scale
requires
cross-functional
collaboration.
A
lot
of
organizations
use
point
solutions
integrated
into
a
do-it-yourself
tool
chains
as
organizations
grow
and
progress
in
their
agile
transformation
journeys.
This
approach
is
challenging
tools
get
out
of
sync:
there's:
lack
of
visibility
for
various
roles
at
different
levels
and
overall
collaboration
and
communication
is
inefficient.
B
B
B
B
However,
we've
learned
from
working
closely
with
our
customers
that
having
separate
objects
with
separate
behaviors
in
each
has
resulted
in
some
usability
challenges.
For
example,
epics
are
only
available
in
groups.
Issues
are
only
available
in
projects,
we
have
assignments
on
issues
and
some
customers
need
assignees
on
epics.
B
We
are
working
toward
consolidating
the
objects
into
a
more
flexible
approach
using
work
items
instead
of
maintaining
distinct
objects
with
special
properties.
We're
merging
the
objects
into
a
single
core
work
item
work
items
will
give
you
all
the
great
functionality
that
we
have
in
separate
objects
in
a
single
place,
you'll
be
able
to
create
work
item
types
with
distinct
properties
and
work
on
hierarchies
to
represent
different
levels
of
work,
we're
also
planning
to
introduce
custom
fields.
B
B
B
B
B
B
Remember
how
I
said
we
dog
food
or
tool.
This
is
one
of
the
features
that
I
really
enjoy.
In
my
time
I
get
love.
I've
found
so
much
value
in
this
I'm
able
to
follow
work
along
in
our
issues
without
talking
to
an
engineer
since
we're
globally
distributed,
there's
not
a
lot
of
times
in
the
day
when
the
whole
team
overlaps,
so
having
this
information
and
being
able
to
self-serve
is
so
valuable,
and
it
helps
me
on
our
value
of
working
async.
B
B
B
Our
animation
helps
us
label
issues
leaves
comments
and
mentioned
teams,
members
based
on
an
array
of
rules.
Unfortunately,
this
currently
lives
outside
the
product.
In
a
separate
of
open
source
repository,
we
will
work
toward
making
this
functionality
available
as
a
first
class
experience
in
gitlab
and
reduce
the
manual
setup
required
to
enable
it
now
remember
how
I
was
going
to
need
your
participation
get
your
pencils
ready,
because
now
is
the
time.
B
B
B
However,
we
all
know
that
things
happen.
The
key
is
whether
a
team
can
change
plans
and
pivot
quickly
enough,
using
downstream
devops
data.
We
have
an
opportunity
to
highlight
risk
and
potential
disruption
to
your
plans.
It's
time
for
your
participation
again,
so
pay
attention
we're
going
to
walk
through
an
example.
What
this
could
look
like
here,
I
show
how
we
could
potentially
set
thresholds
on
monitoring
alerts,
and
these
could
be
used
to
inform
engineering
managers
and
product
managers
that
they
may
need
to
reconsider
their
plans.
B
B
Incorporating
devops
data
into
planning
and
prioritization
processes
allows
teams
to
evaluate
and
prioritize
technical
improvements
objectively,
all
right
same
format
as
last
time.
I
would
love
if
it
could
take
one
minute
to
type
into
chat
and
idea
for
how
downstream
devops
data
could
help
your
team
make
better
plans
in
case
you
need
some
inspiration,
think
about
measuring
the
number
of
deployments
over
time
and
if
changes
to
that
would
necessitate
prioritizing
some
things.