►
From YouTube: DORA4 Metrics design Discussion
B
D
C
A
A
E
A
So,
just
to
talk
about
the
persona
and
who's
interested
in
door,
four
metrics,
there's
really
two
that
we
noted
in
the
issue.
Maybe
there's
more
but
there's
two
that
we're
kind
of
are
focusing
our
first.
One
of
them
is
for
the
executive
team,
which
is
interested
in
like,
but
how
the
company
is
doing
or
how
different
groups
are
doing
and
they're
really
interested
in
seeing
performance
of
different
groups
around
devops
and
their
entire
sdlc
lifecycle
and
the
other
one
is
the
specific
team
that
are
interested
in
their
own.
A
E
A
E
A
C
Okay,
should
I
move
on
to
the
the
premium
dashboard
that
we
talked
about
cool,
so
the
next
one
is
available
at
premium.
This
is
a
project
level
analytics
ci
cd.
We
still
have
that
dora
4
at
the
top,
just
like
we
did
for
core
users.
The
difference
here
is
that
we
are
now
introducing
this
door
of
4
tab
which
will
contain
all
the
door
4
metrics,
so
the
ci
cd
analytics
that
stays
the
same
as
what
it
is
now,
but
for
premium.
C
They'll
get
a
new
dashboard,
and
the
idea
here
is
that
for
each
of
the
door,
four
metrics
we
will
show
a
full
chart.
So
it's
going
to
be
that
metric
over
time,
starting
with
kind
of
hard
coding,
30,
90
and
180
days,
I
believe
and
then
being
able
as
a
post-mbc
idea
to
be
able
to
let
the
user
define
that
kind
of
time
line
a
little
more
effectively.
C
So
we'll
see
a
chart
for
deployment
frequency
we'll
see
one
for
leading
lead
time
to
change
time,
to
restore
service
and
change
failure
rate
right
now.
These
metrics
are
all
going
to
be
based
off
of
production,
and
that
is
a
hard-coded.
It
is
going
to
be
quote
per
prod
production,
I'm
not
sure
what
it
actually
is.
We
think
we
have
an
issue
right
now
to
make
it
something
more
flexible
and
then
the
long-term
goal
is
going
to
be
letting
users
select
what
environment
the
metrics
are
going
to
be
displayed
at.
A
Absolutely
so
we're
making
it
a
little
bit
more
flexible
now,
but
we
want
to
make
it
and
nathan
is
very
active
in
that
issue.
We
want
to
make
that
multiple
selection-
or
I
don't
know
somehow-
for
users
to
be
able
to
select
whatever
environments
they
want,
because
even
internally
in
gitlab
we
don't
use
production
so
at
least
for
dog
pudding.
A
This
is
the
day
that
we
created
a
release,
or
this
is
the
day
that
we
closed
a
release
or
maybe
even
going
into
deploy
freezes
flags
going
on
and
off
like.
I
want
to
know
what's
going
on
in
my
system
in
order
to
understand
these
metrics
more
because
charts
are
great,
but
you
know
you
really
need
a
lot
of
background
information
to
know
like
what's
going
on
there.
So
annotations
is
something
really
nice
that
we
will
add
not
as
part
of
the
nbc
and
also
historical
data.
C
A
D
A
Yes,
it
takes
if
you're
deploying
through
the
back,
if
you're
not
deploying
through
gitlab
you're,
not
getting
these
metrics
but
we're
taking
the
internal
data
that
we
have.
We
added
an
api
in
the
previous
milestone
that
allows
you
to
get
to
fetch
the
data
and
what
nathan
is
doing
is
actually
presenting
that
data
into
the
ui.
So
you
can
get
this
data
both
on
ui
and
go
that
api.
A
You
can
import
it
into
an
external
system,
but
if
you're
doing
cd,
you
know
with
aws
code
deploy
or
with
finicker
or
something
else
you're
not
going
to
be
able
to
see
these
metrics
each
metric
is
defined
a
little
bit
different.
So,
for
example,
lead
time
for
changes.
We
define
this
as
how
long
it
takes
for
a
merge
request
to
get
to
get
merged
into
production.
A
So
again,
if
you're,
not
using
ci
you're,
just
using
first
control,
I'm
not
going
to
help
you
time
to
restore
service.
It
also
depends
if
you
have
deployments
through
gitlab
and
change
failure
rate
we
defined
it
by
how
long
it
takes
to
close
incidents.
So
if
you're
not
using
gitlab
incidents
at
the
moment,
you
really
can't
benefit
from
it.
I'm
sure
we're
going
to
need
to
add
additional
integrations
of
the
when
we
proceed,
but
not
part
of
the
nbc
at
the
moment.
A
A
The
icd
metrics,
on
the
other
hand,
will
release
they
probably
can
so
just
duracore
for
ultimate
is
going
to
be
group
level.
The
idea
at
the
end
is
that,
since
the
majority
of
our
users
are
self-managed
they're
actually
going
to
want
instance
level,
I
didn't
define
it
as
part
of
the
nbc,
but
it's
probably
going
to
be.
You
know
the
next
task.
C
C
I
had
from
the
design
perspective
to
show
was
exactly
what
nathan
just
brought
up.
We
only
for
the
ultimate
tier
should
there
be
these
group
level
analytics
the
analytics,
look
the
same
in
the
design,
but
they'll
be
at
the
group
level
for
the
mvc
I'd
like
it
to
look
very
similar.
I
would
imagine
and
correct
me
if
I'm
wrong
as
a
post
mvc,
we
might
want
to
look
at
the
way
that
groups
are
managed
in
the
dashboard.
A
Yeah,
what
I
do
want
to
mention
here
on
the
ultimate
on
the
ultimate
dashboard
is
that
we
are
now
seeing
a
group
of
projects.
So
again
this
is,
it
doesn't
have
to
be
part
of
the
nbc,
but
I
do
want
to
kind
of
explain
the
broad
vision
in
a
similar
way
that
we
could
select
the
timestamp
and
the
environment.
A
A
If
you
remember
when
we
way
back
when,
when
we
had
an
initial
discussion
in
the
dora
4,
we
kind
of
talked
about
gamification
in
dora
4,
so
just
for
the
uploaders
that
weren't.
In
that
conversation,
I
just
want
to
take
us
back
and
kind
of
explain
what
we
were
thinking
about.
So,
if
you
think
about
dora
for
the
instance
level
or
even
nicer
in
gitlab.com,
we
have
a
ton
of
data
that
others
don't.
So
we
have
a
bunch
of
different
projects
from
different
companies
and
we
have
all
this
aggregation
data.
A
A
I
don't
know
we
can
define
that
in
different
ways,
but
actually
see
how
you're
performing
versus
other
companies
would
be
really
really
interesting,
because
you
want
to
know
that
you're,
a
high
performer,
it
kind
of
gives
you
some
of
that
competition.
You
know,
juice
competitive,
you
know
flow,
and
so
we
were
even
thinking
of
doing
badges
and
even
I
think,
even
design
badges
for
that
to
kind
of
show
you
you're,
awesome
or
or
you
need
to
improve-
and
we
were
thinking
of
doing
like
something
similar
also
for
group
level.
A
So,
if
you're
really
interested
in
a
group
of
developers
or
several
software,
agile
teams-
and
you
kind
of
want
to
do
some
kind
of
you
know
competition
between
them,
you
can
show
how
amazing
your
team
is
versus
others,
and
it
could
be
really
really
cool,
but
definitely
not
part
of
the
university.
Just
you
know
part
of
my
wild.
A
E
So
one
more
question
about
this
again
kind
of
related
to
the
the
different
tiers
so
for,
if
you're
a
premium
customer
at
the
project
level,
and
then
you
upgrade
to
ultimate,
is
there
any
difference
in
the
project
level
page
or
would
those
be
ident?
The
only
change
in
ultimate
is
that
we're
adding
it
to
the
group.
A
A
A
So
we
can
do
two
things:
either
consolidate
the
view
that
we
have
today
from
three
to
one
having
this,
you
know
easy
way
to
navigate
between
the
charts,
because,
basically
we're
showing
the
same
chart
for
just
different
kind
of
sets,
there's
no
difference
in
the
charts
that
was
the
spanking
and
then
just
adding
renaming
the
tab
and
adding
the
metrics
one
by
one.
So
whatever
you
prefer
at
some
point,
we're
going
to
need
to
do
it.
A
E
I
I
personally
really
like
the
look
of
these
mock-ups
right
here,
so
that
yeah,
I
don't
know
what
the
correct
path
is
toward
that,
but
that
that
makes
a
lot
of
sense
to
me,
and
this
gives
us
a
lot
of
flexibility
like
we
could
eventually
replace
that
30
90
180
button
group
with
like
a
custom
date
range
which
is
nice
like.
If
we
wanted
to
do
that
or
or
we
can,
we
can
filter
all
of
them
by
the
same
environment.
So
I
think
this
structure
gives
us
a
lot
of
flexibility
going
forward.
C
Also
thinking
about
ultimate,
as
wanting
to
be
able
to
compare
and
contrast
later
or
be
able
to
dive
into
specific
metrics
for
specific
problems,
if
we
condense
them
all
into
the
door
of
four
tab.
Now,
when
we're
done
with
the
mvc,
then
we
can
start
using
the
tabs
to
show
really
fine
detail
data
or
those
comparisons
and
stuff
like
that.
It
gives
us
more
flexibility.
Moving
forward.
A
Awesome,
so
if
we're
all
good
with
this
we'll
add
this
I'll
create
a
new
issue
to
consolidate
the
charts,
we'll
add
it
to
the
needs
weight
as
as
always
and
then
plan
for
the
iteration,
the
further
implementation
of
it.
Okay
and
then
we
can
move
forward
on
that.
There
is
one
more
thing
that
I
want
to
mention,
and
that
is
the
value
stream
analytics.
A
So
it's
analytics
team,
which
are
now
called
something
else.
Optimized
have
already
created
and
created
some
sort
of
dora
for
metrics
in
a
file
view
and
we're
not
showing
the
same
data.
So
I've
had
conversations
with
them
that
we
should
probably
align
to
share
the
same
data.
They
count
it
a
little
bit
different
than
we
do
so.
A
I
expect
that
we're
going
to
start
collaborating
closer
to
them
and-
and
we
kind
of
need
to
share
the
knowledge
between
the
two
teams-
we're
not
showing
exactly
the
same
things,
because
they're
they're
staying
at
final
view,
which
is
similar
to
what
we're
doing
in
core,
but
I
wouldn't
want
to
show
different
values,
value
analytics
and
in
the
cic
analytics.
So
since
they
don't
have
an
api,
I
think
it's
it's
more
flexible
to
use
our
solution,
which
is
how
we
started
out.
A
We
were
thinking
about
stealing
their
data,
but
there's
a
lot
of
limitations.
One
is
that
there
there
wasn't
an
api
that
we
could
have
used
and
the
other
one
is
that
it's
locked
to
production
similar
to
how
we
started,
but
we
quickly
decided
to
expand
the
api
at
the
least
and
then
maybe
even
allow
selection
of
any
any
environment
that
you
want.
So
we're
going
to
have
to
you
know,
consolidate
those
two
so
that
we're
showing
a
single
sort
of
this
truth
and
people
are
not
like.
A
D
For
it,
I
have
a
comment,
a
question
about
the
namings
of
the
tab.
So
the
left
tab
is
ci,
cd
analytics
and
the
right
tab
is
d4.
But
d4
is
not
part
of
scientific
analytics,
it's
kind
of
analytics
for
ci
cd
right
and
it
looks
like
a
different
thing.
There
is
icd
analytics,
and
so
maybe
something
with
the
naming
has
to
be
adjusted.
A
E
A
D
E
B
B
I
think
would
be
interesting.
Well
if
the
scope
didn't
change
right
for
the
release.
Page,
I
think,
would
be
interesting
to
then
have
I
don't
know
a
shortcut
somewhere
in
the
release
page
where
I
can
link
the
users
here,
if
that's
the
case,
so
that
the
flow
doesn't
doesn't
change
that
much,
but
indeed,
if
you're,
showing
the
metrics
for
pipelines
for
releases
etc.
A
E
B
E
E
Yeah,
so
that's
what
I'm
working
on
this
milestone,
so
I
just
want
to
make
sure
that
this
basically
the
work
I'm
doing
here
isn't
wasted
like
we
have
a
place
for
a
vision
for
it
in
our
in
our
page.
So
I
I
think
that
if
we
add
like
a
releases
tab
like
we
showed
on
the
other
one,
that
would
make
sense
to
me.
B
A
I
think
we
could
probably
come
up
with
a
bunch
of
really
interesting
release.
Metrics,
like
how
many
issues
are
an
average
in
the
release.
How
many?
Mrs,
the
duration
of
a
release,
I
think
we
can
come
up
with
really
interesting
metrics
along
the
way,
though
it's
out
of
scope
for
mordor
for
discussion,
but
just.
B
A
A
D
C
Also
add
the
designs
here
with
the
notes
that
we
put
together.
So
there
is
just
one
place
that
is
like
this
is
our
overall
vision
and
then,
if
there
is
a
discrepancy
between
an
individual
issue,
we
can
always
reference
back
to.
This
is
where
we
last
decided
we're
all
going,
so
that
might
also
make
it
a
little
bit
easier
for
you.