►
From YouTube: CDF SIG Best Practices - Aug 8, 2022
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
A
Okay,
well,
I
guess
we
should
get
started.
So
what
I
wanted
to
talk
about
today
really
was
getting
things
moving
on
the
reference
etc.
A
A
So,
if
I
switch
over
to
the
the
best
practices
website,
you
should
be
able
to
see
that
I've
now
added
added
a
new
architecture
section
in
in
this
version
of
the
documentation.
So
this
this
is
a
a
draft
of
punch
of
the
the
current
document
documentation.
So
it's
successful,
but
not
published
on
the
on
the
site.
A
A
We've
got
here
is
some
temple
and
plus
sign
that
we're
going
to
need
to
fill
out.
So
the
the
way
I
think
need
to
work
with
this
is
is
following
sort
of
the
basic
structure
of
the
methodology.
A
B
A
Within
continuous
delivery,
so
in
terms
of
what
that
represents
from
a
documentary
perspective,
these
are
the
the
first
four
sort
of
headline
pieces
is
that
we
we
need
to
get
written
up
so
so
these
viewpoints
is,
is
going
to
be
the
the
biggest
part
of
the
work
to
start
with,
and
what
I
mean
by
this
is
that
we
need
to
capture
the
viewpoint.
A
A
Sorry
to
cut
you
off
there,
I
think
we're
having
an
issue
with
your
audio,
your
your
voice,
keeps
kind
of
in
and
out
okay.
Well,
let
me
see
if
it
works
to
a
different
microphone,
hang
on
a
sec.
B
So
yeah
so
these
and
viewpoints.
Basically,
what
we're
looking
at
here
is
for
for
any
organization
that
wants
to
implement
continuous
delivery.
A
B
All
going
to
have
a
a
partial
view
of
the
problem,
and
that
means
that,
from
their
perspective,
they
will
have
an
individual
view
of
what
they
need
to
do
with
continuous
delivery,
so
that
it's
relevant
for
their
goals
and
their
concerns
in
within
the
organization.
B
Now,
the
challenge
is
that
very
few
people
will
have
a
complete
view
from
the
organization's
perspective.
So
what
tends
to
happen
is
that
people
grasp
onto
a
partial
set
of
goals
and
try
and
implement?
You
know
one
part
of
the
methodology
without
being
aware
of
how
that
will
impact
on.
A
B
B
Within
this
section,
I've
expanded
that
this
out
to
give
an
early
list
of
the
individual
stakeholders
who
are
likely
to
be
impacted,
and
this
is
not
a
complete
list.
So
one
of
the
things
that
we
need
to
do
is
make
sure
that
we
we've
got
a
a
full
set
of
viewpoints
here
from
any.
You
know
relevant
perspectives
within
a
given
organization.
B
But
this
is
our
starting
point
and
then
for
for
each
viewpoint,
we
need
to
actually
capture
what
that
viewpoint
is
and
then
spell
out
the
view
of
the
stakeholder
who's
holding
that
viewpoint
and
then
address
what
the
what
the
value
is
from
the
perspective
of
implementing
continuous
delivery
and
potentially
also
address
any
challenges
or
potential
issues
that
might
exist
for
that
particular
stakeholder
viewpoint.
A
B
B
So
so
what
I
would
ideally
like
is
to
get
some
contributors
working
on
this
section
of
the
documentation
so
that
we
can.
We
can
start
fill
out
these
these
views
and
and
get
a
good
picture
of
all
of
this
section
of
the
dock.
B
B
Going
back
to
the
overview,
we
then
need
to
look
at
the
drivers
and
constraints
that
will
be
behind
any
organization,
actually
doing
a
roll
out
of
continuous
delivery.
B
B
Then
the
the
the
next
two
pieces
are
capabilities
and
then
the
assessment
of
readiness,
so
the
capabilities
is
really
looking
at
what
what
skills
the
organization
already
has
in
this
space.
So
what
learnings
are
already
relevant
and
then
the
assessment
readiness
is
really
a
gap
analysis
to
say:
okay,
these
are
the
parts
we've
got.
These
are
the
things
that
we
don't
have
and
therefore
we
need
to
understand
which
pieces
of
work
we're
going
to
do
in
order
to
implement
this
methodology.
B
B
So
I
think
this
is
really
the
starting
point
of
this
reference
architecture
work
and
once
we've
got
this
piece
in
place,
we
we
can
do
a
sort
of
first
round
of
publishing.
So
we
can.
We
can
put
this
out
there
on
on
the
production
site
and
then
move
on
to
the
the
next
stages
of
you
know:
further
documentation.
A
So
a
question
from
my
side,
terry!
So
do
we
have
a
plan
to
reach
out
to
the
different.
B
So
probably
the
easiest
thing
to
do
is
for
us
to
encourage
some
contributors
who
have
some
commercial
experience
working
within
product
delivery,
businesses
so,
for
example,
people
with
product
management,
experience
or
people
operating
at
a
cto
level
or
an
architecture,
governance
level.
A
B
A
B
So
hopefully
we
should
have
plenty
of
people
involved
with
the
cdf
already
who
have
some
experience
in
this
space,
and
then
we
can
also
reach
out
to
them
the
members
to
ask
them
to
see
if
they
can
nominate
or
volunteer
people
from
within
their
organizations
to
come
and
contribute.
A
Okay
and
that,
but
we
should
stick
with
the
with
the
members
right.
B
There's
two
bits
of
this,
and,
and
so
we'll
we'll
probably
be
able
to
access
a
fairly
wide
audience
because
of
that,
so
the
the
views
and
viewpoints
piece
is
it's
sort
of
continuous
delivery.
Agnostic
in
the
everyone
who
has
worked
with
a
stakeholder
or
has
been
a
stakeholder
in
one
of
these
roles
will
be
able
to
spell
out
the
the
viewpoint
and
and
the
view
from
that
perspective,
because
you
know
they'll
have
been
very
very
familiar
with
what
that
looks
like
within
any
software
delivery
organization.
B
And
you
know,
in
many
cases
we
we've
got
people
who
are
currently
in
those
roles
who
are
contributing
within
the
cdf.
So
we
shouldn't
have
a
problem
in
getting
access
to
plenty
of
people
who
have
those
perspectives
where
it
then
becomes
more
specialized,
is
in
the
piece
around
spelling
out
the
implications,
and-
and
so
that's
where
we'll
have
to
then
add
to
the
the
basic
information
to
say.
Okay,
here
are
the
parts
that
are
relevant
from
a
continuous
delivery
perspective,
and
this
is
how
this
is
likely
to
impact
you
now.
B
Some
some
members
will
already
be
on
that
journey
and
will
be
able
to
feed
back
some
of
the
learning
experiences
that
they've
already
had
and
for
everyone
else.
This
will
be
a
useful
resource
to
help
them
set
their
expectations
for
what
they're
likely
to
encounter
in
in
various
areas.
B
Most
of
these
roles
are
sort
of
classic
stakeholder
roles
within
your
typical
software
delivery
organization,
and
I'm
I'm
sure,
we've
got
a
whole
bunch
of
people
already
in
involved.
Who've
have
worn
one
or
more
of
these
hats
and
and
can
help
out
where
we
might
need
to
explicitly
reach
out
and
ask
for
additional
help
is
from
say
the
legal
or
brand
management
perspective
where
we
might
have
less
experience
within
the
foundation
today.
B
The
site
itself
is
within
the
cd
foundation,
github
repository,
so
we
can
basically
treat
this
as
a
set
of
pull
requests
against
a
branch
on
that
repository.
B
So
you'll
you'll
find
that
there's
a
reference
architecture
branch
already
set
up
and
there
is
a
a
pull
request
for
that
branch
against
the
main
release.
B
B
I'm
not
going
to
make
you
stand
up
and
say
yes
in
the
session,
but
if
you
want
to
reach
out
to
me
and
express
an
interest
in
any
part
of
this,
that
you'd
like
to
add
some
content
to,
then
that
would
be
very
helpful.
B
To
do
is
put
together
some
messaging
that
we
can
then
communicate
to
the
rest
of
the
organization
and
the
membership
to
try
and
encourage
some
contributors
to
come
and
get
involved
in
this
piece
of
work.
B
I
don't
know
if
anyone's
got
any
suggestions
as
to
the
best
way
to
go
about
that,
but
that
would
certainly
be
useful.
A
About
finding
people
to
contribute
to
this,
like,
I
can
try
to
help
with
that,
because
when
I
reached
out
to
people
and
invited
them
for
the
strategy
meeting
governing
port
strategy
meeting,
I
heard
many
positive
comments
from
the
people
who
joined
the
meeting.
So
I
can
go
back
to
them
and
say
this
is
now
happening.
Could
you
please
come
and
contribute
these?
A
A
B
So
so
there's
a
way
to
say
that
here's,
a
list
of
things
that
we
need
to
fill
out,
make
it
clearer
to
people
where
they
can
get
involved,
and
you
know
also
it
helps
to
show
people
the
the
scale
of
what
needs
to
be
done
and
right
now,
where
we're
talking
about
sort
of
a
few
paragraphs
rather
than
having
to
write
war
and
peace.
So
it's
a
it's,
not
a
huge
commitment
from
any
one
individual
contributor.
B
But
if
we
get
half
a
dozen
people,
then
we'll
very
quickly
be
able
to
fill
this
out
and
get
a
good
collaborative
worldview.
A
Another
question
about
like
the
pull
requests
flow
and
so
on.
Some
people
may
not
be
familiar
with
github,
or
they
know
they
prefer
to
contribute
in
different
ways.
I
guess
it
should
be
fine
to
you
know,
have
a
google
doc
or
something
and
ask
them
to
know,
give
us
google
that
we
can
fix
publishing
your
contribution
ourselves.
B
So,
oh
welcome
to
melissa
and
thomas.
Let
me
just
switch
back
and
and
show
you
what
we've
been
discussing
here
so.
B
We've
got
a
a
draft
overview
of
the
the
first
section
of
the
reference
architecture,
which
has
been
added
to
the
the
cf
best
practices
website.
Now
this
is
on
a
preview
version
of
the
site.
B
B
So
what
we're
trying
to
do
is
get
some
contributors
to
help
fill
out
these
perspectives
and
the
primary
area
being
in
the
viewsmith
viewpoint,
section
where
what
we
want
to
do
is
document
the
sets
of
concerns
relating
to
each
of
these
classes
of
stakeholder.
B
A
B
Architecture
like
this
is
about
showing
that
everyone's
views
have
been
taken
into
account
and
and
also
demonstrating,
basically
what's
in
it
for
me
from
an
individual
stakeholder
perspective
and
what
usually
happens
when
you
work
through
problems
at
this
level.
Is
you
find
out
that
the
organizational
organization
actually
has
conflicting
demands
on
different
stakeholders?
B
And
so
you
know
one
group
wants
to
do
it
and
another
group
doesn't
want
to
do
it
because
one
group
is
being
measured
against
metrics.
That
mean
it's
good
to
do
continuous
delivery
and
another
group
has
a
different
set
of
metrics
that
conflict,
and
then
you
need
to
actually
get
senior
executives
to
adjust
those
metrics
to
align
them
to
the
overarching
strategy.
B
A
That
is
a
really
good
start.
I
love
the
different
viewpoints
approach
and
are
we
and
I'm
sorry
I
didn't
I
missed
the
beginning,
but
are
we
looking
to
reach
out
to
people
in
these
positions
to
get
review
to
get
their
input.
B
B
B
B
So
that's
easy
enough
where
it
gets
a
bit
more
challenging
is
where
we're
looking
at
things
like
legal
roles
or
brand
management
stuff
like
that,
where
we
might
not
necessarily
have
active
contributors
in
those
spaces
at
the
moment,
but
where
we
should
have.
You
know
some
people
in
member
organizations
who
may
be
volunteered
to
come
and
help
out.
B
And
I
think
the
the
process
of
actually
going
through
this
will
will
help
to
get
people
to
understand
why
we're
doing
this
and
what
it
means,
because
it's
it's
all
a
bit
theoretical
until
you
go
through
one
of
these
exercises
for
the
first
time
and
then
it
suddenly
starts
to
really
make
sense
when
you
sit
down
and
and
think
about.
Well,
what
is
the
viewpoint
from
my
job
position
and
what
what's
the
perspective?
I
should
be
taking
what's
important
to
me.
What,
where
are
my
blind
spots.
A
So
I
have
a
quick
question
on
this,
so
based
on
the
best
practices
right
is
there
going
to
be
so?
This
is
like
a
best
practices
guide.
So
is
there
going
to
be
like
an
implementation
of
how
these
practice
practices
look?
A
You
know
based
on
you
know,
just
this
is
my
first
time
attending
this
meeting,
so
I
apologize
if
it's
a
it's
been
answered
before
and
such
but
like
based
off
this,
is
there
going
to
be
our
it's
the
next
step
going
to
be
like
hey,
let's
create
some
kind
of
important
implementation
that
takes
takes
all
these
best
practices
and
kind
of
shows
it
in
a
form
that
customer
or
whoever
is
going
to
look
at
this
going
to
can
follow.
B
Yeah,
so
that's
a
very
good
question
and
and
it's
it's
the
sort
of
medium
term
goal
of
this
piece
of
work.
B
The
the
way
we're
trying
to
tackle
this
is,
if
you
like,
an
inverted
pyramid
balanced
on
a
pyramid
in
that
we're,
starting
at
the
very
top
with
the
methodology
itself.
B
So
this
is
continuous
delivery
as
a
theoretical
methodology
for
improving
your
ability
to
deliver
product
to
market
quickly
and
that's
what
the
best
practices
site
is
all
about,
and
then
what
we're
doing
with
this
piece
is
now
saying:
okay,
well,
you've
got
the
theory,
but
here's
the
impact
when
you
start
to
apply
that
theory
to
your
organization,
and
this
is
who
it's
going
to
affect,
and
this
is
how
it's
going
to
change
the
way
they
need
to
work
in
order
for
this
to
pay
off
for
you
and
then
that,
if
you
like
comes
down
to
a
a
point
which
is
okay.
B
So
what
what
are
the
specifics
and
then
the
the
way
we're
going
to
approach
that
is
to
then
have
each
of
the
relevant
cdf
projects
provide
a
perspective,
saying:
okay,
here's
how
you
implement
best
practice
and
the
reference
architecture
using
this
technology.
A
Got
it
that
makes
sense,
okay,
yeah,
so
I'm
just
coming
like
this
is
my
first
time
so
like
I'm
coming
in
from
more
of
a
software
supply
chain
security
aspect,
so
we've
been
actually
using
a
lot
of
tecton
and
tektons
techno
pipelines,
tecton
chains,
and
we
kind
of
built
out
like
a
reference
architecture
through
the
cncf.
Basically,
you
know
the
the
supply
chain,
security,
best
practices,
white
paper
that
came
out
and
the
reference
architecture
that
came
up
for
that.
A
B
Yeah,
so
that
that's
exactly
the
the
sort
of
thing
that
we're
looking
for
to
go
into
the
the
community
side
of
of
this.
So
let
me
switch
back
over
to
this.
So
if
you're
familiar
with
the
with
the
best
practices
site,
there's
a
community
section
here
which
is
set
up
and
ready
to
go,
for
you
know,
white
papers
and
discussion
about
exactly
those
types
of
things.
B
So
if
if
you
would
like
to
work
on
something
in
that
area,
then
feel
free
to
send
me
a
sort
of
pricey
of
what
you'd
like
to
produce
and
then,
if
we're
comfortable
with
the
the
the
content,
you
know
general
framework
of
that,
then
you
know
you're
welcome
to
then
create
and
submit
a
pr
and
we'll
we'll
merge
it
into
into
this
section.
A
B
So
we
we
have
the
the
cso
viewpoint.
So,
okay.
B
We
can
we
can
expand
these,
so
if
you
feel
that
there
are
multiple
different
viewpoints
that
we
need
to
incorporate,
then
we
can
do
that.
I
suspect
what
we'll
actually
probably
do
with
some
of
these
is
have
a
a
headline
title,
but
then
expand
this
out
with
a
set
of
tags
to
say
you
know
this
applies
to
the
following
job
descriptions
so
so
that
we
can
make
it
easier
for
people
to
search
on
what
their
role
is
and
link
into
a
relevant
viewpoint
that
sits
with
that.
A
I
like
that
idea,
yeah
I
mean,
I
think
the
right.
I
think
security
should
be
on
the
mind
right.
I
mean
everybody
in
that
in
terms
of
the
views
that
we
kind
of
listed
out
there.
I
think
it's
it's.
How
much
I
think
in
the
best
practices,
I
think
it
should
be
like
you
should
be
paying
attention
to
security
right.
Security
is
not
something
is
an
afterthought,
but
that
each
of
these
roles
are
kind
of
responsible
for
it
and
how
maybe
each
one.
A
B
We
should
also
express
the
security
perspective
as
part
of
that
that
viewpoint,
we're
also
operating
within
the
context
of
the
broader
best
practices,
so
you'll
see
that
we've
got
software
supply
chain
as
a
piece
in
here
and
in
fact
that
spans
four
major
categories
of
which
the
supply
chain
security
is
is
one
so
you
know
we,
we
tried
to
capture
a
high-level
view
of
best
practice
in
this
space.
This
is
a
work
in
progress.
B
But
ideally
what
I
like
to
see
is,
as
we
move
into
the
the
architecture
section,
we
start
to
expand
on
some
of
this
now.
This
is
this
piece
is
phase
one
of
the
reference
architecture,
and
I
would
expect
us
to
need
to
expand
on
some
of
this.
Typically,
if
you
were
following
togaf,
you
would
have
a
you
know,
business
architecture
and
a
technical
architecture,
etc,
etc.
B
So
any
other
questions
on
this
anything
that
I've
missed.
B
As
we
go
through
this
process,
it
will
become
more
obvious
where
the
gaps
are,
and
so
I
I
suggest
that
we
we
keep
a
track
of
any.
You
know
key
pieces
that
we
think
need
to
be
included
in
this
documentation
as
issues
on
the
best
practices
site,
repo,
so
feel
free
to
post
stuff
in
in
there
and
use
that
as
a
memory,
so
that
we
can,
we
can
come
back
to
those
and
add
them
as
we
as
we
get
further
down
the
chain.
B
So
does
anyone
have
any
specific
questions
about
next
steps?
Oh,
does
anyone
want
to
volunteer
anyone
from
their
organization
to
come
and
get
involved.
A
B
Yeah,
so
the
the
the
repo
itself
can
can
be
found
within
the
cd
foundation.
Github
and
you'll
find
that
it
it
it.
It's
called
best
practices
site
and
the
the
the
main
site
is
at
best
practices,
cd
dot
foundation.
B
But
this
is
the
the
view
that
you're
seeing
here
is
a
is
a
preview
which
is
publicly
accessible.
So
you
can
actually
see
what's
in
here,
but
it's
not
the
official
published
version
of
the
site.
B
Now
we
can,
we
can
take
contributions
as
pull
requests
against
the
reference
architecture,
branch
and
I'm
happy
for
people
to
just
start
firing
speculative
prs
in
more
than
welcome.
But
if
you'd
like
to
start
a
discussion,
first
then
feel
free
to
raise
an
issue
on
on
that
repo
or
come
and
join
the
conversation
in
the
best
practices,
slack
channel
or
just
out
reach
out
to
to
me
and
have
a
conversation.
B
I
think
the
nice
thing
about
this
piece
of
work
is
it.
It
lets
a
much
broader
audience
get
involved
with
with
the
work
that
we're
doing
within
the
cd
foundation.
This.
This
is
all
going
to
be
very
non-technical
as
as
a
piece
of
work,
it's
it's
all
documentation,
but
it
relies
upon
people
having
you
know,
good,
hands-on
experience
of
actually
working
within
software
delivery
and
not
just
as
a
technical
contributor,
but
but
also.
B
B
Okay,
anyone
have
anything
else,
they'd
like
to
add
at
this
point.
A
B
Well,
it's
it's
one
of
those
things
where
it's
much
much
easier
to
understand.
If
you
can
see
what
it
is,
we're
trying
to
do
and
where
the
gaps
are
so
rather
than
constantly
having
to
explain
this
stuff
and
get
people
to
understand
it's
much
easier
to
just
build
a
framework
and
then
say
what
we
need
to
do
is
build
fill
in
all
the
gout.
B
And
there's
this
there's
probably
a
couple
of
rounds
of
this
that
we
can
do
and
once
we've
filled
in
this
first
set
and
published
this,
then
there's
an
another
level
of
detail
that
we
could
then
go
into
and
and
expand
on
that
again
and-
and
we
can,
we
can
keep
doing
that
until
we
feel
that
we've
got
a
really
rich
resource
that
is
properly
communicating
the
challenges
in
the
space.
B
But
I
think
this,
although
it
sounds
like
a
big
undertaking,
it's
actually
fairly
nicely
time
boxed.
We
should
be
able
to
pull
this
together
quite
quickly
and
get
it
to
the
point
where
it's
useful
information,
that's
tidy
enough,
that
we
can
publish
it
and
it
stands
alone.
B
So
again,
I
want
us
to
be
doing
continuous
delivery
on
our
documentation,
as
well
as
everything
else,
so
it
would
be
nice
to
to
move
fairly
quickly
through
this
phase.
Get
some
momentum
going
and
know
get
something
out.
You
know
in
weeks
to
month,
rather
than
months
to
years,
as
it
was
with
the
original
site,.
B
Okay,
well,
if
everybody's
happy
with
that,
then
I
think
it's
probably
a
good
place
to
wind
up.
You
know
feel
free
to
reach
out
to
me
or
put
people
in
touch
with
me
and
we'll
get
this
started
and
get
moving.