►
From YouTube: CDF SIG Events - April 24, 2023
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
A
B
A
D
Things
are
good
I'm
working
on
I'm
working
on
delivering
a
workshop
on
identifying
value
streams
that
I'm
going
to
be
running
tomorrow
and
so
I
kind
of
split,
my
time
between
the
value
stream
management,
Consortium
and
my
own
Consulting
and
so
I've
got
a
I've,
got
a
couple
clients
that
I'm
running
right
now
and
then
doing
work
for
the
the
vsmc
trying
to
trying
to
help
build
out
material
for
them
so
that
the
kind
of
members
have
a
lot
of
information
that
is
kind
of
missing
right
now,
like
there's,
not
a
lot
of
information
out
around
value
stream
management
and
software.
B
A
I,
haven't
really
sorted
out
my
mind.
Well
what
the
outcome
was
yet
I
plan
to
do
that
during
the
weekend,
but
I
had
other
things
studied
at
that
time.
So
I
couldn't
so
it
was
a
great
place
to
meet
people.
There
I
need
some
people
face
to
face
as
well.
C
D
Yeah,
it's
been
a
while,
since
I've
been
to
a
conference.
Actually
it's
been
probably
since
this
time
last
year
conference
season
last
year,
I
don't
think
I've
been
to
a
conference
yet
but
I've.
C
A
Just
bring
out
the
attend,
Minister,
sorry,
not
friends
with
Google.
Yet
sorry.
A
A
D
C
C
A
Also,
this
was
something
I
wrote
during
our
last
COC
meeting,
where
you
also
were.
Were
there
published,
I
wrote
the
wrong
date,
so
it
is
today
it's
not
perfect
all
right,
but
I
hope
we
can
have
that
discussion
now,
absolutely
a
joint
work
group.
So,
let's
just
first
sign
in
ourselves,
I
sign
in
myself.
So
you
know.
B
B
A
A
We
are
now
looking
forward
to
the
next
release,
which
is
zero
three
plan
for
the
end
of
this
month,
which
ends
in
the
week
and
the
focus
there
will
be
declaring
signed,
artifacts
to
events
and
also
Implements
of
test
device.
So
there
are
two
different
pull
requests
for
these
two
initiatives
which
we
hope
to
merge
soon
and
once
those
are
merged,
we
can
also
create
the
release.
One.
A
That's
what
I
intended
to
say
about
the
CD
events
updates
then
from
the
TOC.
You
were
both
there
on
the
last
meeting,
so
it's
not
too
much.
Oh,
this
is
our
place.
Sorry
about
the
top
six
sponsors
I
didn't
remove
this.
Maybe
we
should
refresh
this
now.
I
think.
Is
it
the
Andrea
that
Tracy
was
elective
sponsor
for
for
Sig
events
or
what
she
asked
volunteering,
and
then
nothing
happened
or
do
you
know
who
the
state
is
there.
A
A
C
I,
don't
think
we
have
a
very,
very
specific
process,
usually
well,
we'll
create
a
seek.
So
we
had
this
case
before
just
someone
volunteer,
it
was.
B
C
So
yeah,
that's
good!
So
she
volunteered
for
or
sponsor
no
yeah.
C
A
I
guess
the
mail
there
was
sent
to
to
you
as
a
chair
of
the
TLC
and
the
TOC
the
CC,
so
it
wasn't
really
sent
to
the
City
events
group.
So
no
one
else
in
the
City
events
might
have
seen
that
she
volunteered
but
I
guess
anyway,
since
we
happen
to
be
here
in
this
meeting
and
we
are
on
the
top.
We
saw
that
made.
That
was
good,
but
let's
just
state
it
tomorrow
on
the
TLC
as
well.
So
it's
formal
right
right.
C
A
A
The
roadmap
there
will
in
some
sense
be
affected
by
the
discussion
later
on
about
the
BSM
integration
or
a
joint
trying
to
work
there.
But
the
rest
is
outside.
That's
mostly
I
would
say:
yeah
I,
don't
know.
How
do
you
have
any
comments
down
here?
I
really
think:
should
this
be
pushed
for,
or
is
it
okay
that
we
stand
by
a
bit
or.
C
B
C
Session
at
some
point
like
making
some
blending
of
what
we
want
to
achieve
as
as
activities
for
for
the
year
for
the
upcoming
months,
at
least
so
that
we
don't
lose
like
Focus
Direction.
There.
B
C
A
I
think
this
might
need
some
preparation.
It
might
not
be
too
valuable,
just
start
talking
about
it
now,
so
we
propose
that
we,
we
postpone
this
discussion
to
to
the
next
Sig
meeting
and
I
can
try
to
prepare
something
before
that.
Obviously,
where
we
go
with
it,
then.
A
Those
elections
or
those
are
the
elections,
will
start
on
May,
9th
and
so
far.
I
think
that
the
the
action
actual
election
process
there
and
how
it
will
work
is
not
called
in
stone.
Yet
there
is
still
some
ongoing
discussions
on
exactly
how
this
should
be
done,
but
anyway
we
can
promote
someone
from
from
seed
events
to
be
our
representative
on
the
TLC.
Then
all.
A
Projects
on
CDF,
we
are
now
in
projects
today.
There
are
no,
not
nine
seats
in
the
talk
for
projects,
so
it's
only
four
seats,
so
there
would
be
an
algorithm
to
calculate
what
project
should
have
epoxied
and
so
on,
or
some
kind
of
election
so
anyway,
but
we
should
at
least
promote
someone
from
the
basic
events.
A
Sorry,
it's
no,
not
the
second
spot
for
the
CD
events
project
to
take
on
such
a
seat
if
it
will
be
available
for
us
I'm,
not
sure
if
we
can
postpone
that
as
well
for
the
next
one,
or
maybe
it's
better
to
have
that
on
slack,
because
since
we
are
so
few
people
here
now,
it's
it's
not
really
valuable
to
to
elect
someone
on
this
meeting
itself,
I
think,
but
that
we
should
have
a
comment.
A
Yeah
so
I
think
I
can
put
a
message
on
our
slack
Channel
there
to
see
who
would
like
to
volunteer
for
it
or
maybe
send
a
mail
even
to
see
who
would
like
to
volunteer
to
be
our
candidate
on
the
TLC
from
the
project.
A
I
will
do
that
then.
This
is
all
news
from
the
Outreach
committee.
I'm,
not
sure
this
needs
to
be
kept
here
or
yeah.
We
should
eventually
have
some
information
here.
This
was
discussed
last
week
and
that's
right
and
last
time,
but
that's
why
it's
still
here,
I'm,
not
sure.
If
there's
been
any
meeting
since
then,
no
it
hasn't
this
wasn't
much
or
are
you
on
those
meetings
Andrea,
you
were
there
last
time
at
least.
A
C
So
I
think
there
is
already
something
in
the
list
of
potential
topic
if
I'm
not
mistaken.
Yes,
so
the
number
five
interoperability
events,
but
these
are
just
like
ideas,
I
think
that
there
is
a
process
that
has
been
defined
on
and
it
will
work
exactly
so
I
think
there
will
be
need
for
a
sponsor
for
a
certain
topic
and
but
a
certain
process
basically
to
to.
A
Yeah,
well,
that's
all
we
expected
to
take
some
action
on
this.
Do
you
think,
or
should
we
wait
for
the
university
who
drives
this
now
I'm
confused
I?
Think
the
Outreach
committee
is
that
Karima?
No,
no!
It's.
C
B
C
Outreach
committee
is
lorry,
but
the
CDF
Workshop
itself,
I
think
they
it
has
its
own
leads,
I,
think
they're,
almost
and
Veronica
I
think
possibly
as
well.
I.
C
Right
so
I
think
it's
it's
up
to
us
really
how
if
any
of
us
thinks
that
we
we
have
bandwidth
or
interest
and
and
working
on
on
disks,
we
think
we
want
to
promote
or
World
Worship
in
this
area
we
can
do
but.
B
C
Right
now,
I
think
it's
personally
I'm
following
the
the
initial
meetings,
see
what
the
process
will
be
shipping
to
be
like,
but
yeah.
C
A
C
A
A
C
Next
meeting
is
going
to
be
on
Wednesday
s,
what's
in
the
calendar
and
then
May
the
10th
I'll
try
to
keep
joining
the
meetings,
or
at
least
following
what's
going
on,
if
I'm
not
able
to
join
the
meeting.
B
C
If
there
is,
if
there
is
interest
in
doing
something
about
interpretability
and
City
events,
I
think
it
would
be
good
for
someone
from
us
to
be
involved.
As
we
have
some
experience
already
building
pocs,
we
see
the
events
and
yeah,
but,
as
you
say,
this
I
don't
think
we
would
have
the
benefits
to
drive
this
initiative
from
our
side
right
now.
Yeah.
A
C
We
yeah
we,
we
met
with
the
cncf
app
delivery,
yeah.
A
C
That's
some
information
worth
mentioning
that
we've
learned
to
to
and
they
are
coming
emitting.
B
C
It's
on
May,
the
Third
yep.
B
A
B
A
Yeah,
but
that's
good,
so
they
can't
advice
to
mistake
and
if
they
want
the
proper
invite,
I
can
forward
it,
the
one
that
thought
they
sent
us
good
yeah.
That's
a
good
comment
s
should
we
then
go
on
to
the
main
topic
for
today,
since
Steve
is
here
and
obviously
Tracy
John
as
well.
Hi,
Tracy,
welcome
and
Tracy.
Hear
us:
hey,
hey,
hey.
B
A
E
And
I
I
did
everything.
I
I
could
do
on
the
white
paper
I'm,
not
sure
if
Fati
is
moving
forward
with
getting
that
done.
E
Andrea,
if
maybe,
if
you
can
follow
up
with
him
and
then
I
wanted
to
let
everybody
know
that
I
did
send
it
invite
out
to
some
of
the
folks
that
foughty
suggested
to
attend
the
CD
events,
project
Summit
as
well
as
they're,
going
to
put
it
on
the
main
schedule
and
I've
asked
them
to
list
it
in
the
press
release
but
I,
don't
know
if
they'll
get.
If
that
will
happen,
but
anyway
we
we
should
have
some
visibility.
With
regards
to
our
events.
C
E
Yeah
that
would
be,
that
would
be.
The
goal
is
to
know
that
we
had
introduced
what
we
were
up
to,
and
you
know
I
really
would
like
us
to
push
to
get
have
version
one
out
as
soon
as
we
can
I
don't
know
what
your
thoughts
are
on
it,
but
I
feel
like
it's
time
that
we
do
a
proper
we're
getting
some
eyes
so
it'd
be
good
to
do
a
proper
release
of
it.
E
I
think
I
think
we
have
a
aren't.
We
like
versioning
the
vocabulary.
If
we
could
get
a
kind
of
a
proper
you
know
say
this
is
the
first
cut.
It
would
be
good
foreign.
A
C
So
the
version
0.1
so
the
the
initial
version
we
we
did
cut
it
and
we
recently
made
0.2
and
we
are
planning
for
0.3
before
cdcon.
C
C
There
is
a
cubeconis
that
it
would
be
great
to
see
some
adoption
and
get
some
feedback
from
from
the
folks
that
were
working
on
CD
events
and
thinking
of
adopting
and
thinking
of,
like
Fidelity,
for
instance,
we're
going
to
implement
it
and
others
hopefully,
and
as
soon
as
we
get
some
some
feedback
from
from
adopters
I
think
we'll
be
better,
we'll
be
in
a
better
position
to
to
change
the
the
release
numbering
from
like
zero
dot,
something
to
to
a
1.0.
If
it.
E
Makes
sense
sounds
like
a
plan,
and
that
gives
you
know
the
CDF
from
the
Linux
perspective.
They
they
need
more
press
release
information
and
they
need
more
activity.
So
I
think
that
that
will
be
a
that
will
be
when
we
get
it
to
1.0
I.
Think
that
will
be
an
exciting
point
that
the
Fati
can
do.
Some
can
run
with.
C
Yeah,
absolutely
so
I
think
it's
been
yeah
in
fact
has
been
quite
quite
goods
and
collaborative
in
helping
us
being
in
the
in
the
press
release
until
now.
So.
E
Well,
I've
been
pushing
them
to
make
it
a
primary
goal
for
the
CDF
and
so
now
they're
starting
to
do
it
now
now
I
feel
like
we
need
to
start
really
delivering
some
regular
news
about
it,
I'm
watching
some
of
the
other
bigger
projects,
and
they
have
a
lot
of
news
coming
out
constantly,
especially
like
at
the
open
ssf
around
Alpha,
Omega
and
six
store.
They
could
be
at
a
very
you
know,
kind
of
have
an
MVP
out
there
and
they're
pushing
it
really
hard,
so
I
think
that
it
in
the
future.
E
We
should
start
thinking
about
getting
that
press
out
and
and
pushing
it,
even
if
we
feel
that
we're
it's
not
quite
there,
it's
okay
to
go
ahead
and
move
forward
and
on
that
I
have
to
jump
because
I
have
like
my
ortillas
calls.
So
I
just
had
a
bunch
of
calls
lined
up
today.
So
next
time,
I
will
be
here
on
on
time
and
not
interrupt
the
meeting
like
this,
but
thank
you
for
listening.
E
A
Bye,
yeah
I,
don't
know
in
there
about
the
the
more
versioning
should
we
have
some
more
action
on
that
now
than
or
push
for
it.
A
A
It
is
that's
from
my
perspective,
so,
from
my
perspective,
I
don't
have
that
strong
drive
to
to
push
for
1.0.
Yet
that's
just
my
yeah.
C
That's
yeah,
no
I
agree
something
in
in
the
future,
as
I
think
I
will
say
we
we
need
to
get
some
adoption,
but
I
think
it's
it's
good
that
we
have
like
proper
releases
now
and
yeah.
C
A
So
so
what
about
the
white
pepper?
So
we
don't
drop
that
that
ball,
I
think
the
the
last
mail
in
this
that
chain,
maybe
or
at
least
in
my
one
of
the
discussions
for
some
one
I
wrote
on
that
the
issue
so
not
yet
solved
completely.
A
So
we
have
this
one
where
we
it
was
discussed
if
we
should
have
a
new
link
to
the
the
book
implementation,
but
that's
not
and
very
close
I
guess
to
be
done
so.
A
C
But
I
think
what
we
we
discussed
with
48
cubicle.
It
was
that
at
least
we
should
make
sure
that
links
are
up
to
date,
so
so
yeah
I'll
try
to
follow
up
on
that
with
fatty
today.
C
C
In
my
understanding,
Tracy
provided
some
updates
already
include
incident
events
as
well,
but
yeah
and.
A
I
wrote
URLs:
we
don't
confuse
it
with
the
connected
events
initiative
with
links,
yeah
yeah,
good
thanks.
So
now,
let's
move
on.
We
have
passed
off
the
hour
and
now
since
you're
here
Steve,
we
should
have
some
getting
started
on
the
on
our
joint
initiative
there
on
vs
Mi
and
the
interoperability,
so
I
copied
some
information
from
our
last
talk
meeting
where
you
both
were.
A
We
have
the
proposed
Charter,
that's
maybe
something
we
could
look
into
now.
If
we
should
improve
this
in
some
way
or
what
we
should
do
about
that
we
have
already
meeted,
that's
I
mean
and
greeted.
A
So
that's
already
done
between
us
three
at
least
and
of
course
we
should
have
some
some
common
understanding
on
how
should
I
joined
meetings
be
be
planned
for
the
future?
A
We
I
think
we
discussed
on
the
DLC
that
we
could
have
this
as
as,
like
a
sub
work
group
in
the
Sig
events
yeah,
we
could
initially
maybe
have
it
as
one
recurring
item
on
our
Sig
events
meeting
this
this
meeting
now
every
two
weeks,
but
if
we
see
the
need
for
it,
we
could
break
out
break
it
up
to
a
separate
meeting
if
we
have
the
the
bandwidth
to
plan
another
meeting,
have
you
spent
any
thinking
about
this
Steve
since,
since
the
TLC
meeting
there
and
do
we
have
any
more
ideas
on
the
way
forward
for
us.
D
Yeah,
so
I
I
think
what
would
be
valuable
for
today
would
be
I
can
present
I,
don't
think
I've
shared
a
deck
that
describes
the
reference
architecture
from
our
perspective
and
where
we
can,
where
we
can
think
about
an
overlap
and
collaboration
with
CD
events
and
I.
Think
that
might
be
valuable
to
frame
all
of
this,
because
I
think
there
is,
there
is
still
a
possibility
of
you
know
you
folks,
saying
that
oh
this
doesn't
match
or
this
isn't.
D
If
that
sounds
valuable
and
then
I
think
that
should
inform
everything
else
that
we're
talking
about
like
meeting
Cadence
structure,
kind
of
cooperating
model
and
the
charter
as
well
I
saw
that
Andrea,
you
added
the
the
column
for
the
CD
events
aspect
of
the
charter,
which
was
which
is
very
valuable.
D
I
just
note
that
notice
that
this
morning,
but
I
I'll
review
that
and
I
noticed
that
there
were
comments,
so
I'll
I'll
make
sure
that
I
catch
up
on
that
if,
after
this,
after
this
event,
far
up
to
this
meeting,
but
I
can
take
you
folks,
through
the
reference
architecture,
presentation
that
we
have.
If
that
sounds
valuable.
C
B
D
Okay,
so
essentially
just
a
really
quick
establishment
of
terms
where
we
see
an
opportunity
right
now
is
that
there's
a
gap
and
there's
considerable
investment
in
progress
in
I.
Think
that
you
know
the
current
domain
of
of
CD
events
and
the
CDF
in
general.
In
that
delivery
has
got
a
lot
of
attention
and
even
kind
of
operations.
It's
got
a
lot
of
attention,
but
management
and
kind
of
visibility
measurement
at
the
scope
that
we're
interested
in
in
value
stream
management
is
kind
of
lagged
behind.
D
So
we
kind
of
group,
CI,
CD
pipelines
and
a
lot
of
you
know
current
efforts
under
this
idea
of
value
stream,
delivery
platforms
and
that's
kind
of
terminology
that
I
think
was
floated
by
Gartner
initially
a
couple
years
ago,
and
so
we
kind
of
follow
that
to
a
degree
as
a
frame
of
reference.
D
So
there's
kind
of
delivery
and
management
where
delivery
is
very
relevant
to
let's
say,
team,
lead
and
individual
contributor
and
management,
valuable
from
like
team
lead
and
above
right
across
the
organization
and
where
we
see
potential
here
is
kind
of
this
idea
of
managing
multiple
pipelines
within
value
streams.
Meaning-
and
we
don't
have
this
illustration
at
the
moment,
but
I
think
you
folks
are
familiar
with.
D
You
know
the
fact
that
you've
got
code,
pipelines,
data
pipelines,
multiple
different
collections
of
interconnected
pipelines
and
workflows
and
value
streams,
kind
of
wrap
that
all
up
into
a
single
flow
delivering
either
a
product
or
a
feature
on
a
consistent
basis
and
all
these
being
interconnected
and
the
complexity
Rising.
So
there's
there's
challenges
in
kind
of
management
that
are
arising
at
these
more
sophisticated
organizations,
or
maybe
just
larger
organizations
and
and
the
challenges
that
they're
not
necessarily
as
sophisticated
as
they
need
to
be.
D
So
we
have
limited
workflow
visibility,
that's
kind
of
wrapped
up
in
individual
systems
like
jira
and
and
let's
say
task
management
systems,
primarily
and
meaning
that
we
have
limited
ability
to
understand
what
happens
when
work
is
being
done,
whether
the
work
is
effective
or
there's
opportunities
for
improvement,
and
it's
very
challenging
to
adopt
the
solutions
that
exist
in
the
market.
Currently
a
woke
up,
Siri,
okay,
it's
very
difficult
to
adopt
the
the
current
platforms
that
are
available
on
the
market,
because
the
source
data
is
typically
low
quality.
D
D
So
what
we're
looking
to
do
is
gather
data
from
multiple
tools
across
a
value
stream
and
attribute
all
that
data
to
an
end-to-end
workflow
that
begins
at
the
initiation
of
an
effort
and
ends
with
the
delivery
of
that
effort
to
customers
and
not
only
the
delivery
to
production,
but
the
actual
effect
of
that
delivery.
D
Right
so
was
that
a
positive
or
negative
change
did
it
result
in
customer
value
by
metrics
that
we
Define
inside
of
our
organization,
so
either
usage
goes
up
or
you
know
we
retain
a
customer
that
we
were
at
risk
of
losing
there's
all
kinds
of
things
that
you
can
kind
of
connect
to
this
idea
of
value,
realization
and
I'm
trying
to
pay
attention
to
hands.
So
if
you
want
to
throw
a
hand
up,
it's
totally
fine
or
interrupts,
there's
only
a
few
of
us,
so
you
can
just
speak.
D
If
you
want
we,
we
would
like
to
be
able
to
enable
leadership
in
an
organization
to
see
not
only
just
a
single
value
stream,
but
how
the
organization
is
performing
as
a
network
of
value
streams
that
it
are
interconnected
and
interdependent,
and
the
connection
between
the
efforts
and
the
effects
of
all
of
those
value
streams,
including
things
like
customer
experience
and,
ideally,
let's
say,
contributor
experience
as
well.
D
We
want
a
single
source
of
data
for
workflow,
which
I
think
is
maybe
a
different
dimension
than
CD
events
is
currently
pursuing,
but
I'll
reiterate
that
later
and
then
understand
sort
of
how
this
data
can
be
used
to
manage
the
organization
and
ensure
a
specific
level
of
quality,
and
this,
hopefully
over
the
long
term,
feeds
things
like
artificial
intelligence,
insights
or,
let's
say,
machine
learning,
to
be
more
specific
on
what
possible
effects
of
changing
workflow
and
changing
the
system
have
on
this
performance
and
right
now,
we
would
like
to
more
directly
connect
values
from
delivery
platforms
to
Value
Street
management
platforms,
so
that
it
becomes
easier
over
time
to
say
that
okay,
we're
doing
a
specific
thing,
that's
enabled
by
this
system,
where
we've
improved
the
capability
of
the
system
and
so
we're
realizing
that
benefit
in
the
management
system
over
some
time.
D
On
what
ultimately
matters
to
the
business,
so
in
terms
of
value
stream
management,
what
we
care
about
is
everything
all
the
way
from
the
initial
population
of
a
portfolio
or
backlog,
like
the
the
first
instance
of
something
to
do,
and
ideally,
as
a
hypothesis,
all
the
way
to
analysis
of
that
hypothesis
did
it,
you
know.
Did
we
end
up
where
we
expected?
Are
we
realizing
the
value
that
we
expected?
D
Is
there
something
that
we've
learned
along
the
way,
and
it
kind
of
includes
a
lot
of
these
things
that
exist
inside
the
CDF
ecosystem,
but
perhaps
a
little
bit
broader
in
it,
in
a
difference
of
focus,
so
some
of
the
things
that
we
think
classify
this
domain
are
entities,
functional
components,
metrics
and
perhaps
events
like
I,
think
events
actually
feeds
directly
into
this
to
understand
what
is
behind
the
metrics
right,
it's
very
difficult
to
get
accurate
or
useful
metrics
without
parsing
events.
A
All
right
so
go
ahead
when
you
say
metrics
there.
That's
that's
to
me
some
some
calculated
data
from
other
sources,
which
could
be
events,
for
example,
exactly
exactly
I
mean
there's
no
one-to-one
relationship
between
metrics
and
events,
I
think
right.
It's
a
higher
level
abstraction
of
of
something
a
high
level
objects
of
that
data
which
could
come
from
events
exactly.
D
Exactly
so,
then,
I
suppose
that
events
would
be
accurately
classified
as
a
a
subset
of
metrics,
because
metrics
could
be
due
to
any
number
of
things.
A
D
You're
right
well,
yeah,
sorry,
no
I,
I,
think
you're
you're
right!
You
know
events
can
be
based.
They
could
be
compliance
relevant.
They
could
be
attributed
to
any
other
anything
you
you
want
to
observe
in
the
system.
Correct
yeah,.
A
Yeah
so
I
mean
entities,
I
mean
if
you
would,
for
example,
when,
as
we
call
artifacts
when
something
is
built,
a
new
new
version
of
the
software
is
built
and
put
on
the
Shelf.
Then
that's
also
informed
by
an
event
which
is
probably
not
meant
for
a
metric.
That's
meant
to
declare
that
now
we
have
a
new
version
of
this
entity.
A
D
C
You
could
still
build
metrics
for
from
that
event,
I
think,
though,
even
if
it's
not
originally
crafted
or
metrics
like,
if
you
think
of
like
Dora
metrics,
that
rely
on
information
about
yeah,
artifactory,
published
and
so
forth.
So.
B
A
C
I
think
so
the
only
tablet
there
is
yeah
I'm,
not
sure
how
different
the
data
model
would
be
for
the
two
use
cases
or
right
I.
Imagine
I
mean
my
my
feeling
is
that
there
is
a
good
amount
of
overlap,
at
least
so
you
should.
D
Wait
overlap
between.
C
D
Okay,
yeah
I
agree
so
in
the
entity
aspect
of
this.
What
we're
primarily
focused
on
in
value
stream
management
as
work
items,
so
we're
thinking
of
different
classifications
of
efforts.
Essentially,
epic
stories
tasks,
distribution
of
work
items
so
in
in
flow
framework.
There
is
four
categories
of
of
efforts:
there's
when
they
have,
they
have
a
risk
as
well.
Debt
and
defects,
but
primarily
you
know
most
folks
are
concerned
with
features
feature
delivery,
but
that
classification
allows
you
to
see
the
Mist
the
mix
over
time
and
understand.
D
Okay,
we've
over
invested
in
features
and
we're
seeing
little
payback
of
technical
debt,
and
that
is
manifesting
itself
through
a
a
trend
in
a
downward
Trend
in
productivity,
for
instance,
or
an
upward
Trend
in
incidents
the
systems
of
work.
So
we
have
producers
which
could
be
things
like
Version,
Control,
Systems,
producing
events.
We
could
have
Work
Work,
Management
Systems
like
jira
and
then
different
artifacts
within
that
workflow
and
contributors.
D
This
is
just
a
high
level.
So
far,
so
there's
quite
a
bit
that
could
be
included
here,
but.
A
About
the
the
defects
there,
how
would
you
define
a
defect?
Is
it
do
you
think?
That's
a
a
bug
in
some
Asia
tracker
system,
or
is
it
because,
yes
integrated
the
incident
events
and
the
incidents
as
we
call
the
normalcy
events
are
not
really
buggy
bugs
yet
I
would
say,
I
mean
an
incident
they're
just
reactions
to
issues
when
something
happens,
oh
yeah.
It's
rather
something
happens
in
the
system.
It's
an
incident!
Something
has
happened,
we
don't
know
yet.
A
C
A
D
It's
interesting,
I
I
would
say
that
that
that
that
that
would
apply
because
it
kind
of
arises
in
the
system
of
work
as
a
as
an
incident
to
be
addressed.
That.
D
Right
I
mean
it
kind
of
follows
the
same
workflow
as
a
lot
of
these
things,
just
with
a
different
level
of
urgency
and
a
a
lower
degree
of
definition.
Right,
something
has
happened,
we've
got
to
figure
it
out,
we've
got
to
get
it
solved.
Maybe
we
have
to
get
it
solved
immediately,
but
at
least
we
need
to
triage
it
immediately
right.
We
need
to
understand
okay.
Well,
this
is
not
a
big
deal,
let's,
let's
put
it
in
the
backlog
or
it's
a
it's
like
all
hands
on
deck.
D
And
you
know:
we've
been
through
the
through
the
vsmc,
we
kind
of
consider
Incident
Management
to
be
a
value
stream.
So
it's
like
the
the
practice
of
managing
incidents
would
be
something
performed
by
a
stable
team,
much
like
product
team,
hopefully
within
the
product
team
itself.
But
sometimes
you
know
this
goes
beyond
the
scope
of
a
product
team,
so
I
see.
D
Yeah
I
would
see
incidents
as
a
natural
inclusion
in
that
in
that,
because
it
certainly
wouldn't
fit
in
these
other
areas
that
we've
defined
so
functional
components-
there's
quite
a
bit
here,
but
this
is
essentially
like
a
catalog
of
systems
that
could
be
producing
data
or
repositories
of
data
to
consume
in
order
to
understand
the
value
stream
from
a
management
perspective.
D
Increasingly
we
have
things
like
value,
Management
Systems,
where
it's
a
repository
for
products,
portfolio
planning,
but
in
the
context
of
we
you
know
we
expect
to
get
this
return
on
investment
from
this
effort.
We
want
to
track
the
the
results
of
that
hypothesis
upon
realization
in
production
with
with
real
users,
and
that
could
be
long
term.
D
Metrics,
so
the
metrics
there's
quite
a
bit
of
metrics
that
we
care
about
in
the
context
of
value
stream
management,
but
this
is
a
selection
there's.
This
is
this
is
fairly
extensive.
D
These
are
kind
of
the
generic
terms
and
then
more
specific
industry
terms
that
have
caught
on
in
popularity.
So
things
like
flow
velocity
are
really
talking
about
throughput.
We
talk
about
lead
time,
there's
various
different
definitions,
I
think
the
you
know,
the
Dora
definition
of
lead
time
is
very
narrow
and
it's
really
talking
about
commit
to
production,
but
our
definition
of
lead
time
is
kind
of
lean
defined,
which
is
you
know,
everything
from
initiation
all
the
way
to
a
delivery
to
customer.
D
This
is
kind
of
driven
largely
by
Gartner's
analysis
of
what
they
they
throw
into
the
the
context
of
a
value
stream.
So
there
are
technical
product
and
business
metrics
that
kind
of
all
factor
in
here,
and
we
have
I
think
a
little
bit
of
variation
or
expansion
there.
But
these
are
the
sort
of
things
that
we
think
expand:
scope
beyond
your
typical
CI
CD
process
or
continuous
delivery
context.
D
Another
way
to
look
at
this
is
there's
quite
a
bit
in
kind
of
General
business
metrics
that
fall
under
the
umbrella
of
value
stream.
Metrics,
because
you
know
value
streams
are
very
tightly
correlated
to
business
performance
in
a
holistic
context,
so
we
would
also
be
looking
to
consume
over
the
long
term.
D
You
know
we're
not
going
to
be
factoring
in
cash
flow
anytime
soon,
I
don't
know
if
anybody
actually
captures
cash
flow
in
the
context
of
individual
efforts
and
and
connecting
the
dots,
but
that
this,
this
kind
of
sets
the
stage
for
the
long
term
promise
of
this
type
of
effort
where
you
can
connect.
You
know
we
did
this
thing
and
here's
the
ultimate
result
that,
in
the
context
of
the
business
and
stakeholders
and
shareholders
and
customers
and
everybody
involved,
all
the
way
down
to
you,
know
the
costs
of
of
each
of
those
contributing
factors.
D
There
are
some
existing
efforts
in
the
space,
so
we're
actually
leveraging
the
work
inside
of
it
for
it,
which
is
provided
by
the
open
group.
This
is
another
body,
that's
kind
of
in
the
value
stream
management
sense
in
in
the
space,
but
primarily
in
the
context
of
I.T,
so
not
the
broadest
domain.
It
does
consider
things
like
financial
management
and
it's
fairly
Broad
and
they've
done
some
good
work
on
identifying
functional
components
and
entities
that
you
know.
D
We
don't
want
to
reinvent
the
wheel,
so
we're
borrowing
quite
a
bit
from
what
they've
done
and
we
have
some
of
their
contributors
in
involved
in
the
bsmi
effort.
So
far,
so
they're
helping
us
kind
of
borrow.
What
what
makes
sense
here
and
integrate
it
into
the
dsmi
effort.
D
Safe
is
kind
of
a
you
know,
a
Powerhouse
in
this
industry
like
it
or
not,
and
they
include
some
of
this
scope
in
what
they
talk
about.
We
obviously
want
to
provide
something
that
they
work
in
concert
with,
instead
of
work
against,
so
that
we
don't
have
to
undo
everything.
That's
safe
does,
and
you
know
talk
about
how
you
know
we
have
we
we're
different
from
what
they're
proposing
so,
hopefully
something
they
can
leverage
and
just
say
that
the
bsmi
is
defined
value
stream
management.
D
Interoperability
in
these
in
these
ways-
and
you
know-
hopefully
provide
a
valuable
resource
to
the
most
popular
efforts
in
this
in
this
domain.
So
this
is
what
I've
parsed
from
CD
events.
So
far,
this
is
very
limited,
but
this
is
from
pulling
from
GitHub
and
and
what
I've,
what
I've
seen
so
far.
So
the
stages
that
you
folks
talk
about
the
architecture,
steps
in
relation
to
those
stages
and
the
difference
that
we
see
is
this
primarily
this
expansion
of
scope.
D
So
we
go
all
the
way
Upstream
to
initial
planning,
hopefully
capturing
what
was
defining
the
reason
why
a
specific
effort
is
happening
and
then
this
extension
Beyond
operation
two.
What
is
what
is
the
ultimate
outcome
of
this
effort?
What
are
we
doing
as
a
result?
Are
we?
Are
we
investing
further?
Are
we
going
to
change
our
approach?
Reprocessing
feedback,
so
I've
got
two
minutes
left
and
I've
got
to
jump
to
another
meeting.
D
But
in
summary,
what
I've
got
here
is
that
you
know
we.
We
think
that
we've
got
a
broader
scope.
We've
got
to
focus
on
workflow
and
and
a
different
level
of
detail,
so
expanding
into
value
estimation
and
realization,
but
we
can
pick
it
up
from
there.
We
don't
really
have
a
lot
more
here.
I'll
share
this
deck
with
you
folks,
just
so
you
can.
You
can
step
through
it,
but
this
is
sort
of
what
we've
got
so
far.
A
Yeah-
it's
it's
great,
so
it's
good
to
see
the
similarities
and
obviously
has
to
say
that
the
scope
for
this
work
that
you
have
there
is
is
much
broader
than
City
events
that
this
currently
focuses
on
and
I
would
doubt
that
students
will
never
go
to
such
a
broad
scope.
A
A
A
design
deployment
by
plan
and
continuous,
mounting
I
think
that
that's
a
bit
more,
the
terms
that
are
used
Maybe,
but
so
yeah
different
terms
and
different
economic
letters,
but
there's
a
lot
of
overlap,
so
I,
I'm,
yeah
I,
think
this
is
a
good
initiative
that
we
can
continue
working
on
so
for
the
next
meeting.
Should
we
are
you
able
to
come
in
in
two
weeks?
Maybe
that's
when
cdcon
is
by
the
way,
so.
B
D
If
that
doesn't
work
for
your
for
your
schedule,
you
can
definitely
we
can.
We
can
talk
about
a
a
next,
a
next
meeting
to
dive
a
little
bit
deeper,
but
it
sounds
I'm
very
happy
to
hear
that
you
folks
see
see
an
opportunity
here
and
look
forward
to
the
next.
The
next
conversation.
D
Apologies
I
gotta
run
but
and
I
I
probably
took
more
time
than
you
were
expecting,
but
I
appreciate
this.
We.