►
From YouTube: Dev Group Conversation (Public Livestream)
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
Welcome
to
the
dev
group
conversation,
my
name
is
Eric
Brinkman
I'm,
the
product
director
for
the
dev
section
and
I'm
joined
by
the
rest
of
our
team,
including
our
engineers
or
dev
managers,
our
product
managers
and
Tim
Zalman,
who
leads
up
the
engineering
side
of
the
dev
section
house
and
so
looking
forward
to
having
a
great
discussion
today.
The
deck
is
in
the
agenda
and
Tim.
You
actually
have
the
first
icebreaker
question.
So
do
you
want
to
go
ahead
and
take
it
away?
Yes,.
B
Thanks
a
lot
for
the
intro
and
yeah
in
a
two
minute
of
conferences
and
a
fireside
chats
and
conference
panels,
I'm
going
to
try
out
to
ask
the
first
questions
and
it's
not
cheating
if
anyone
is
asking
so
Eric,
and
especially
also
all
the
other
product
managers.
But
do
you
think
in
terms
of
dark,
folding
and
being
excited,
especially
over
the
next
two
three
months?
What
other
features
that
you
think
from
your
side?
A
C
I'll
speak
up,
I
think
that
I'm
really
excited
about
the
analytics
work
that
Virginia's
been
working
on
on
the
manage
stage.
I
think
that
it
has
the
potential
to
really
give
us
a
lot
of
insight
in
terms
of
like
our
engineering.
Throughput
is
good.
You
know,
we've
we've
been
kind
of
managing
around
these
with
with
tools
like
insights,
but
I
think
it's
I
think
she's
leading
a
lot
of
great
work
and
actually
like
dogfooding,
some
of
that
information
in
the
products
I'm
personally
excited
to
see
how
that's
going
to
change
our
engineering
organization.
D
D
Obviously,
engineering
managers
are
our
the
persona
as
well,
but
most
sometimes
engineering
managers
actually
have
a
good
view
of
what's
happening
if
they
don't
manage
too
many
people,
although
it
get
left
picture
they're
always
managing
to
money,
but
I
think
it
would
be
great
to
have
to
have
your
feedback
because
we're
very
engineering,
heavy
organization
and
we
can
actually
build
the
tools
that
make
us
become
more
efficient
and
more
productive
and
I.
Think
there
are
not
many
companies.
That's
that
can
do
that.
D
But
I
guess
I
can
I
can
maybe
just
a
hijack
a
little
bit
more
time
for
that,
but
one
one
of
them
is
basically
productivity
analytics,
which
is
very
much
focused
on
the
time
it
takes
to
emerge
on
the
mark,
and
we
we
know
from
from
our
experience-
that's
very
much
related
to
size.
So
we
have
basically
couple
of
charts
that
should
help
with
those
patterns.
It's
very
much
related
to
size,
it's
usually
dependent
as
well
on.
D
We
also
want
to
have
a
way
to
obviously
represent
the
waiting
time
and
the
block
time
and
I
would
I
would
love
to
get
some
feedback
on
that,
because
I
think,
for
example,
applying
many
labels
would
usually
need
to
bad
quality
and
stuff
like
that.
But
if
engineering
can
figure
out
a
way
that
we
can
do
this
automatically
so
that
they're
not
asked
to
do
such
menial
tasks,
lb
I
would
be
happy
to
to
progress.
Yeah
I'm
quite
excited
actually
and
I
would
really
love
people
to
start
dogfooding.
The
animated
features.
E
This
is
Scott
I'll
speak
up
on
behalf
of
Kenny
who's,
doing
a
see,
a
shadow
right
now,
dogfooding
D
the
incident
management
and
monitoring
capabilities
over
in
the
ops
area.
It's
going
to
be
a
huge
win
for
us
to
learn
really
fast.
We
haven't
had
all
that
much
customer
adoption
yet
so
we
really
want
to
accelerate
our
learning
curve
and
getting
that
feature
set
to
our
own
teams
can
use
them
and
get
value
out
of
them
should
be
mutually
beneficial.
F
Say
from
the
knowledge
group
I
think
we're
most
excited
about
design
management,
it's
really
seeing
in
12
and
it's
on
canary
now
and
so
I
think
we're
excited
to
start
getting
feedback
from
all
of
the
you
Xers
and
product
designers.
Here
at
I,
get
lab
on
how
this
works
or
doesn't
work
for
them
and
what
we
can
do
to
improve.
It
I
think
that's
the
one
that
I'm
personally
most
excited
to
see
finally
make
it,
make
it
into
the
app
and
start
getting
some
feedback
on.
G
This
is
fabian,
I
think,
from
from
my
perspective.
One
of
the
things
I'm
really
excited
about
is
to
see
improvements
on
how
we
use
our
roadmaps
and
epics.
I
think
there
are
quite
a
few
interesting
things.
We
had
something
recently
behind
feature
flags
that
displayed
epic
trees
a
little
bit
differently.
That's
really
exciting
or
features
to
do
with
you
know,
expanding
and
contracting
certain
ethics
in
roadmaps,
working
with
that,
I
think
is,
is
something
that
I'm
really
looking
forward
to,
because
I
use
it
every
day.
So
I'm
really
really
looking
forward
to
that.
A
Cool
I'll
voice
over
the
one
while
Scott's
typing
his
his
next
question,
I'm
excited
for
just
in
general
plan
becoming
a
little
bit
easier
to
use
so
there's
things
that
are
not
necessarily
associated
with
dogfooding,
but
they're.
Just
gonna
make
the
product
a
lot
more
lovable.
So,
for
example,
ability
to
move
multiple
issues
from
one
board
list
to
another
board
list
is
just
making
boards
easier
to
use.
E
A
Yeah,
this
is
gonna,
be
funny,
because
this
is
like
one
of
those
we're
gonna
ask
your
spouse.
What
you
know,
what
your
favorite,
what
your
favorite
food
is
and
then,
if
you
actually
see
if
you
actually
agree
we're,
obviously
so
just
to
get
set
context
on
why
there
might
be
disagreement,
we're
working
through
the
one
year
playing
currently
at
the
dev
section,
which
obviously
that
plane
would
have
each
of
these
themes.
A
It's
still
a
work
in
progress
right
now,
but
I
would
say,
I'll
provide
these
themes
and
then
I
would
love
for
each
of
the
PM's
to
kind
of
speak
up
on
in
each
of
the
each
of
the
stages
so
for
managed.
I.
Think
there's
two
two
big
themes.
The
first
big
theme
is
like
making
the
product
more
Enterprise
ready.
So
that's
ensuring
that
off
options
are
available.
It's
essentially
a
hook
up
things
like
you
know,
octa
and
LDAP
and
making
sure
that
smart
card
authentication
works.
A
This
is
really
big
in
a
public
sector,
so
it's
more
Enterprise
ready
and
more
regulated,
Enterprise
ready
and
then
the
second
one
would
be
analytics.
So
it's
it's
helping.
Our
customers
understand
the
cycle
time
through.
You
know
what
they
would
define
as
their
about
their
value
stream.
There's
a
lot
more
coming
on
on
value
stream
management
in
the
near
future
working
and
putting
that
ole
vision
together,
but
naive
stream
management
is
essentially
the
time
that
it
takes
to
do
your
value-added
steps
through
the
process
and
so
really
excited
that
we're
going
to
kind
of
help.
A
Our
customers
understand
how
gitlab
is
helping
them
really
helping
them
through
their
developer
transformation.
We
talked
about
that
a
lot
yesterday
in
our
vision,
casting
session
for
value
stream
management,
and
we
kind
of
got
this.
We
kind
of
landed
on
this
question
of
how
do
companies
prove
to
their
upper
management
to
their
consultants,
that
their
DevOps
transformation
is
being
successful.
I
think
that
value
stream
management
is
a
way
for
organizations
to
start
to
do
that.
So
I
think
those
are
two
really
cool
themes.
I'm
excited
for
and
manage
in
plan.
A
I
think
we
we
need
to
start
taking
a
look
at
how
we
can
truly
take
a
dent
out
of
JIRA,
and
so
I
think
this
is
going
to.
This
is
going
to
challenge
some
of
the
paradigms
that
we've
we've
had
recently,
which
has
always
been
like
designed
for
modern.
First,
we
have
done
a
great
job,
designing
for
kind
of
modern
product
management,
workflows
in
terms
of
making
small
primitives
and
we're
using
the
small
primitives
to
solve
for
a
variety
of
use
cases,
but
there
are
just
some
mainstays
in
some
of
these
other
project
management
tools.
A
So,
to
give
you
a
quick
example
like
wiki's,
like
wiki's,
is
a
category
that
we
have,
that
that's
complete,
but
it's
not
it's
not
lovable,
because
wikis
are
only
available
at
the
project
level
not
available
at
the
group
level,
which
is
really
important
for
an
organization
and
so
I
think
it's
making
things
like
that.
A
little
bit
easier
to
use.
A
It's
like
investing
into
technical
work
to
make
large
files
just
work
in
git
and
making
you
know
you
know
contributing
back
to
upstream
git
and
make
it
that
a
little
bit
better,
so
I
would
say
in
if
there's
one
theme
for
create
it's
making
the
stuff
that
we
already
have,
which
is
used
by
the
overwhelming
majority
of
our
customers.
You
know,
creates
the
one
stage
where
nearly
a
hundred
percent
of
people
who
are
using
git
lab
use.
A
The
107
people
use
create
it's
making
that
just
work
a
little
bit
better
and
solving
for
some
of
these
use
cases
that
are
prohibiting
people
from
moving
off
with
tools
like
perforce
and
and
other
things
like
that.
So
I
would
love
for
the
PM's.
That
kind
of
chime
in
this
is
that's
a
meaty
question,
but
I
think
it's
a
really
important
one.
Thanks.
E
C
From
the
manage
side,
I
think
that
you
hit
on
two
huge
themes
that
the
seem
that
the
stage
tries
to
work
on
I.
Think
Enterprise
readiness
is
absolutely
a
focus
of
like
the
axis.
The
access
group
seeks
to
kind
of
understand
and
dive
deeply
into
areas
like
compliance
and
permissions
and
off,
but
all
kind
of
touch
on
the
new
prezz
readiness,
I'm
sure
Virginia
would
definitely
agree
on
the
analytic
side.
With
all
the
sentiments
you
mentioned,
I
think
what
wasn't
mentioned
was
I.
Think
we've
created
this
new
import
group
with
a
dedicated
focus
on.
C
How
can
we
make
it
just
ridiculously
easy
to
get
started
using
git,
lab
and
I
think
that
we
plan
on
you
know
you
know
creating
that
group
with
the
focus
of
you
know
doing
things
like
jury
import,
and
you
know
in
creating
like
a
great
Jenkins
importer
to
make
like
getting
started
with
CI
this
ridiculously
unity.
So
I
think
that,
like
that
that
I
definitely
would
just
add
that
third
theme
of
just
making
adoption
super
easy
like
have
by
being
able
to
get
spun
up
and
get
labs.
Just
just
you
know,
frictionless
as
possible.
F
H
A
H
Think
it
was
just
more
around
better
feedback
for
how
a
team
is
progressing
through
our
given
release,
so
even
just
coming
in
I've
only
been
at
lab
for
four
weeks
now.
It's
my
fifth
I'm
used
to
having
better
feedback
and
reports
around
like
how
is
the
team
progressing?
What
is
a
breakdown
of
issue
types
that
we're
working
on?
What
can
we
possibly
get
done?
H
The
next
release,
based
on
our
historical
velocity
and
just
some
of
those
like
planning
questions
that
you
need
to
answer
on
the
team
level
that
we
don't
have
a
ton
of
built-in
visibility
right
now,
because
the
way
that
we
use
it
at
least
we
roll
everything
up
to
is
you
know
what
release,
and
so
we
can't
filter
that
down
by
different.
You
know,
product
area
or
by
you
know,
different
projects
or
teams
and
so
I
think
providing
more
feedback
for
users
around.
That
is
a
it's
a
really
requested
feature
from
customers.
So
you.
D
So
I
guess
this
is
my
main
team
as
well,
because
I
think
in
psycho
analytics
for
trying
to
to
do
just
that
where
customers
can
define
basically
the
the
stages
according
to
their
software
development
like
psycho
and
then
with
the
flow
and
type
of
work.
You
can
basically
select
the
different
labels
and
in
our
case
this
can
be
different
groups
or
different
stages
or
basically
books,
technical
debt
or
whatever
are
the
classifications
that
we
have
and
I'm.
Basically,
there
I,
like
the
community
flow
diagram
from
from
a
state
perspective.
D
A
I
It's
just
looking
for
a
little
more
a
little
more
expansion
on
the
ticking
indent
on
Ogier,
basically
trying
to
understand
you
know
what
the
needed
features
and
examples.
You
know
fine,
which
now
there
are
several
examples
in
there
which
that
definitely
helps
me
understand.
I
know
what
we're
looking
to
do.
You
guys
can
go
ahead
and
herbal
eyes.
The
rest
of
the
answers.
H
This
game
just
reiterated
kind
of
what
I
said
earlier.
The
concept
of
smaller
iterations,
like
sprints
I,
think
47%
of
companies
that
use
agile
use,
scrum,
which
is
sprint
based
and
the
rest
use
a
mix
of
Kanban
or
scrum
ban,
or
something
along
those
lines
and
so
kind
of
building
in
more
the
ability
to
have
these
kind
of
time
cycles
that
match
two
releases,
but
also
to
how
companies
organize
their
work
is
a
pretty
big
one.
A
Yeah,
there's
a
few
there's
a
few
others
that
you
could.
You
could
find
some
some
pretty
fun
issues
to
read
through
on
we're
close,
so
custom
enforce
workflows
with
approvals
I
just
linked
out
to
you
know
how
you
can
set
up
like
a
basic
workflow
in
JIRA,
and
that's
something
that
many
organizations
use
it's
something
that
you
can
kind
of
do
if
you
use
scope
labels,
but
you
can't
enforce
the
order
at
which
something
would
move
through
a
workflow
here.
A
A
Custom
fields
is
another
one,
so
pulling
out
some
custom
fields
or
tags
under
the
side
bar
obviously,
labels
are
are,
can
can
be
used
to
solve
this
problem,
but
it's
something
that
JIRA
has
them
and
we
we
don't
other
things
that
just
make
the
Kanban
process
a
little
bit
easier,
like
cumulative
flow
diagrams
to
help
kind
of
measure
the
burndown
of
work,
although
it's
more
of
like
a
stack
up
or
a
burn
up
rather
than
a
burn
down,
but
to
understand
the
apps.
You
understand
in
cycle
time.
A
If
you
look
from
left
to
right
and
then
understands
you
know,
are
you
getting
better
you
getting
worse?
Are
you
closing
things
is
something
diverging
in
your
process,
so
I
would
like
to
see
cumulative
flow
diagrams
in
our
product
soon
and
then
the
last
thing
I
wrote
here
too,
and
we
talked
about
this
in
the
last
plan
group
conversation
which
we
don't
have
anymore
so
I'm
happy
to
link
that
deck
or
if
someone
else
can
find
that
and
link
it.
That
would
be
helpful,
but
we
talked
about
this
as
well.
A
It's
just
making
it
easier
to
move
from
JIRA.
I
think
this
is
this
is
something
that
is
difficult
to
do
today,
because
oftentimes
people
have
invested
into
workflows
in
JIRA,
or
they
just
have
like
a
specific
setup.
That
they've
invested
a
lot
of
configuration
into
and
we
don't.
We
don't
have
a
lot
of
those
configuration
things,
which
is
why
we're
really
waiting
things
like
enforce,
workflows
and
custom
fields,
because
those
are
heavily
utilized
by
organizations
currently
using
JIRA,
so
making
that
a
little
bit
easier
would
be
would
be
helpful.
A
J
So
I'm
just
wondering
you
know
in
terms
of
JIRA
in
previous
places,
when
I
was
a
jury
user,
like
the
concept
of
ethics,
was
the
baseline
and
that
just
kind
of
existed
and
we
keep
it
all
the
way
up
at
the
ultimate
tier.
So
you
know
for
folks
who
want
to
adopt
us,
but
don't
need
to
go
all
the
way
to
ultimate.
How
impactful
is
that
that
are
you
know
just
a
core
thing
of
grouping
things
together
in
clustering.
Epics
is
all
the
weight
altima.
We
have
measurements
on
that.
A
I'll
speak
a
little
bit
about
the
decision
to
put
there
to
put
FX
into
ultimate
and
then
kind
of
what
we're
what
we're
doing
to
re-evaluate
this
holistically.
And
then,
if
there's
a
specific
follow-up
question
you
have,
let
me
know
and
happy
to
address
that
so
epics
are
originally
introduced
into
into
ultimate
on
a
buying
model
or
tier
model
that
we
we
no
longer
have
so
just
to
back
up
a
second.
The
way
that
product
management
introduces
features
into
various
tiers
is
based
off
of
what
we
call
the
likely
buyer
persona.
A
And
so
you
can
go
to
the
the
CEO
pricing
page
I'll
link
it
here
in
a
second,
when
I'm
done
talking
and
there's
we
have,
we
have
four
tiers.
So
obviously
there's
there's
cord
and
there's
bronze
silver
gold
if
you're
uncle
of
calm
or
there's
starter
premium
ultimate,
if
you're
on
self-managed
and
the
the
essentially
the
the
buyer
persona
for
each
one
of
those
tiers
is
mapped
to
individual
contributor
manager,
director
executive
respectively,
and
so
you
bring
up
a
good
point
which
is
I.
A
Think
questioning
if
epics
is
maybe
in
in
the
which
one
world
taking
a
look
at
holistically
of
all
of
our
features,
but
the
other
thing
about
putting
epochs
in
ultimate
is
that
we're
not
getting
a
ton
of
feedback
right
because
we
don't,
we
don't
have
it
in
a
lower
tier
that
other
people
might
be
using
and
so
I
would
say.
Like
the
vast
majority,
if
you
ask
for
data,
the
vast
majority
of
get
live.
Customers
are
not
using
epics,
because
the
vast
majority
is
not
on
on
ultimate
it's
on
it's
on
a
little
lower
tier.
J
It
does
and
I
just
think
from.
Maybe
you
know
a
value
standpoint
that
epics
allow.
You
is
develop,
a
be
more
iterative
because
you
can
break
things
into
smaller
pieces
and
track
it
across
a
longer.
You
know
a
longer
pipeline,
so
I
almost
feel,
like
that's
I
hate,
to
say
it's
almost
a
base
feature
but
its
core
to
how
we
want
the
developer
world
to
work
right.
Don't
do
a
big
issue.
Do
an
epic
break
it
up
into
small
pieces
and
track
it
across
so
to
me.
J
I'd
almost
put
that
all
the
way
down
into
community
right.
It's
that
basic!
Now,
the
tracking
right.
If
people
want
extra
tracking
and
all
that
that's
more
enterprising
features
that
appeals
to
be.
You
know
that
different
persona,
but
again
I,
just
I've,
always
seen
that
as
kind
of
a
curious
thing
about
our
offering,
because
it's
included
by
default
batteries
included
in
most
of
our
competitors,
so
yeah
that
answered
my
question.
I
just
I
just
noticed
that
I'm
trying
to
find
there
was
issue
for
it
that
was
opened
a
while
back
and
I
can't
find
it.
A
A
We
shouldn't
have
it
both
ways
where,
like
we
say
that
hey
the
way
that
we
put
features
into
various
tiers
is
based
off
of
the
buyer
persona
and
then
say
like
well,
except
for
epics,
like
we're
just
gonna,
throw
that
one
in
ultimate
like
we
should
be
consistent,
and
just
so
you
know,
product
overall
holistically
is
taking
a
look
at
all.
Essentially
all
features
that
we
have
that
are
paid
by
each
stage
and
kind
of
doing
this,
essentially
bulk
evaluation
of.
A
K
Okay,
mech
you've
got
the
next
item.
Yes,
sir,
so
speaking
about
epics
I
am
personally
very
excited
for
that
issue,
so
that
our
activities
can
contain
discussion
that
we
make
in
epics
now,
because
right
now
you
make
something
a
comment
on
an
epic
it
just
doesn't
get
captured
in
in
our
activity
feed.
So
this
would
help
with
discoverability
and
make
it
a
lot
easier.